[Kernel-packages] [Bug 1534647] Re: Collateral damage due to kernel configuration change enabling CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)

[Doug Smythies]

> Upstream is discussing a fix that might allow both configurations
@Tim, could you point us to the upstream discussion?

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

Title:
  Collateral damage due to kernel configuration change enabling
  CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)

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

Bug description:
  Late in the kernel 4.4 RC (Release Candidate) cycle (between rc7 and
  rc8), Ubuntu implemented an amd64 kernel configuration change enabling
  CONFIG_ZONE_DEVICE.

  The related email: https://lists.ubuntu.com/archives/kernel-
  team/2016-January/067683.html

  The commit message does mention collateral damage: "In effect, this precludes 
devices that can only DMA from memory addresses below 16MB".
  Indeed we already have a complaint about a sound card that doesn't work as of 
kernel 4.4-rc8.

  If CONFIG_ZONE_DEVICE is enabled, then CONFIG_ZONE_DMA is forced to disabled, 
which in turn forces these devices, all are sound cards, and their derivative 
devices, to be disabled:
  Avance Logic ALS300/ALS300+
  ALi M5451 PCI Audio Controller
  Aztech AZF3328 / PCI168
  Emu10k1 (SB Live!, Audigy, E-mu APS)
  Emu10k1X (Dell OEM Version)
  ESS ES1938/1946/1969 (Solo-1)
  ESS ES1968/1978 (Maestro-1/2/2E)
  ICEnsemble ICE1712 (Envy24)
  ESS Allegro/Maestro3
  S3 SonicVibes
  Trident 4D-Wave DX/NX; SiS 7018.

  References: linux/mm/Kconfig; linux/sound/pci/Kconfig

  One test done (suggested by apw on IRC) was to remove the dependency of 
ZONE_DEVICE on !ZONE_DMA, but that causes:
  "#error ZONES_SHIFT -- too many zones configured adjust calculation", as apw 
predicted.
  In a mindless way, I tried to allow more zones in 
linux/include/linux/page-flags-layout.h, but that caused a bunch of "shifting 
by too many bits type errors. Anyway it seems that MAX_NR_ZONES is, at least 
partially, hard coded to 4 in some array definitions and such.

  Please do not ask me to do "apport-collect" for this bug report as it
  is not needed, nor relevant.

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

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

[Kernel-packages] [Bug 1398193] Re: The bluetooth headset can not control the media playback

[Pat McGowan]

** Tags added: bluetooth

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

Title:
  The bluetooth headset can not control the media playback

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  In Progress
Status in media-hub package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu RTM:
  Invalid

Bug description:
  [Preconditions]
  1.The DUT pair with bluetooth headset

  [Procedures]
  1.Play a video using the mediaplayer-app
  2.Play/pause video by bluetooth headset

  [Expect results]
  The bluetooth headset can play/pause video
  [Actual results]
  The bluetooth headset can not control the video playback.

  [Reproduce]
  Always

  Same for audio playback

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+subscriptions

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

[Kernel-packages] [Bug 1536493] Re: Call/SMS Alert are not routed to bluetooth headset

[Pat McGowan]

** Tags added: bluetooth

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

Title:
  Call/SMS Alert are not routed to bluetooth headset

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Expected Result:
  All audio from the phone should play in the bluetooth headset when it is 
connected.

  Actual Result:
  The music and other audio plays on the bluetooth headset however the SMS/Call 
alerts are not. They are still played in the phone's speaker. This causes the 
user to miss the notification because you can't hear it especially when 
listening to music/podcast.

  Device:
  bq Aquarius E5 HD
  Version:
  OTA 8.5

  Same on MX4 rc-proposed/ota 9

  In addition when answering the call, the call audio is not on the
  headset

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536493/+subscriptions

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  package linux-image-4.3.0-7-generic 4.3.0-7.18 failed to
  install/upgrade: подпроцесс установлен сценарий post-installation
  возвратил код ошибки 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  123

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-7-generic 4.3.0-7.18
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  valera 1683 F pulseaudio
  Date: Tue Feb  2 22:40:53 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 2
  InstallationDate: Installed on 2016-01-17 (16 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: HP-Pavilion NR011AA-ACB p6041ru
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=2f6ba869-6053-4970-8790-7eca9b875aa7 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-35ubuntu1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.3.0-7-generic 4.3.0-7.18 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.43
  dmi.board.name: Benicia
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Asset-1234
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnNR011AA-ACBp6041ru:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: NR011AA-ACB p6041ru
  dmi.sys.vendor: HP-Pavilion

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

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

[Kernel-packages] [Bug 1541044] Re: package linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 25

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 25

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

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Tue Feb  2 12:56:05 2016
  DpkgHistoryLog:
   Start-Date: 2016-02-02  12:56:00
   Commandline: aptdaemon role='role-commit-packages' sender=':1.68'
   Install: linux-image-extra-3.19.0-49-generic:i386 (3.19.0-49.55~14.04.1), 
linux-headers-3.19.0-49:i386 (3.19.0-49.55~14.04.1), 
linux-headers-3.19.0-49-generic:i386 (3.19.0-49.55~14.04.1), 
linux-image-3.19.0-49-generic:i386 (3.19.0-49.55~14.04.1)
   Upgrade: linux-generic-lts-vivid:i386 (3.19.0.47.32, 3.19.0.49.34), 
linux-libc-dev:i386 (3.13.0-76.120, 3.13.0-77.121), 
linux-headers-generic-lts-vivid:i386 (3.19.0.47.32, 3.19.0.49.34), 
linux-image-generic-lts-vivid:i386 (3.19.0.47.32, 3.19.0.49.34)
  DpkgTerminalLog:
   Preparing to unpack 
.../linux-image-3.19.0-49-generic_3.19.0-49.55~14.04.1_i386.deb ...
   Can't locate object method "new" via package "Text::Iconv" (perhaps you 
forgot to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-3.19.0-49-generic_3.19.0-49.55~14.04.1_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 25
  DuplicateSignature: 
package:linux-image-3.19.0-49-generic:3.19.0-49.55~14.04.1:subprocess new 
pre-installation script returned error exit status 25
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 25
  InstallationDate: Installed on 2015-09-12 (143 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: linux-lts-vivid
  Title: package linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 25
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1534647] Re: Collateral damage due to kernel configuration change enabling CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-January/067683.html
http://www.spinics.net/lists/kernel/msg2170767.html

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

Title:
  Collateral damage due to kernel configuration change enabling
  CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)

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

Bug description:
  Late in the kernel 4.4 RC (Release Candidate) cycle (between rc7 and
  rc8), Ubuntu implemented an amd64 kernel configuration change enabling
  CONFIG_ZONE_DEVICE.

  The related email: https://lists.ubuntu.com/archives/kernel-
  team/2016-January/067683.html

  The commit message does mention collateral damage: "In effect, this precludes 
devices that can only DMA from memory addresses below 16MB".
  Indeed we already have a complaint about a sound card that doesn't work as of 
kernel 4.4-rc8.

  If CONFIG_ZONE_DEVICE is enabled, then CONFIG_ZONE_DMA is forced to disabled, 
which in turn forces these devices, all are sound cards, and their derivative 
devices, to be disabled:
  Avance Logic ALS300/ALS300+
  ALi M5451 PCI Audio Controller
  Aztech AZF3328 / PCI168
  Emu10k1 (SB Live!, Audigy, E-mu APS)
  Emu10k1X (Dell OEM Version)
  ESS ES1938/1946/1969 (Solo-1)
  ESS ES1968/1978 (Maestro-1/2/2E)
  ICEnsemble ICE1712 (Envy24)
  ESS Allegro/Maestro3
  S3 SonicVibes
  Trident 4D-Wave DX/NX; SiS 7018.

  References: linux/mm/Kconfig; linux/sound/pci/Kconfig

  One test done (suggested by apw on IRC) was to remove the dependency of 
ZONE_DEVICE on !ZONE_DMA, but that causes:
  "#error ZONES_SHIFT -- too many zones configured adjust calculation", as apw 
predicted.
  In a mindless way, I tried to allow more zones in 
linux/include/linux/page-flags-layout.h, but that caused a bunch of "shifting 
by too many bits type errors. Anyway it seems that MAX_NR_ZONES is, at least 
partially, hard coded to 4 in some array definitions and such.

  Please do not ask me to do "apport-collect" for this bug report as it
  is not needed, nor relevant.

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

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

[Kernel-packages] [Bug 1541058] [NEW] linux: 4.4.0-3.17 -proposed tracker

[Tim Gardner]

Public bug reported:

This bug is for tracking the 4.4.0-3.17 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:Tuesday, 02. February 2016 18:30 UTC
kernel-phase-changed:Tuesday, 02. February 2016 18:30 UTC
kernel-phase:Prepare

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

** Affects: kernel-development-workflow/automated-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: Medium
 Status: New

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


** Tags: block-proposed kernel-release-tracking-bug xenial

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

** Tags added: block-proposed

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

** Tags added: xenial

** Also affects: kernel-development-workflow/automated-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/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-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)
   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/1541058

Title:
  linux: 4.4.0-3.17 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-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:
  New
Status in linux source 

[Kernel-packages] [Bug 1541062] [NEW] package linux-image-extra-4.3.0-7-generic 4.3.0-7.18 failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1

[Валера]

Public bug reported:

123

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.3.0-7-generic 4.3.0-7.18
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  valera 1618 F pulseaudio
Date: Tue Feb  2 21:32:32 2016
ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код ошибки 1
InstallationDate: Installed on 2016-01-17 (16 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: HP-Pavilion NR011AA-ACB p6041ru
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=2f6ba869-6053-4970-8790-7eca9b875aa7 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-35ubuntu1
RfKill:
 
SourcePackage: linux
Title: package linux-image-extra-4.3.0-7-generic 4.3.0-7.18 failed to 
install/upgrade: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 1
UpgradeStatus: Upgraded to xenial on 2016-01-19 (13 days ago)
dmi.bios.date: 09/10/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.43
dmi.board.name: Benicia
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.01
dmi.chassis.asset.tag: Asset-1234
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnNR011AA-ACBp6041ru:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: NR011AA-ACB p6041ru
dmi.sys.vendor: HP-Pavilion

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-extra-4.3.0-7-generic 4.3.0-7.18 failed to
  install/upgrade: подпроцесс установлен сценарий post-removal возвратил
  код ошибки 1

Status in linux package in Ubuntu:
  New

Bug description:
  123

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.3.0-7-generic 4.3.0-7.18
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  valera 1618 F pulseaudio
  Date: Tue Feb  2 21:32:32 2016
  ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 1
  InstallationDate: Installed on 2016-01-17 (16 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: HP-Pavilion NR011AA-ACB p6041ru
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=2f6ba869-6053-4970-8790-7eca9b875aa7 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-35ubuntu1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.3.0-7-generic 4.3.0-7.18 failed to 
install/upgrade: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 1
  UpgradeStatus: Upgraded to xenial on 2016-01-19 (13 days ago)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.43
  dmi.board.name: Benicia
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Asset-1234
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnNR011AA-ACBp6041ru:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: NR011AA-ACB p6041ru
  dmi.sys.vendor: HP-Pavilion

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

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

[Kernel-packages] [Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one

[Cavsfan]

The installation of the 4.4.0-2-generic in Xenial 16.04 went well, It
left 3 kernels in 01autoremove-kernels so I manually purged the 3rd
oldest one. Now there are 2 there. I updated my /etc/kernel/postinst.d
/apt-auto-removal with version 5 above.

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

Title:
  /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
  except the latest one

Status in One Hundred Papercuts:
  Triaged
Status in apt package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After installing a 3rd kernel currently 3.19.0-12-generic, the
  /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
  3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed
  to be autoremoved. But once autoremove is completed the machine
  requests to be rebooted and at that time the /etc/apt/apt.conf.d
  /01autoremove-kernels file lists the 3.19.0-12-generic and
  3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is
  requested to be autoremoved leaving only one kernel the latest one
  3.19.0-12-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  5 17:03:01 2015
  InstallationDate: Installed on 2015-04-02 (3 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1541058] Re: linux: 4.4.0-3.17 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 4.4.0-3.17 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:Tuesday, 02. February 2016 18:30 UTC
  kernel-phase-changed:Tuesday, 02. February 2016 18:30 UTC
  kernel-phase:Prepare
+ kernel-stable-Promote-to-proposed-end:Tuesday, 02. February 2016 19:01 UTC

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

Title:
  linux: 4.4.0-3.17 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-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:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-3.17 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:Tuesday, 02. February 2016 18:30 UTC
  kernel-phase-changed:Tuesday, 02. February 2016 18:30 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 02. February 2016 19:01 UTC

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

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

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

[Robie Basak]

If this will take a while, then would it be possible to have ofono
default to a deterministic SIM for outbound calls as an interim
workaround? Eg. sort them by some key and take the lowest one, or use
the lowest numbered port or something. Then I could swap the SIM cards
around (if needed) to get the behaviour I need without having to wait
for a full solution.

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

Title:
  Calling from car using bluetooth, call is placed on ril_0, even though
  ril_1 is default

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Triaged
Status in telephony-service package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  What happened
  Placed call from car over bluetooth
  Call was placed on my first SIM card, even though I selected my second SIM as 
default for calls

  What should have happened
  The call should have been placed on my second SIM

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20150124-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: armhf
  Date: Wed Feb  4 14:25:44 2015
  InstallationDate: Installed on 2015-02-02 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150202-020204)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions

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

[Kernel-packages] [Bug 1534647] Re: Collateral damage due to kernel configuration change enabling CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)

[Doug Smythies]

I found this:
https://lkml.org/lkml/2016/1/25/1233
and this:
https://bugzilla.kernel.org/show_bug.cgi?id=110931


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

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

Title:
  Collateral damage due to kernel configuration change enabling
  CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)

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

Bug description:
  Late in the kernel 4.4 RC (Release Candidate) cycle (between rc7 and
  rc8), Ubuntu implemented an amd64 kernel configuration change enabling
  CONFIG_ZONE_DEVICE.

  The related email: https://lists.ubuntu.com/archives/kernel-
  team/2016-January/067683.html

  The commit message does mention collateral damage: "In effect, this precludes 
devices that can only DMA from memory addresses below 16MB".
  Indeed we already have a complaint about a sound card that doesn't work as of 
kernel 4.4-rc8.

  If CONFIG_ZONE_DEVICE is enabled, then CONFIG_ZONE_DMA is forced to disabled, 
which in turn forces these devices, all are sound cards, and their derivative 
devices, to be disabled:
  Avance Logic ALS300/ALS300+
  ALi M5451 PCI Audio Controller
  Aztech AZF3328 / PCI168
  Emu10k1 (SB Live!, Audigy, E-mu APS)
  Emu10k1X (Dell OEM Version)
  ESS ES1938/1946/1969 (Solo-1)
  ESS ES1968/1978 (Maestro-1/2/2E)
  ICEnsemble ICE1712 (Envy24)
  ESS Allegro/Maestro3
  S3 SonicVibes
  Trident 4D-Wave DX/NX; SiS 7018.

  References: linux/mm/Kconfig; linux/sound/pci/Kconfig

  One test done (suggested by apw on IRC) was to remove the dependency of 
ZONE_DEVICE on !ZONE_DMA, but that causes:
  "#error ZONES_SHIFT -- too many zones configured adjust calculation", as apw 
predicted.
  In a mindless way, I tried to allow more zones in 
linux/include/linux/page-flags-layout.h, but that caused a bunch of "shifting 
by too many bits type errors. Anyway it seems that MAX_NR_ZONES is, at least 
partially, hard coded to 4 in some array definitions and such.

  Please do not ask me to do "apport-collect" for this bug report as it
  is not needed, nor relevant.

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

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

[Kernel-packages] [Bug 1537918] Re: Kernel doesn't support UDF

[Joseph Salisbury]

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

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

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

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

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


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

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

Title:
  Kernel doesn't support UDF

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I was pulling my hair out for the last six months trying to figure out
  why the heck some DVDs (encrypted, pressed, burned, it doesn't matter)
  just will not be recognized. In the GNOME Disk Utility, the disks show
  up as X.X GB Unknown, and will not mount. I have to manually go into a
  terminal, type

  sudo mount /dev/sr0 /mnt

  and just deal with it. This is a real pain, and I just recently
  figured out why. According to this:

  http://superuser.com/questions/730130/how-to-get-ubuntu-12-04-to-
  recognize-the-udf-filesystem

  in addition to this:

  http://www.linuxquestions.org/questions/linux-desktop-74/some-udf-
  dvds-will-not-mount-unknown-filesystem-4175550577/

  I deduced that the kernel was not compiled with UDF support.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ihatewindows  28002 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan 22 13:55:28 2016
  HibernationDevice: RESUME=UUID=2f0f1d7c-4117-40df-9314-f2556c82fc3b
  InstallationDate: Installed on 2015-11-12 (71 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude E5420
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0H5TG2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd11/30/2011:svnDellInc.:pnLatitudeE5420:pvr01:rvnDellInc.:rn0H5TG2:rvrA03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)

[Joseph Salisbury]

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

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

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

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

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


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

** Tags added: kernel-da-key

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

Title:
  Touchpad not working (4.3 -> 4.4 regression)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not
  working. When booting 4.3 kernels, the touchpad is works.

  Expected: When I move a finger touching the touchpad, an arrow should move 
accordingly on the screen.
  What happens instead: nothing.

  I've tried an upstream 4.4 kernel; problem is present there as well.

  I've booted with pci=noaer due to another bug that would otherwise
  spam dmesg. Removing it does not fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 18:49:25 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent pci=noaer 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 972604] Re: 168c:001c [HP Compaq Presario C700 Notebook PC] Wireless led button doesn't switch colors

[Joseph Salisbury]

I built a Wily test kernel with the fix mentioned in comment #60.  Can
you test this kernel and see if it resolves this bug?  It can be
downloaded from:

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

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

Title:
  168c:001c [HP Compaq Presario C700 Notebook PC] Wireless led button
  doesn't switch colors

Status in linux package in Ubuntu:
  In Progress

Bug description:
  I'm using Lubuntu 11.10 Oneiric Ocelot. My wifi chip is supported from
  ath5k drivers. The led button blinks between red and blue light and
  its pressure does anything.

  WORKAROUND: I tried to type:
  echo none > "/sys/class/leds/ath5k-phy0::tx/trigger"
  echo phy0radio > "/sys/class/leds/ath5k-phy0::rx/trigger"

  and in this way I can control the color of the LED. But the problem is
  that the colors are reversed: it should be red for wifi off and blue
  for wifi on, but it is rather the opposite!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-17-generic 3.0.0-17.30
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
  Uname: Linux 3.0.0-17-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cristian   1872 F pulseaudio
  CRDA: Error: [Errno 2] File o directory non esistente
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x9240 irq 42'
     Mixer name : 'Conexant CX20561 (Hermosa)'
     Components : 'HDA:14f15051,103c30d9,0010'
     Controls  : 15
     Simple ctrls  : 8
  Date: Tue Apr  3 17:37:08 2012
  HibernationDevice: RESUME=UUID=3899fff8-34b5-4722-a9f7-44fd70d111c9
  InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 04f2:b057 Chicony Electronics Co., Ltd integrated USB 
webcam
  MachineType: Hewlett-Packard Compaq Presario C700 Notebook PC
  ProcEnviron:
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic 
root=UUID=36836f2d-ce02-4249-a4c4-8ad7eb580b58 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-17-generic N/A
   linux-backports-modules-3.0.0-17-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserAsoundrc:
   pcm.Intel { type hw; card Intel; }
   ctl.Intel { type hw; card Intel; }
   pcm.!default pcm.Intel
   ctl.!default ctl.Intel
  dmi.bios.date: 02/29/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.31
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30D9
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 83.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.31:bd02/29/2008:svnHewlett-Packard:pnCompaqPresarioC700NotebookPC:pvrF.31:rvnHewlett-Packard:rn30D9:rvr83.21:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: Compaq Presario C700 Notebook PC
  dmi.product.version: F.31
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu2605 F lxpanel
  CRDA: Error: [Errno 2] File o directory non esistente
  CasperVersion: 1.336ubuntu1
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  LiveMediaBuild: Lubuntu 14.04 "Trusty Tahr" - Alpha i386 (20131218)
  MachineType: Hewlett-Packard Compaq Presario C700 Notebook PC
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=it 
keyboard-configuration/layoutcode?=it
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware1.117
  StagingDrivers: zram
  Tags:  trusty staging
  Uname: Linux 3.12.0-7-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/29/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.35
  

[Kernel-packages] [Bug 1541086] [NEW] package linux-image-4.3.0-7-generic 4.3.0-7.18 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 2

[Валера]

Public bug reported:

123

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.3.0-7-generic 4.3.0-7.18
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  valera 1683 F pulseaudio
Date: Tue Feb  2 22:40:53 2016
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 2
InstallationDate: Installed on 2016-01-17 (16 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: HP-Pavilion NR011AA-ACB p6041ru
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=2f6ba869-6053-4970-8790-7eca9b875aa7 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-35ubuntu1
RfKill:
 
SourcePackage: linux
Title: package linux-image-4.3.0-7-generic 4.3.0-7.18 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.43
dmi.board.name: Benicia
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.01
dmi.chassis.asset.tag: Asset-1234
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnNR011AA-ACBp6041ru:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: NR011AA-ACB p6041ru
dmi.sys.vendor: HP-Pavilion

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-4.3.0-7-generic 4.3.0-7.18 failed to
  install/upgrade: подпроцесс установлен сценарий post-installation
  возвратил код ошибки 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  123

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-7-generic 4.3.0-7.18
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  valera 1683 F pulseaudio
  Date: Tue Feb  2 22:40:53 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 2
  InstallationDate: Installed on 2016-01-17 (16 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: HP-Pavilion NR011AA-ACB p6041ru
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=2f6ba869-6053-4970-8790-7eca9b875aa7 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-35ubuntu1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.3.0-7-generic 4.3.0-7.18 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.43
  dmi.board.name: Benicia
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Asset-1234
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnNR011AA-ACBp6041ru:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: NR011AA-ACB p6041ru
  dmi.sys.vendor: HP-Pavilion

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

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

[Kernel-packages] [Bug 1494225] Re: Call audio is not routed to headset with HFP

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: High => Critical

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

Title:
  Call audio is not routed to headset with HFP

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Fix Committed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  With bluez 5.33 on Nexus 4 and silo 43 installed:

  * pair and connect a headset over HFP
  * Establish an outgoing call or accept an incoming one
  * Once the call is established the call audio isn't routed through the 
handsfree device

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+subscriptions

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

[Kernel-packages] [Bug 1536493] Re: Call/SMS Alert are not routed to bluetooth headset

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: High => Critical

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

Title:
  Call/SMS Alert are not routed to bluetooth headset

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Expected Result:
  All audio from the phone should play in the bluetooth headset when it is 
connected.

  Actual Result:
  The music and other audio plays on the bluetooth headset however the SMS/Call 
alerts are not. They are still played in the phone's speaker. This causes the 
user to miss the notification because you can't hear it especially when 
listening to music/podcast.

  Device:
  bq Aquarius E5 HD
  Version:
  OTA 8.5

  Same on MX4 rc-proposed/ota 9

  In addition when answering the call, the call audio is not on the
  headset

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536493/+subscriptions

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

[Kernel-packages] [Bug 1540517] Re: many igb errors in log

[Joseph Salisbury]

Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced.   If this is a
regression, we can perform a kernel bisect to identify the commit that
introduced the problem.


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

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

** Tags added: kernel-da-key

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

Title:
  many igb errors in log

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  [161701.952748] igb: p119p1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: RX/TX
  [161703.000966] igb: p119p1 NIC Link is Down
  [161705.916160] igb: p119p1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: RX/TX
  [161707.080375] igb: p119p1 NIC Link is Down
  [161709.739470] igb: p119p1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: RX/TX

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-76-generic 3.13.0-76.120
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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: Mon Feb  1 19:06:55 2016
  HibernationDevice: RESUME=UUID=ad9e478b-302e-4c7c-83e4-8550df7bf51a
  InstallationDate: Installed on 2016-01-14 (17 days ago)
  InstallationMedia: yavdr64-0.6.0
  IwConfig:
   lono wireless extensions.
   
   p121p1no wireless extensions.
   
   p119p1no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 8087:07db Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, 
Ltd FT232 USB-Serial (UART) IC
   Bus 001 Device 004: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 005: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic 
root=UUID=3eb83753-a535-451b-8cdc-dd0bac58865f ro vmalloc=256m quiet splash 
noresume nohz=off acpi_enforce_resources=lax pcie_aspm=off nomdmonddf 
nomdmonisw vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-76-generic N/A
   linux-backports-modules-3.13.0-76-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   Feb  1 18:04:48 neptun kernel: [257579.340447] igb: p119p1 NIC Link is Down
   Feb  1 18:04:48 neptun kernel: [257579.340605] igb :07:00.0 p119p1: 
Reset adapter
   Feb  1 18:04:54 neptun kernel: [257585.530226] igb: p119p1 NIC Link is Up 
1000 Mbps Full Duplex, Flow Control: RX/TX
  dmi.bios.date: 12/04/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: C2750D4I
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd12/04/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnC2750D4I:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

[Cavsfan]

I could not successfully run the command.

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

Title:
  removing kernels should not require a restart afterward

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  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.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1522404] Re: [Ubuntu 16.04] CAPI flash (cxlflash) driver support for PowerVM virtualized environment

[bugproxy]

** Tags removed: targetmilestone-inin1604
** Tags added: targetmilestone-inin1610

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

Title:
  [Ubuntu 16.04] CAPI flash (cxlflash) driver support for PowerVM
  virtualized environment

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Update the cxlflash driver with new features and platform support.

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

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

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

[Brad Figg]

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-Prepare-package-start:Tuesday, 02. February 2016 19:14 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Tuesday, 02. February 2016 19:14 UTC

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

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

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

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

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

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

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

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

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

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

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

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

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

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


** Tags: block-proposed-trusty kernel-release-tracking-bug trusty

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

** Tags added: block-proposed-trusty

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

** Tags added: trusty

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: 

[Kernel-packages] [Bug 1529232] Re: Scanner not detected over wifi since after 3.13.0-68

[Lucas Partridge]

Canon have come back with: "Unfortunately you need to wait for
scangearmp to update so that it then supports ubuntu version 14.04. We
are not yet aware of a scheduled time of release for this update, the
only thing I can recommend is that you keep an eye on the website to see
when the scangear is updated to support this."

And I notice now at the download link for scangearmp v2.20 it says under
System Requirements: Fedora 18(32bit/64bit) Ubuntu 13.04(32bit/64bit)

So, maybe when Canon update scangearmp to support 14.04 they'll take a
look at this bug...

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

Title:
  Scanner not detected over wifi since after 3.13.0-68

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Please see http://ubuntuforums.org/showthread.php?t=2306464 for
  details.  I'm running 64-bit 14.04 LTS ubuntu.

  When I boot my PC into 3.13.0-68-generic (via the 'ubuntu advanced'
  menu item in grub) I can detect my scanner over wifi using scangearmp.
  However since 3.13.0-70-generic I have not been able to detect my
  scanner over wifi.  My current kernel is 3.13.0-74-generic.  Therefore
  I suspect a regression has occurred between 3.13.0-68-generic and
  3.13.0-70-generic:

  Scanner *is* detected by scangearmp over wifi and it scans documents as 
expected in this version:
  uname -a
  Linux zorro 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  But scanner is *not* detected by scangearmp in this version or later:
  Linux zorro 3.13.0-70-generic #113-Ubuntu SMP Mon Nov 16 18:34:13 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  Note that this happened before some time ago. i.e., The scanner was
  detected over wifi, then not, then it was again some time later. Then
  this latest break occurred again. I suspect successive updates are
  fixing or breaking the detection accordingly.

  $ dpkg -l | grep scangear
  ii  scangearmp-common 2.20-1  
amd64ScanGear MP for Linux.
  ii  scangearmp-mg7100series   2.20-1  
amd64ScanGear MP for Linux.

  Device is Canon Pixma MG7150 (combined printer, scanner, copier). Note
  the printer works fine over wifi; only the scanner is affected.

  I can see from the changelog at 
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_3.13.0-74.118/changelog
 that many changes went into 3.13.0-69.112 but it's not obvious to me which of 
these might have caused the regression.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lucas  1604 F pulseaudio
   /dev/snd/controlC2:  lucas  1604 F pulseaudio
   /dev/snd/controlC0:  lucas  1604 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0140e677-b732-4571-a80a-fc5d7c00359c
  InstallationDate: Installed on 2014-12-05 (387 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7528
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic 
root=UUID=941f5e44-f02e-42f2-ac78-5f6b4b9e98e9 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-74-generic N/A
   linux-backports-modules-3.13.0-74-generic  N/A
   linux-firmware 1.127.19
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-74-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: G31M3-F(MS-7528)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.3:bd06/19/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7528:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-F(MS-7528):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7528
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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

[Kernel-packages] [Bug 1460768] Re: Unable to build kernel 3.19.0-18

[tomoke]

In addition to the link in #24 I found that I also had to enter:
ubuntu/vbox/vboxguest

and do an "ln -s ../r0drv/" to avoid the error:

make[4]: *** No rule to make target 
`ubuntu/vbox/vboxguest/r0drv/alloc-r0drv.o', needed by 
`ubuntu/vbox/vboxguest/vboxguest.o'.  Stop.
make[3]: *** [ubuntu/vbox/vboxguest] Error 2

Was building a: linux-lts-vivid-3.19.0 with the procedure:

make-kpkg -j N --initrd --append-to-version=my-very-own-kernel kernel-
image kernel-headers

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

Title:
  Unable to build kernel 3.19.0-18

Status in One Hundred Papercuts:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There is a bug during compiling kernel version 3.19.0-18.
  First I executed patch file from archive  linux_3.19.0-18.18.diff.gz and 
source https://launchpad.net/ubuntu/+source/linux/3.19.0-18.18

  Then I executed

  make-kpkg --initrd buildpackage

  with attached config file.

  But I got a compiling error:

  CC [M]  ubuntu/vbox/vboxguest/VBoxGuest-linux.o
  In file included from :0:0:
  ././include/linux/kconfig.h:46:1: fatal error: 
./ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h: No such file or 
directory
   #endif /* __LINUX_KCONFIG_H */
   ^
  compilation terminated.
  make[6]: *** [ubuntu/vbox/vboxguest/VBoxGuest-linux.o] Error 1
  make[5]: *** [ubuntu/vbox/vboxguest] Error 2
  make[4]: *** [ubuntu/vbox] Error 2
  make[3]: *** [ubuntu] Error 2

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

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

[Kernel-packages] [Bug 1318551] Re: Kernel Panic - not syncing: An NMI occurred, please see the Integrated Management Log for details.

[Rafael David Tinoco]

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

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

Title:
  Kernel Panic - not syncing: An NMI occurred, please see the Integrated
  Management Log for details.

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Server 14.04 amd64
  Linux global04-jobs2 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

  HW: HP DL380p Gen8 / Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz / 256GB

  
  global04-jobs2 login: [203930.116834] Kernel panic - not syncing: An NMI 
occurred, please see the Integrated Management Log for details.
  [203930.116834] 
  [203930.174171] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-24-generic 
#46-Ubuntu
  [203930.211766] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 02/10/2014
  [203930.249588]  b9792e2c349e 881fbfa06dd0 81715a64 
a02c02d8
  [203930.286130]  881fbfa06e48 8170ec65 0008 
881fbfa06e58
  [203930.322243]  881fbfa06df8  c90029274072 
0001
  [203930.358126] Call Trace:
  [203930.370201][] dump_stack+0x45/0x56
  [203930.407285]  [] panic+0xc8/0x1d7
  [203930.430907]  [] hpwdt_pretimeout+0xdd/0xdd [hpwdt]
  [203930.461560]  [] ? sched_clock+0x9/0x10
  [203930.487228]  [] nmi_handle.isra.3+0x88/0x180
  [203930.516179]  [] do_nmi+0x1bd/0x340
  [203930.540958]  [] end_repeat_nmi+0x1e/0x2e
  [203930.567543]  [] ? intel_idle+0xd8/0x140
  [203930.593928]  [] ? intel_idle+0xd8/0x140
  [203930.619941]  [] ? intel_idle+0xd8/0x140
  [203930.646100]  <>  [] cpuidle_enter_state+0x40/0xc0
  [203930.678933]  [] cpuidle_idle_call+0xb9/0x1f0
  [203930.707409]  [] arch_cpu_idle+0xe/0x30
  [203930.734325]  [] cpu_startup_entry+0xc5/0x290
  [203930.763715]  [] rest_init+0x77/0x80
  [203930.789115]  [] start_kernel+0x438/0x443
  [203930.815958]  [] ? repair_env_string+0x5c/0x5c
  [203930.844461]  [] ? early_idt_handlers+0x120/0x120
  [203930.874616]  [] x86_64_start_reservations+0x2a/0x2c
  [203930.907482]  [] x86_64_start_kernel+0x143/0x152
  [203930.942571] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203930.983822] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203931.026586] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203931.068394] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203931.110558] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203931.151923] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203931.189421] [ cut here ]
  [203931.212832] WARNING: CPU: 0 PID: 0 at 
/build/buildd/linux-3.13.0/kernel/rcu/tree.c:508 
rcu_eqs_exit_common.isra.48+0x110/0x120()
  [203931.269279] Modules linked in: veth bridge bonding dm_thin_pool 
dm_persistent_data dm_bufio dm_bio_prison libcrc32c gpio_ich 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul sb_edac 
glue_helper 8021q ablk_helper cryptd hpwdt hpilo edac_core ioatdma lpc_ich 
psmouse garp serio_raw stp mrp llc acpi_power_meter ipmi_si mac_hid lp parport 
igb i2c_algo_bit tg3 dca ptp hpsa pps_core
  [203931.488907] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-24-generic 
#46-Ubuntu
  [203931.526932] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 02/10/2014
  [203931.559891]  0009 881fbfa03ed0 81715a64 

  [203931.597473]  881fbfa03f08 810676bd 0001 
0046
  [203931.634669]    81c93398 
881fbfa03f18
  [203931.696007] Call Trace:
  [203931.708590][] dump_stack+0x45/0x56
  [203931.737818]  [] warn_slowpath_common+0x7d/0xa0
  [203931.767951]  [] warn_slowpath_null+0x1a/0x20
  [203931.797160]  [] rcu_eqs_exit_common.isra.48+0x110/0x120
  [203931.831002]  [] rcu_irq_enter+0x75/0xa0
  [203931.857924]  [] irq_enter+0x17/0xa0
  [203931.883727]  [] scheduler_ipi+0x4e/0x1d0
  [203931.911444]  [] smp_reschedule_interrupt+0x2a/0x30
  [203931.943438]  [] reschedule_interrupt+0x6d/0x80
  [203931.973619]  [] ? panic+0x196/0x1d7
  [203932.005056]  [] hpwdt_pretimeout+0xdd/0xdd [hpwdt]
  [203932.036609]  [] ? sched_clock+0x9/0x10
  [203932.063827]  [] nmi_handle.isra.3+0x88/0x180
  [203932.093283]  [] do_nmi+0x1bd/0x340
  [203932.118263]  [] end_repeat_nmi+0x1e/0x2e
  [203932.145761]  [] ? intel_idle+0xd8/0x140
  [203932.172752]  [] ? intel_idle+0xd8/0x140
  [203932.199896]  [] ? intel_idle+0xd8/0x140
  [203932.227251]  <>  [] cpuidle_enter_state+0x40/0xc0
  [203932.260781]  [] cpuidle_idle_call+0xb9/0x1f0
  [203932.290037]  [] arch_cpu_idle+0xe/0x30
  [203932.316383]  [] cpu_startup_entry+0xc5/0x290
  [203932.345426]  [] rest_init+0x77/0x80
  [203932.370610]  [] start_kernel+0x438/0x443
  

[Kernel-packages] [Bug 1541058] Re: linux: 4.4.0-3.17 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: New => Fix Released

** Description changed:

  This bug is for tracking the 4.4.0-3.17 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:Tuesday, 02. February 2016 18:30 UTC
  kernel-phase-changed:Tuesday, 02. February 2016 18:30 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 02. February 2016 19:01 UTC
+ proposed-announcement-sent:True

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

Title:
  linux: 4.4.0-3.17 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-3.17 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:Tuesday, 02. February 2016 18:30 UTC
  kernel-phase-changed:Tuesday, 02. February 2016 18:30 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 02. February 2016 19:01 UTC
  proposed-announcement-sent:True

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

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

[Kernel-packages] [Bug 1417580] Re: HP Proliant Servers Advices for Ubuntu Linux (cmdline, panics, firmware options)

[Rafael David Tinoco]

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

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

Title:
  HP Proliant Servers Advices for Ubuntu Linux (cmdline, panics,
  firmware options)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug will try to consolidate all HP Proliant Bugs related to
  kernel panics. Please do not use this to attach cores and/or files.
  Just to provide feedback on the cmdline and its explanations.

  We had several talks (in the last 2 weeks) with HP ROM Engineering
  Team regarding NMIs (non maskable interrupts) being generated in some
  situations:

  1 - NMIs caused during MWAIT instruction (caused by intel_idle module):
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318551)

  HP strongly uses ACPI for its power management features. HP is one of
  the most active members in the ACPI specification group and several
  features for their servers, available through their firmware, are
  heavily ACPI dependent. In the process of solving this and other bugs
  we have discovered that intel_idle module did not use ACPI tables (a
  way of firmware to say to OS what are the p-state/c-state values
  available) but queried processor directly for the available c-states.
  This is, probably, leading the OS to set a c-state (or sub-state) when
  the firmware is not "prepared" to handle. We have provided the
  following cmdline to be used: " intel_idle.max_cstate=0 ". This will
  tell OS to deactivate intel_idle and activate acpi_idle module, which
  gets c-state values to be used from the ACPI tables, given by
  firmware. HP is trying to figure out what is generating the NMIs with
  intel_idle but it might be the case to recommend all HP servers to
  deactivate intel_idle module (in a near future).

  Update:

  1.1 - This case might not be related to MWAIT and/or C-STATES after all. It 
looks like some users were using /dev/watchdog (from HPWDT module) by accident 
and/or without even knowing. 
  (like for example running corosync and using watchdog).

  Check: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837
  for this problem.

  2 - Recently discovered NMIs caused by a BUG in Intel microcode
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416414)

  I've discovered that there is a recent microcode problem in some Intel
  Ivy Bridge microcode regarding a specific BIT not being cleared from
  the PMU (performance counter) register. This can lead to a NMI being
  wrongly handled (like if the PMU register was overflowed, without
  being) and a kernel panic. We have backported the fix to
  Ubuntu-3.13.0-35.61. So it is strongly advised that all Ubuntu Trusty
  Servers, running Xeon® Processor E7 v2, to be upgraded "at least" to
  kernel 3.13.0-35". The following cmdline: " nmi_watchdog=0 " can be
  used to disable regular x86 watchdog and use HP one but they don't
  recommend this to be the "default" cmdline. HP was advised by
  Canonical regarding Intel Errata # and that recommended workaround is
  a fix in firmware. Canonical has provided a kernel patch to
  "workaround" the issue in non-patched firmware (yet to be released by
  HP probably).

  3 - X2APIC support for HP Proliant Servers
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398497)

  During this investigation we had to clarify with HP ROM Engineering
  Team whether this servers support X2APIC or not. It was told to us, by
  HP, that all Gen8 (and more recent generations) do support X2APIC but
  they still "ask" the OS to opt-out from X2APIC (not to use X2APIC).
  Running the PIC (programmable interrupt controller) in XAPIC mode
  might not be compatible with firmware if the CPU supports X2APIC
  because of one of the only features that differs XAPIC from X2APIC:
  IRQ remapping (for virtualization, basically). So it is recommended
  that on all HP Proliant Servers Gen8, or newer, to use the following
  cmdline: " intremap=no_x2apic_optout ".

  4 - Proliant servers can fail to initialize cpufreq for some cores when 
having collaborative power control enabled into firmware
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447763)

  ==

  Anyone affected, please provide proper feedback in this bug regarding
  the use of those cmdlines (and kernel version) and tell me if new
  kernel panics (regarding NMIs and/or APIC) happened on this Server
  Family. We are getting feedback from community that these options are
  being enough to avoid the Proliant Server Family to have kernel panics
  and they might be released as a "public recommendation" for HP HW
  compatibility soon.

  Thank you

  Rafael Tinoco

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

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

[Kernel-packages] [Bug 1536397] Re: [nForce2] pata_amd pata_acpi can't load

[Sergey]

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

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

Title:
  [nForce2] pata_amd pata_acpi can't load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The system is 15.04.

  Since the 3.19.0-33-generic system fall to (initramfs) prompt. Now I
  can boot the system only with 3.19.0-15-generic.

  I always update the system and check new kernel packages, but they
  have the same error.

  In dmesg I found:

  pata_amd :00:09.0: can't enable device: BAR 0 [io 0x01f0-0x01f7] not 
claimed
  pata_amd: probe of :00:09.0 failed with error -22

  And analogical for pata_acpi.

  P.S. I have a suspicion to the option CONFIG_PCI_BUS_ADDR_T_64BIT=y . But I'm 
not linux kernel guru.
  --- 
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paly   2672 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=d4137d34-9c31-41b2-9557-b14531398f02
  InstallationDate: Installed on 2015-11-14 (67 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release i386 (20150422.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=/dev/sda2 ro rootflags=subvol=@ quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  vivid
  UdevLog: Error: [Errno 2] Немає такого файла або каталогу: '/var/log/udev'
  Uname: Linux 3.19.0-15-generic i686
  UpgradeStatus: Upgraded to vivid on 2015-12-05 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/07/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: nVidia-nForce
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/07/2004:svn:pn:pvr:rvn:rnnVidia-nForce:rvr:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1517951] Re: CVE-2013-7446

[Steve Beattie]

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

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

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

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

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

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

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

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

** Changed in: linux-raspi2 (Ubuntu Wily)
   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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1517951

Title:
  CVE-2013-7446

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

[Kernel-packages] [Bug 1540720] Re: linux-ti-omap4: 3.2.0-1477.100 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

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

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

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

Bug description:
  This bug is for tracking the 3.2.0-1477.100 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, 02. February 2016 04:01 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 02. February 2016 04:01 UTC
  kernel-stable-master-bug:1540538
  kernel-stable-Certification-testing-end:Tuesday, 02. February 2016 16:01 UTC

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

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

[Kernel-packages] [Bug 1541120] [NEW] [Hyper-V] PCI Passthrough

[Joshua R. Poulson]

Public bug reported:

Jake Oshins (Microsoft) has submitted upstream the PCI Passthrough
feature, and while it is not yet accepted upstream (because of the
effect on multiple trees and affects PCI), Microsoft would like
Canonical to consider its inclusion in Ubuntu 16.04 and beyond. The
rounds of feedback on the patches are winding down, so it is a good time
to consider them.

All of the submitted files are in the attached thread, but not all are
committed to Linus's tree as of 4.5-rc1.

This feature is needed for supporting SR-IOV and GPU passthrough on
Hyper-V.

The 10th iteration of the upstream submission is available on lkml:

https://lkml.org/lkml/2015/12/10/553

Fromjakeo@microsof ...
Subject [PATCH v10 0/7] PCI: hv: New paravirtual PCI front-end for Hyper-V VMs
DateThu, 10 Dec 2015 17:52:56 +
From: Jake Oshins 

This version of the patch series removes warning when compiling x86
32-bit while still making it build cleanly for x64.

First, export functions that allow correlating Hyper-V virtual processors
and Linux cpus, along with the means for invoking a hypercall that targets
interrupts at chosen vectors on specific cpus.

Second, mark various parts of IRQ domain related code as exported, so that
this PCI front-end can implement an IRQ domain as part of a module. (The
alternative would be to pull all tyhis into the kernel, which would pull
in a lot of other Hyper-V related code, as this IRQ domain depends on
vmbus.ko.)

Third, modify PCI so that new root PCI buses can be marked with an associated
fwnode_handle, and so that root PCI buses can look up their associated IRQ
domain by that handle.

Fourth, introduce a new driver, hv_pcifront, which exposes root PCI buses in
a Hyper-V VM. These root PCI buses expose real PCIe device, or PCI Virtual
Functions.

Jake Oshins (7):
  drivers:hv: Export a function that maps Linux CPU num onto Hyper-V
proc num
  drivers:hv: Export hv_do_hypercall()
  PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
  PCI: Add fwnode_handle to pci_sysdata
  PCI: irqdomain: Look up IRQ domain by fwnode_handle
  drivers:hv: Define the channel type of Hyper-V PCI Express
pass-through
  PCI: hv: New paravirtual PCI front-end for Hyper-V VMs

 MAINTAINERS | 1 +
 arch/x86/include/asm/msi.h | 6 +
 arch/x86/include/asm/pci.h | 15 +
 arch/x86/kernel/apic/msi.c | 8 +-
 arch/x86/kernel/apic/vector.c | 2 +
 drivers/hv/hv.c | 20 +-
 drivers/hv/hyperv_vmbus.h | 2 +-
 drivers/hv/vmbus_drv.c | 17 +
 drivers/pci/Kconfig | 7 +
 drivers/pci/host/Makefile | 1 +
 drivers/pci/host/hv_pcifront.c | 2249 
 drivers/pci/msi.c | 4 +
 drivers/pci/probe.c | 15 +
 include/linux/hyperv.h | 14 +
 include/linux/pci.h | 4 +
 kernel/irq/chip.c | 1 +
 kernel/irq/irqdomain.c | 4 +
 17 files changed, 2356 insertions(+), 14 deletions(-)
 create mode 100644 drivers/pci/host/hv_pcifront.c

Accepted commits so far in 4.5-rc1:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a108393dbf764efb2405f21ca759806c65b8bc16
 drivers:hv: Export the API to invoke a hypercall on Hyper-V
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=619848bd074343ff2bdeeafca0be39748f6da372
 drivers:hv: Export a function that maps Linux CPU num onto Hyper-V proc num
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3053c762444a83ec6a8777f9476668b23b8ab180
 drivers:hv: Define the channel type for Hyper-V PCI Express pass-through
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=40f26f3168bf7a4da490db308dc0bd9f9923f41f
 drivers:hv: Allow for MMIO claims that span ACPI _CRS records
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a4289dc2ec3a5821076a78ee9678909b4eff297e
 genirq/msi: Export functions to allow MSI domains in modules
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c8f3e518d3444ee9200a4987421fcee60f768f11
 x86/irq: Export functions to allow MSI domains in modules

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

Title:
  [Hyper-V] PCI Passthrough

Status in linux package in Ubuntu:
  New

Bug description:
  Jake Oshins (Microsoft) has submitted upstream the PCI Passthrough
  feature, and while it is not yet accepted upstream (because of the
  effect on multiple trees and affects PCI), Microsoft would like
  Canonical to consider its inclusion in Ubuntu 16.04 and beyond. The
  rounds of feedback on the patches are winding down, so it is a good
  time to consider them.

  All of the submitted files are in the attached thread, but not all are
  committed to Linus's tree as of 4.5-rc1.

  This feature is needed for supporting SR-IOV and GPU passthrough on
  Hyper-V.

  The 10th iteration of the 

[Kernel-packages] [Bug 1437492] Re: boot stalls on USB detection errors

[Antonio Vicent]

For me the problem seems to have been resolved with  Ubuntu 15.10 and
kernel 4.2.0-23

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

Title:
  boot stalls on USB detection errors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system boots slow. I investigated this and it seems 
systemd-udev-settle.service is the culprit.
  My system runs ext4 with GPT on UEFI.
  I do not use encryption or LVM.

  $ journalctl -u systemd-udev-settle
  -- Logs begin at fri 2015-03-27 19:03:06 CET, end at fri 2015-03-27 22:06:32 
CET. --
  mar 27 19:03:42 hostname systemd[1]: Started udev Wait for Complete Device 
Initialization.

  $ systemd-analyze
  Startup finished in 14.865s (firmware) + 11.133s (loader) + 6.127s (kernel) + 
42.079s (userspace) = 1min 14.206s

  $ systemd-analyze critical-chain
  http://paste.ubuntu.com/10691416/

  $ systemd-analyze blame
  36.013s systemd-udev-settle.service
  http://paste.ubuntu.com/10691314/

  $ systemctl show systemd-udev-settle.service -p RequiredBy
  RequiredBy=

  $ systemctl show systemd-udev-settle.service -p WantedBy
  WantedBy=friendly-recovery.service

  $ systemd-analyze plot > boot.svg
  http://imgh.us/boot_1.svg

  $ systemd-analyze dump
  http://paste.ubuntu.com/10691856/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Mar 27 22:05:28 2015
  InstallationDate: Installed on 2013-12-26 (455 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

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

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 02. February 2016 06:02 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 02. February 2016 06:02 UTC
  kernel-stable-master-bug:1540559

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

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

[Kernel-packages] [Bug 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

[SuperNoa]

Thank you, now wifi is working on my Alienware 15 R2 too!

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

Title:
  Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ---

  STATUS:

  Currently there is a fix for this problem in post #22 (originally post
  #19, but reposted due to command typos!) which seems to have fixed the
  issue for many. This bug is unique to revision 32 of the card
  [168c:003e], fixes for older revisions don't seem to work.

  There are a couple of issues regarding the fix for some people (not
  all):

  1. Wireless works, but network throughput stops some time after
  connecting to access point

  2. Bluetooth communications take a noticeable performance hit when
  transferring something over WiFi

  ---

  I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an 
Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card 
doesn't work in it or 16.04.
  The card has the device id 168c:003e as many other cards, for example the 
Qualcomm Atheros Killer 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a 
newer revision number (32) and the suggested fixes work only partially and the 
wireless is unusable.

  The computer has just been released this summer and is Intel Skylake
  -based.

  I've tried the patch from bug 1383184, which has a fix for the card revision 
20:
  Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch 
files:
  board.bin
  firmware-4.bin
  notice_ath10k_firmware-4.txt

  ath10k_pci succeeds in loading the firmware, but it seems that the
  firmware is not working correctly:

  dmesg | grep ath
  [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 
reset_mode 0
  [5.678420] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/cal-pci-:07:00.0.bin failed with error -2
  [5.678773] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2
  [5.678781] ath10k_pci :07:00.0: failed to load spec board file, 
falling back to generic: -2
  [5.679445] ath10k_pci :07:00.0: Direct firmware load for 
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 
0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 
4 htt 3.26 wmi 4 cal otp max_sta 32
  [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 
testmode 0
  [8.200607] ath: EEPROM regdomain: 0x6c
  [8.200614] ath: EEPROM indicates we should expect a direct regpair map
  [8.200619] ath: Country alpha2 being used: 00
  [8.200621] ath: Regpair used: 0x6c
  [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0
  [   13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   16.461416] ath10k_pci :07:00.0: could not suspend target (-11)
  [   24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   27.759534] ath10k_pci :07:00.0: could not suspend target (-11)
  [   36.046205] ath10k_pci :07:00.0: failed to set arp ac override 
parameter: -11
  [   39.045729] ath10k_pci :07:00.0: could not suspend target (-11)
  [   47.344304] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   50.343794] ath10k_pci :07:00.0: could not suspend target (-11)
  [   58.630534] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   61.629936] ath10k_pci :07:00.0: could not suspend target (-11)
  [   69.920624] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   72.920132] ath10k_pci :07:00.0: could not suspend target (-11)
  [   81.206812] ath10k_pci :07:00.0: failed to enable dynamic BW: -11
  [   84.206218] ath10k_pci :07:00.0: could not suspend target (-11)
  ...

  Then it just constantly prints the last two messages on and on.
  I can weirdly enough see the card in iwconfig:
  wlp7s0IEEE 802.11abgn  ESSID:off/any
    Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm
    Retry short limit:7   RTS thr:off   Fragment thr:off
    Power Management:off

  And I can see the wireless-icon in the toolbar, but scanning for
  access points or trying to connect to one doesn't work.

  This is the furthest I've gotten. I suspect this card needs a new
  firmware in ath10k?

  ---
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1230 F 

[Kernel-packages] [Bug 1437492] Re: boot stalls on USB detection errors

[Awesome Donkey]

It still happens to me.

Is there an open bug report we can follow on the kernel mailing list? If
not, it might be worth posting there about this.

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

Title:
  boot stalls on USB detection errors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system boots slow. I investigated this and it seems 
systemd-udev-settle.service is the culprit.
  My system runs ext4 with GPT on UEFI.
  I do not use encryption or LVM.

  $ journalctl -u systemd-udev-settle
  -- Logs begin at fri 2015-03-27 19:03:06 CET, end at fri 2015-03-27 22:06:32 
CET. --
  mar 27 19:03:42 hostname systemd[1]: Started udev Wait for Complete Device 
Initialization.

  $ systemd-analyze
  Startup finished in 14.865s (firmware) + 11.133s (loader) + 6.127s (kernel) + 
42.079s (userspace) = 1min 14.206s

  $ systemd-analyze critical-chain
  http://paste.ubuntu.com/10691416/

  $ systemd-analyze blame
  36.013s systemd-udev-settle.service
  http://paste.ubuntu.com/10691314/

  $ systemctl show systemd-udev-settle.service -p RequiredBy
  RequiredBy=

  $ systemctl show systemd-udev-settle.service -p WantedBy
  WantedBy=friendly-recovery.service

  $ systemd-analyze plot > boot.svg
  http://imgh.us/boot_1.svg

  $ systemd-analyze dump
  http://paste.ubuntu.com/10691856/

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Mar 27 22:05:28 2015
  InstallationDate: Installed on 2013-12-26 (455 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1318551] Re: Kernel Panic - not syncing: An NMI occurred, please see the Integrated Management Log for details.

[Rafael David Tinoco]

** Tags removed: kernel-key

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

Title:
  Kernel Panic - not syncing: An NMI occurred, please see the Integrated
  Management Log for details.

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Server 14.04 amd64
  Linux global04-jobs2 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

  HW: HP DL380p Gen8 / Intel(R) Xeon(R) CPU E5-2667 v2 @ 3.30GHz / 256GB

  
  global04-jobs2 login: [203930.116834] Kernel panic - not syncing: An NMI 
occurred, please see the Integrated Management Log for details.
  [203930.116834] 
  [203930.174171] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-24-generic 
#46-Ubuntu
  [203930.211766] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 02/10/2014
  [203930.249588]  b9792e2c349e 881fbfa06dd0 81715a64 
a02c02d8
  [203930.286130]  881fbfa06e48 8170ec65 0008 
881fbfa06e58
  [203930.322243]  881fbfa06df8  c90029274072 
0001
  [203930.358126] Call Trace:
  [203930.370201][] dump_stack+0x45/0x56
  [203930.407285]  [] panic+0xc8/0x1d7
  [203930.430907]  [] hpwdt_pretimeout+0xdd/0xdd [hpwdt]
  [203930.461560]  [] ? sched_clock+0x9/0x10
  [203930.487228]  [] nmi_handle.isra.3+0x88/0x180
  [203930.516179]  [] do_nmi+0x1bd/0x340
  [203930.540958]  [] end_repeat_nmi+0x1e/0x2e
  [203930.567543]  [] ? intel_idle+0xd8/0x140
  [203930.593928]  [] ? intel_idle+0xd8/0x140
  [203930.619941]  [] ? intel_idle+0xd8/0x140
  [203930.646100]  <>  [] cpuidle_enter_state+0x40/0xc0
  [203930.678933]  [] cpuidle_idle_call+0xb9/0x1f0
  [203930.707409]  [] arch_cpu_idle+0xe/0x30
  [203930.734325]  [] cpu_startup_entry+0xc5/0x290
  [203930.763715]  [] rest_init+0x77/0x80
  [203930.789115]  [] start_kernel+0x438/0x443
  [203930.815958]  [] ? repair_env_string+0x5c/0x5c
  [203930.844461]  [] ? early_idt_handlers+0x120/0x120
  [203930.874616]  [] x86_64_start_reservations+0x2a/0x2c
  [203930.907482]  [] x86_64_start_kernel+0x143/0x152
  [203930.942571] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203930.983822] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203931.026586] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203931.068394] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203931.110558] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203931.151923] ERST: [Firmware Warn]: Firmware does not respond in time.
  [203931.189421] [ cut here ]
  [203931.212832] WARNING: CPU: 0 PID: 0 at 
/build/buildd/linux-3.13.0/kernel/rcu/tree.c:508 
rcu_eqs_exit_common.isra.48+0x110/0x120()
  [203931.269279] Modules linked in: veth bridge bonding dm_thin_pool 
dm_persistent_data dm_bufio dm_bio_prison libcrc32c gpio_ich 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul sb_edac 
glue_helper 8021q ablk_helper cryptd hpwdt hpilo edac_core ioatdma lpc_ich 
psmouse garp serio_raw stp mrp llc acpi_power_meter ipmi_si mac_hid lp parport 
igb i2c_algo_bit tg3 dca ptp hpsa pps_core
  [203931.488907] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-24-generic 
#46-Ubuntu
  [203931.526932] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 02/10/2014
  [203931.559891]  0009 881fbfa03ed0 81715a64 

  [203931.597473]  881fbfa03f08 810676bd 0001 
0046
  [203931.634669]    81c93398 
881fbfa03f18
  [203931.696007] Call Trace:
  [203931.708590][] dump_stack+0x45/0x56
  [203931.737818]  [] warn_slowpath_common+0x7d/0xa0
  [203931.767951]  [] warn_slowpath_null+0x1a/0x20
  [203931.797160]  [] rcu_eqs_exit_common.isra.48+0x110/0x120
  [203931.831002]  [] rcu_irq_enter+0x75/0xa0
  [203931.857924]  [] irq_enter+0x17/0xa0
  [203931.883727]  [] scheduler_ipi+0x4e/0x1d0
  [203931.911444]  [] smp_reschedule_interrupt+0x2a/0x30
  [203931.943438]  [] reschedule_interrupt+0x6d/0x80
  [203931.973619]  [] ? panic+0x196/0x1d7
  [203932.005056]  [] hpwdt_pretimeout+0xdd/0xdd [hpwdt]
  [203932.036609]  [] ? sched_clock+0x9/0x10
  [203932.063827]  [] nmi_handle.isra.3+0x88/0x180
  [203932.093283]  [] do_nmi+0x1bd/0x340
  [203932.118263]  [] end_repeat_nmi+0x1e/0x2e
  [203932.145761]  [] ? intel_idle+0xd8/0x140
  [203932.172752]  [] ? intel_idle+0xd8/0x140
  [203932.199896]  [] ? intel_idle+0xd8/0x140
  [203932.227251]  <>  [] cpuidle_enter_state+0x40/0xc0
  [203932.260781]  [] cpuidle_idle_call+0xb9/0x1f0
  [203932.290037]  [] arch_cpu_idle+0xe/0x30
  [203932.316383]  [] cpu_startup_entry+0xc5/0x290
  [203932.345426]  [] rest_init+0x77/0x80
  [203932.370610]  [] start_kernel+0x438/0x443
  [203932.398445]  [] ? 

[Kernel-packages] [Bug 1533043] Re: AUFS can hang up; Please update to v20160111

[Ryan Sundberg]

Tested 3.19.0-49-generic #55~14.04.1hf1533043v20160201b1-Ubuntu on bare
metal.

Works like a charm. What a great effort by everyone involved. Thanks a
lot!

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

Title:
  AUFS can hang up; Please update to v20160111

Status in linux package in Ubuntu:
  In Progress
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:
  In Progress
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in linux-lts-utopic source package in Xenial:
  Invalid

Bug description:
  AUFS  can hang up (more precisely, produces unkillable processes) with some 
kernels that contain the commit 296291cdd1629c308114504b850dc343eabc278.
  - 14.04LTS:  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=b8702f3cf9c06914476fb3206039131c2c3d8450
  - 15.04: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=6b08592b8acc677d5b9bb7986343fdd6e0ad3303
  - 15.10: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-wily.git/commit/?id=4d291df30fb7a94d13c6d38addf8d85d38f0111b

  Many docker users have been experiencing this issue:
  https://github.com/docker/docker/issues/18180

  
  The issue has been fixed since AUFS v20160111: 
http://permalink.gmane.org/gmane.linux.file-systems.aufs.user/5345
  So I suggest updating AUFS to v20160111.

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

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

[Kernel-packages] [Bug 1530406] Re: CVE-2015-8552

[Steve Beattie]

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

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

Title:
  CVE-2015-8552

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

[Kernel-packages] [Bug 1530404] Re: CVE-2015-8551

[Steve Beattie]

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

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

Title:
  CVE-2015-8551

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

[Kernel-packages] [Bug 1538673] Re: Atheros Qualcomm Killer N1525 Wireless-AC Cannot Connect to ac/5GHz

[Corey]

The log in the attachment is not what I had in the description
originally, you can see this by viewing the original description, but if
its not helping anyone anyway I will just remove it.

The bug was not fixed upstream, will add tags

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

** Description changed:

  Ubuntu Gnome 15.10
  
  I do not know what package this error is a part of or if it is even part
  of a package as I am not familiar enough with linux.  I know it is the
  ath10k_pci module.
  
  Expected: The wifi would connect to the access point.
  
  Actual: Firmware crashes twice then NetworkManager times out the
  connection.
  
  This problem only occurs when either connecting to an 802.11ac or a 5GHz
  access point.  I do not have the equipment and or knowledge to be able
  to narrow it down any to one specifically.  It does connect to my
  phone's hotspot on 2.4GHz (I think it is N?) but will not when the
  hotspot is set to 5GHz (Definitely AC).  It also will not connect to my
  school's AC wireless network.
- 
- Here is the system log from the start of attempting to connect to the 
connection finally timing out (I censored some personal data):
- 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1538673/+attachment/4558010/+files/log
  
  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polomoto   1168 F pulseaudio
   /dev/snd/controlC1:  polomoto   1168 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=5018c1c5-f5d2-45e3-a3da-4e74bd9b9131
  InstallationDate: Installed on 2016-01-22 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: Micro-Star International Co., Ltd. GS60 2QE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=b7920bb6-c35c-43c5-82be-c195753bc15f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16H5IMS.104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16H5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16H5IMS.104:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H5:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GS60 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC Cannot Connect to ac/5GHz

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Gnome 15.10

  I do not know what package this error is a part of or if it is even
  part of a package as I am not familiar enough with linux.  I know it
  is the ath10k_pci module.

  Expected: The wifi would connect to the access point.

  Actual: Firmware crashes twice then NetworkManager times out the
  connection.

  This problem only occurs when either connecting to an 802.11ac or a
  5GHz access point.  I do not have the equipment and or knowledge to be
  able to narrow it down any to one specifically.  It does connect to my
  phone's hotspot on 2.4GHz (I think it is N?) but will not when the
  hotspot is set to 5GHz (Definitely AC).  It also will not connect to
  my school's AC wireless network.

  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polomoto   1168 F pulseaudio
   /dev/snd/controlC1:  polomoto   1168 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=5018c1c5-f5d2-45e3-a3da-4e74bd9b9131
  InstallationDate: Installed on 2016-01-22 (4 days ago)
  

[Kernel-packages] [Bug 1530958] Re: CVE-2015-8553

[Steve Beattie]

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

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

Title:
  CVE-2015-8553

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

[Kernel-packages] [Bug 1454286] Re: BNX2X firmware an hang on Trusty (3.13) and Utopic (3.16).

[Dan Streetman]

Update: after some discussion, I'm going to pull specific commits into
the trusty 3.13 bnx2x driver, instead of pulling the entire 3.19 bnx2x
driver back.  I'll update this bug when I have something new to test.

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

Title:
  BNX2X firmware an hang on Trusty (3.13) and Utopic (3.16).

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress

Bug description:
  It was brought to my attention that BNX2X FIRMWARE is causing HW hangs
  on kernels 3.13 and 3.16 (until next power-cycle):

  Messages like this one:

  """
  Mar 30 13:42:05 host kernel: [3986360.755781] device em3 left promiscuous mode
  Mar 30 13:42:05 host kernel: [3986360.755849] br1: port 1(em3) entered 
disabled state
  Mar 30 13:42:05 host kernel: [3986360.756305] IPv6: ADDRCONF(NETDEV_UP): em3: 
link is not ready
  Mar 30 13:42:08 host kernel: [3986363.354376] device em3 entered promiscuous 
mode
  Mar 30 13:42:08 host kernel: [3986363.376093] bnx2x: 
[bnx2x_open:11791(em3)]Recovery flow hasn't been properly completed yet. Try 
again later.
  Mar 30 13:42:08 host kernel: [3986363.376093] If you still see this message 
after a few retries then power cycle is required.
  Mar 30 13:42:08 host kernel: [3986363.420113] bnx2x: 
[bnx2x_open:11791(em3)]Recovery flow hasn't been properly completed yet. Try 
again later.
  Mar 30 13:42:08 host kernel: [3986363.420113] If you still see this message 
after a few retries then power cycle is required.
  Mar 30 13:42:08 host kernel: [3986363.443840] IPv6: ADDRCONF(NETDEV_UP): br1: 
link is not ready
  """

  Are likely to be given in syslog whenever this happens.

  WORKAROUND: After providing the user a "linux-lts-vivid" and an
  updated linux-firmware package
  (https://launchpad.net/~inaddy/+archive/ubuntu/sf00080928/) the issue
  was fixed after package installation and power-cycle -> Power cycle is
  needed since previous firmware hangs HW until it is shutdown.

  My comments:

  """
  Actually after reading the Changelog for FW 7.10.51 (specifically the part 
"Chip may stall in very rare cases under heavy traffic with FW GRO enabled.") I 
think we might need to upgrade not only the FIRMWARE but also the DRIVER. 

  commit 626041248d3fb5b2fca5c9af172f00fa3bb6dcfe 
  Author: Yuval Mintz  
  Date: Sun Aug 17 16:47:46 2014 +0300 

  bnx2x: Update driver version to 1.710.5

  commit e42780b66aab88d3a82b6087bcd6095b90eecde7 
  Author: Dmitry Kravkov  
  Date: Sun Aug 17 16:47:43 2014 +0300 

  bnx2x: Utilize FW 7.10.51

  Observations:

  
inaddy@alien:~/Bugs/customer/sf00080928/sources/trusty/linux-firmware-1.127.11$ 
find . | grep bnx2x 
  ./bnx2x 
  ./bnx2x/bnx2x-e1h-7.8.19.0.fw 
  ./bnx2x/bnx2x-e1-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.8.19.0.fw 
  ./bnx2x/bnx2x-e2-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1h-7.8.17.0.fw 
  ./bnx2x/bnx2x-e2-7.8.19.0.fw 

  
inaddy@alien:~/Bugs/customer/sf00080928/sources/utopic/linux-firmware-1.138.1$ 
find . | grep bnx2x 
  ./bnx2x 
  ./bnx2x/bnx2x-e1h-7.8.19.0.fw 
  ./bnx2x/bnx2x-e1-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.8.19.0.fw 
  ./bnx2x/bnx2x-e2-7.10.51.0.fw 
  ./bnx2x/bnx2x-e1h-7.10.51.0.fw 
  ./bnx2x/bnx2x-e2-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1h-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.10.51.0.fw 
  ./bnx2x/bnx2x-e2-7.8.19.0.fw 

  Firmware 7.10.51 is already present in Utopic but the commit to support it is 
only in 3.18.  It might be feasible to backport it to 3.16 (and use HWE) but 
not sure about 3.13 (to be resolved if this new firmware/driver fixes the 
issue).
  """

  I'll provide more comments right after my backport attempt (of this
  new version) is made.

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

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

[Kernel-packages] [Bug 1521273] Re: CVE-2015-8374

[Steve Beattie]

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

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

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

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

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

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

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

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

** Changed in: linux-raspi2 (Ubuntu Wily)
   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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1521273

Title:
  CVE-2015-8374

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

[Kernel-packages] [Bug 1530403] Re: CVE-2015-8550

[Steve Beattie]

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

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

Title:
  CVE-2015-8550

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

[Kernel-packages] [Bug 1525570] Re: CVE-2015-8543

[Steve Beattie]

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

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

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

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

** Changed in: linux-raspi2 (Ubuntu Wily)
   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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1525570

Title:
  CVE-2015-8543

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

[Kernel-packages] [Bug 1526958] Re: CVE-2015-8569

[Steve Beattie]

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

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

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

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

** Changed in: linux-raspi2 (Ubuntu Wily)
   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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1526958

Title:
  CVE-2015-8569

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

[Kernel-packages] [Bug 1530407] Re: CVE-2015-8575

[Steve Beattie]

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

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

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

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

** Changed in: linux-raspi2 (Ubuntu Wily)
   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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1530407

Title:
  CVE-2015-8575

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

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

[Steve Beattie]

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

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

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

Title:
  CVE-2015-8785

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

[Kernel-packages] [Bug 1539001] Re: CVE-2015-8787

[Steve Beattie]

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

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

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

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

** Changed in: linux-raspi2 (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  CVE-2015-8787

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

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

[Brad Figg]

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

apport-collect 1541120

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

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

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

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

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

Title:
  [Hyper-V] PCI Passthrough

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Jake Oshins (Microsoft) has submitted upstream the PCI Passthrough
  feature, and while it is not yet accepted upstream (because of the
  effect on multiple trees and affects PCI), Microsoft would like
  Canonical to consider its inclusion in Ubuntu 16.04 and beyond. The
  rounds of feedback on the patches are winding down, so it is a good
  time to consider them.

  All of the submitted files are in the attached thread, but not all are
  committed to Linus's tree as of 4.5-rc1.

  This feature is needed for supporting SR-IOV and GPU passthrough on
  Hyper-V.

  The 10th iteration of the upstream submission is available on lkml:

  https://lkml.org/lkml/2015/12/10/553

  From  jakeo@microsof ...
  Subject   [PATCH v10 0/7] PCI: hv: New paravirtual PCI front-end for 
Hyper-V VMs
  Date  Thu, 10 Dec 2015 17:52:56 +
  From: Jake Oshins 

  This version of the patch series removes warning when compiling x86
  32-bit while still making it build cleanly for x64.

  First, export functions that allow correlating Hyper-V virtual processors
  and Linux cpus, along with the means for invoking a hypercall that targets
  interrupts at chosen vectors on specific cpus.

  Second, mark various parts of IRQ domain related code as exported, so that
  this PCI front-end can implement an IRQ domain as part of a module. (The
  alternative would be to pull all tyhis into the kernel, which would pull
  in a lot of other Hyper-V related code, as this IRQ domain depends on
  vmbus.ko.)

  Third, modify PCI so that new root PCI buses can be marked with an associated
  fwnode_handle, and so that root PCI buses can look up their associated IRQ
  domain by that handle.

  Fourth, introduce a new driver, hv_pcifront, which exposes root PCI buses in
  a Hyper-V VM. These root PCI buses expose real PCIe device, or PCI Virtual
  Functions.

  Jake Oshins (7):
drivers:hv: Export a function that maps Linux CPU num onto Hyper-V
  proc num
drivers:hv: Export hv_do_hypercall()
PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
PCI: Add fwnode_handle to pci_sysdata
PCI: irqdomain: Look up IRQ domain by fwnode_handle
drivers:hv: Define the channel type of Hyper-V PCI Express
  pass-through
PCI: hv: New paravirtual PCI front-end for Hyper-V VMs

   MAINTAINERS | 1 +
   arch/x86/include/asm/msi.h | 6 +
   arch/x86/include/asm/pci.h | 15 +
   arch/x86/kernel/apic/msi.c | 8 +-
   arch/x86/kernel/apic/vector.c | 2 +
   drivers/hv/hv.c | 20 +-
   drivers/hv/hyperv_vmbus.h | 2 +-
   drivers/hv/vmbus_drv.c | 17 +
   drivers/pci/Kconfig | 7 +
   drivers/pci/host/Makefile | 1 +
   drivers/pci/host/hv_pcifront.c | 2249 

   drivers/pci/msi.c | 4 +
   drivers/pci/probe.c | 15 +
   include/linux/hyperv.h | 14 +
   include/linux/pci.h | 4 +
   kernel/irq/chip.c | 1 +
   kernel/irq/irqdomain.c | 4 +
   17 files changed, 2356 insertions(+), 14 deletions(-)
   create mode 100644 drivers/pci/host/hv_pcifront.c

  Accepted commits so far in 4.5-rc1:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a108393dbf764efb2405f21ca759806c65b8bc16
 drivers:hv: Export the API to invoke a hypercall on Hyper-V
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=619848bd074343ff2bdeeafca0be39748f6da372
 drivers:hv: Export a function that maps Linux CPU num onto Hyper-V proc num
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3053c762444a83ec6a8777f9476668b23b8ab180
 drivers:hv: Define the channel type for Hyper-V PCI Express pass-through
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=40f26f3168bf7a4da490db308dc0bd9f9923f41f
 drivers:hv: Allow for MMIO claims that span ACPI _CRS records
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a4289dc2ec3a5821076a78ee9678909b4eff297e
 genirq/msi: Export functions to allow MSI domains in modules
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c8f3e518d3444ee9200a4987421fcee60f768f11
 x86/irq: Export functions to allow MSI domains in modules

To manage notifications about 

[Kernel-packages] [Bug 1530400] Re: CVE-2015-7550

[Steve Beattie]

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

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

** Changed in: linux-raspi2 (Ubuntu Wily)
   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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1530400

Title:
  CVE-2015-7550

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

[Kernel-packages] [Bug 1524930] Re: "ACPI PCC probe failed" message is an error message when it should be debug

[Colin Ian King]

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

Title:
  "ACPI PCC probe failed" message is an error message when it should be
  debug

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

Bug description:
  [SRU Justification][Vivid]

  Users of Ubuntu Vivid are seeing a seemingly alarming kernel failure
  message "ACPI PCC probe failed" when in fact it is just a debug
  message informing the kernel developers that a probe for an ACPI PCC
  mailbox was not successful (which is just a debug only message) and
  not a failure one needs to worry about.   This message is asked about
  frequently on askubuntu.com, so it is alarming quite a few users, c.f.
  : http://askubuntu.com/questions/708215/1-037533-acpi-pcc-probe-
  failed.

  This fix landed in Wily, and the driver with the alarming message only
  affects Vivid.

  [Fix]
  Upstream commit efd756daf4ddae3cec2404c4e0b680b7cfdd6a45 ("ACPI / PCC: Use 
pr_debug() for debug messages in pcc_init()")

  [Testcase]

  Boot a machine without the PCC feature, without the fix one sees the
  error message in the kernel log. With the fix, this error is now a
  warning.  Note: This only affects Vivid.

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

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

[Kernel-packages] [Bug 1530956] Re: CVE-2015-7513

[Steve Beattie]

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

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

** Changed in: linux-raspi2 (Ubuntu Wily)
   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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1530956

Title:
  CVE-2015-7513

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

[Kernel-packages] [Bug 1508329] Re: CVE-2015-7799

[Steve Beattie]

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

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

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

Title:
  CVE-2015-7799

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

[Kernel-packages] [Bug 1510805] Re: CVE-2015-7990

[Steve Beattie]

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

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

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

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

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

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

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

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

** Changed in: linux-raspi2 (Ubuntu Wily)
   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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1510805

Title:
  CVE-2015-7990

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

[Kernel-packages] [Bug 1454286] Re: BNX2X firmware an hang on Trusty (3.13) and Utopic (3.16).

[Dan Streetman]

For reference, to repeat the commit hashes that Rafael mentioned above
(in standard reverse chronological order):

ddstreet@toughbook:~/linux$ git show 6260412 | head -5
commit 626041248d3fb5b2fca5c9af172f00fa3bb6dcfe
Author: Yuval Mintz 
Date:   Sun Aug 17 16:47:46 2014 +0300

bnx2x: Update driver version to 1.710.51
ddstreet@toughbook:~/linux$ git show 0c23ad3 | head -5
commit 0c23ad37a220b6a58b90e36203fe915c80dbd403
Author: Yuval Mintz 
Date:   Sun Aug 17 16:47:45 2014 +0300

bnx2x: Code cleanup
ddstreet@toughbook:~/linux$ git show e42780b | head -5
commit e42780b66aab88d3a82b6087bcd6095b90eecde7
Author: Dmitry Kravkov 
Date:   Sun Aug 17 16:47:43 2014 +0300

bnx2x: Utilize FW 7.10.51

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

Title:
  BNX2X firmware an hang on Trusty (3.13) and Utopic (3.16).

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress

Bug description:
  It was brought to my attention that BNX2X FIRMWARE is causing HW hangs
  on kernels 3.13 and 3.16 (until next power-cycle):

  Messages like this one:

  """
  Mar 30 13:42:05 host kernel: [3986360.755781] device em3 left promiscuous mode
  Mar 30 13:42:05 host kernel: [3986360.755849] br1: port 1(em3) entered 
disabled state
  Mar 30 13:42:05 host kernel: [3986360.756305] IPv6: ADDRCONF(NETDEV_UP): em3: 
link is not ready
  Mar 30 13:42:08 host kernel: [3986363.354376] device em3 entered promiscuous 
mode
  Mar 30 13:42:08 host kernel: [3986363.376093] bnx2x: 
[bnx2x_open:11791(em3)]Recovery flow hasn't been properly completed yet. Try 
again later.
  Mar 30 13:42:08 host kernel: [3986363.376093] If you still see this message 
after a few retries then power cycle is required.
  Mar 30 13:42:08 host kernel: [3986363.420113] bnx2x: 
[bnx2x_open:11791(em3)]Recovery flow hasn't been properly completed yet. Try 
again later.
  Mar 30 13:42:08 host kernel: [3986363.420113] If you still see this message 
after a few retries then power cycle is required.
  Mar 30 13:42:08 host kernel: [3986363.443840] IPv6: ADDRCONF(NETDEV_UP): br1: 
link is not ready
  """

  Are likely to be given in syslog whenever this happens.

  WORKAROUND: After providing the user a "linux-lts-vivid" and an
  updated linux-firmware package
  (https://launchpad.net/~inaddy/+archive/ubuntu/sf00080928/) the issue
  was fixed after package installation and power-cycle -> Power cycle is
  needed since previous firmware hangs HW until it is shutdown.

  My comments:

  """
  Actually after reading the Changelog for FW 7.10.51 (specifically the part 
"Chip may stall in very rare cases under heavy traffic with FW GRO enabled.") I 
think we might need to upgrade not only the FIRMWARE but also the DRIVER. 

  commit 626041248d3fb5b2fca5c9af172f00fa3bb6dcfe 
  Author: Yuval Mintz  
  Date: Sun Aug 17 16:47:46 2014 +0300 

  bnx2x: Update driver version to 1.710.5

  commit e42780b66aab88d3a82b6087bcd6095b90eecde7 
  Author: Dmitry Kravkov  
  Date: Sun Aug 17 16:47:43 2014 +0300 

  bnx2x: Utilize FW 7.10.51

  Observations:

  
inaddy@alien:~/Bugs/customer/sf00080928/sources/trusty/linux-firmware-1.127.11$ 
find . | grep bnx2x 
  ./bnx2x 
  ./bnx2x/bnx2x-e1h-7.8.19.0.fw 
  ./bnx2x/bnx2x-e1-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.8.19.0.fw 
  ./bnx2x/bnx2x-e2-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1h-7.8.17.0.fw 
  ./bnx2x/bnx2x-e2-7.8.19.0.fw 

  
inaddy@alien:~/Bugs/customer/sf00080928/sources/utopic/linux-firmware-1.138.1$ 
find . | grep bnx2x 
  ./bnx2x 
  ./bnx2x/bnx2x-e1h-7.8.19.0.fw 
  ./bnx2x/bnx2x-e1-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.8.19.0.fw 
  ./bnx2x/bnx2x-e2-7.10.51.0.fw 
  ./bnx2x/bnx2x-e1h-7.10.51.0.fw 
  ./bnx2x/bnx2x-e2-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1h-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.10.51.0.fw 
  ./bnx2x/bnx2x-e2-7.8.19.0.fw 

  Firmware 7.10.51 is already present in Utopic but the commit to support it is 
only in 3.18.  It might be feasible to backport it to 3.16 (and use HWE) but 
not sure about 3.13 (to be resolved if this new firmware/driver fixes the 
issue).
  """

  I'll provide more comments right after my backport attempt (of this
  new version) is made.

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

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

[Kernel-packages] [Bug 1541120] Re: [Hyper-V] PCI Passthrough

[Joshua R. Poulson]

This is a request to pull a feature from the upstream Linux kernel. No
logs required, but we'll talk about how to test the feature when the
time comes.

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

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

Title:
  [Hyper-V] PCI Passthrough

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Jake Oshins (Microsoft) has submitted upstream the PCI Passthrough
  feature, and while it is not yet accepted upstream (because of the
  effect on multiple trees and affects PCI), Microsoft would like
  Canonical to consider its inclusion in Ubuntu 16.04 and beyond. The
  rounds of feedback on the patches are winding down, so it is a good
  time to consider them.

  All of the submitted files are in the attached thread, but not all are
  committed to Linus's tree as of 4.5-rc1.

  This feature is needed for supporting SR-IOV and GPU passthrough on
  Hyper-V.

  The 10th iteration of the upstream submission is available on lkml:

  https://lkml.org/lkml/2015/12/10/553

  From  jakeo@microsof ...
  Subject   [PATCH v10 0/7] PCI: hv: New paravirtual PCI front-end for 
Hyper-V VMs
  Date  Thu, 10 Dec 2015 17:52:56 +
  From: Jake Oshins 

  This version of the patch series removes warning when compiling x86
  32-bit while still making it build cleanly for x64.

  First, export functions that allow correlating Hyper-V virtual processors
  and Linux cpus, along with the means for invoking a hypercall that targets
  interrupts at chosen vectors on specific cpus.

  Second, mark various parts of IRQ domain related code as exported, so that
  this PCI front-end can implement an IRQ domain as part of a module. (The
  alternative would be to pull all tyhis into the kernel, which would pull
  in a lot of other Hyper-V related code, as this IRQ domain depends on
  vmbus.ko.)

  Third, modify PCI so that new root PCI buses can be marked with an associated
  fwnode_handle, and so that root PCI buses can look up their associated IRQ
  domain by that handle.

  Fourth, introduce a new driver, hv_pcifront, which exposes root PCI buses in
  a Hyper-V VM. These root PCI buses expose real PCIe device, or PCI Virtual
  Functions.

  Jake Oshins (7):
drivers:hv: Export a function that maps Linux CPU num onto Hyper-V
  proc num
drivers:hv: Export hv_do_hypercall()
PCI: Make it possible to implement a PCI MSI IRQ Domain in a module.
PCI: Add fwnode_handle to pci_sysdata
PCI: irqdomain: Look up IRQ domain by fwnode_handle
drivers:hv: Define the channel type of Hyper-V PCI Express
  pass-through
PCI: hv: New paravirtual PCI front-end for Hyper-V VMs

   MAINTAINERS | 1 +
   arch/x86/include/asm/msi.h | 6 +
   arch/x86/include/asm/pci.h | 15 +
   arch/x86/kernel/apic/msi.c | 8 +-
   arch/x86/kernel/apic/vector.c | 2 +
   drivers/hv/hv.c | 20 +-
   drivers/hv/hyperv_vmbus.h | 2 +-
   drivers/hv/vmbus_drv.c | 17 +
   drivers/pci/Kconfig | 7 +
   drivers/pci/host/Makefile | 1 +
   drivers/pci/host/hv_pcifront.c | 2249 

   drivers/pci/msi.c | 4 +
   drivers/pci/probe.c | 15 +
   include/linux/hyperv.h | 14 +
   include/linux/pci.h | 4 +
   kernel/irq/chip.c | 1 +
   kernel/irq/irqdomain.c | 4 +
   17 files changed, 2356 insertions(+), 14 deletions(-)
   create mode 100644 drivers/pci/host/hv_pcifront.c

  Accepted commits so far in 4.5-rc1:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a108393dbf764efb2405f21ca759806c65b8bc16
 drivers:hv: Export the API to invoke a hypercall on Hyper-V
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=619848bd074343ff2bdeeafca0be39748f6da372
 drivers:hv: Export a function that maps Linux CPU num onto Hyper-V proc num
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3053c762444a83ec6a8777f9476668b23b8ab180
 drivers:hv: Define the channel type for Hyper-V PCI Express pass-through
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=40f26f3168bf7a4da490db308dc0bd9f9923f41f
 drivers:hv: Allow for MMIO claims that span ACPI _CRS records
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a4289dc2ec3a5821076a78ee9678909b4eff297e
 genirq/msi: Export functions to allow MSI domains in modules
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c8f3e518d3444ee9200a4987421fcee60f768f11
 x86/irq: Export functions to allow MSI domains in modules

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

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

[Kernel-packages] [Bug 1540720] Re: linux-ti-omap4: 3.2.0-1477.100 -proposed tracker

[Brad Figg]

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

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: ubuntu-armel-kernel (ubuntu-armel-kernel) => Brad Figg 
(brad-figg)

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

** Description changed:

  This bug is for tracking the 3.2.0-1477.100 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, 02. February 2016 04:01 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 02. February 2016 04:01 UTC
  kernel-stable-master-bug:1540538
  kernel-stable-Certification-testing-end:Tuesday, 02. February 2016 16:01 UTC
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Wednesday, 03. February 2016 00:01 UTC
+ kernel-stable-Promote-to-proposed-start:Wednesday, 03. February 2016 00:01 UTC
+ kernel-stable-phase-changed:Wednesday, 03. February 2016 00:01 UTC

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

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

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

Bug description:
  This bug is for tracking the 3.2.0-1477.100 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, 02. February 2016 04:01 UTC
  kernel-stable-master-bug:1540538
  kernel-stable-Certification-testing-end:Tuesday, 02. February 2016 16:01 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Wednesday, 03. February 2016 00:01 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 03. February 2016 00:01 UTC
  kernel-stable-phase-changed:Wednesday, 03. February 2016 00:01 UTC

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

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

[Kernel-packages] [Bug 1454286] Re: BNX2X firmware an hang on Trusty (3.13) and Utopic (3.16).

[Dan Streetman]

Note: commit e42780b actually updates the driver to use the new
firmware:

diff --git a/drivers/net/ethernet/broadcom/bnx2x/bnx2x_hsi.h 
b/drivers/net/ethernet/broadcom/bnx2x/b
index 5ba8af5..3b6cbd2 100644
--- a/drivers/net/ethernet/broadcom/bnx2x/bnx2x_hsi.h
+++ b/drivers/net/ethernet/broadcom/bnx2x/bnx2x_hsi.h
@@ -2876,8 +2876,8 @@ struct afex_stats {
 };
 
 #define BCM_5710_FW_MAJOR_VERSION  7
-#define BCM_5710_FW_MINOR_VERSION  8
-#define BCM_5710_FW_REVISION_VERSION   19
+#define BCM_5710_FW_MINOR_VERSION  10
+#define BCM_5710_FW_REVISION_VERSION   51
 #define BCM_5710_FW_ENGINEERING_VERSION0
 #define BCM_5710_FW_COMPILE_FLAGS  1
 

however, this commit sits on top of 87 other commits:

ddstreet@toughbook:~/linux/drivers/net/ethernet/broadcom/bnx2x$ git log 
--oneline Ubuntu-3.13.0-78.122..e42780b . | wc -l
87

so, it's not clear yet if any of those 87 commits are also needed to
work properly with the 7.10.51 firmware.

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

Title:
  BNX2X firmware an hang on Trusty (3.13) and Utopic (3.16).

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress

Bug description:
  It was brought to my attention that BNX2X FIRMWARE is causing HW hangs
  on kernels 3.13 and 3.16 (until next power-cycle):

  Messages like this one:

  """
  Mar 30 13:42:05 host kernel: [3986360.755781] device em3 left promiscuous mode
  Mar 30 13:42:05 host kernel: [3986360.755849] br1: port 1(em3) entered 
disabled state
  Mar 30 13:42:05 host kernel: [3986360.756305] IPv6: ADDRCONF(NETDEV_UP): em3: 
link is not ready
  Mar 30 13:42:08 host kernel: [3986363.354376] device em3 entered promiscuous 
mode
  Mar 30 13:42:08 host kernel: [3986363.376093] bnx2x: 
[bnx2x_open:11791(em3)]Recovery flow hasn't been properly completed yet. Try 
again later.
  Mar 30 13:42:08 host kernel: [3986363.376093] If you still see this message 
after a few retries then power cycle is required.
  Mar 30 13:42:08 host kernel: [3986363.420113] bnx2x: 
[bnx2x_open:11791(em3)]Recovery flow hasn't been properly completed yet. Try 
again later.
  Mar 30 13:42:08 host kernel: [3986363.420113] If you still see this message 
after a few retries then power cycle is required.
  Mar 30 13:42:08 host kernel: [3986363.443840] IPv6: ADDRCONF(NETDEV_UP): br1: 
link is not ready
  """

  Are likely to be given in syslog whenever this happens.

  WORKAROUND: After providing the user a "linux-lts-vivid" and an
  updated linux-firmware package
  (https://launchpad.net/~inaddy/+archive/ubuntu/sf00080928/) the issue
  was fixed after package installation and power-cycle -> Power cycle is
  needed since previous firmware hangs HW until it is shutdown.

  My comments:

  """
  Actually after reading the Changelog for FW 7.10.51 (specifically the part 
"Chip may stall in very rare cases under heavy traffic with FW GRO enabled.") I 
think we might need to upgrade not only the FIRMWARE but also the DRIVER. 

  commit 626041248d3fb5b2fca5c9af172f00fa3bb6dcfe 
  Author: Yuval Mintz  
  Date: Sun Aug 17 16:47:46 2014 +0300 

  bnx2x: Update driver version to 1.710.5

  commit e42780b66aab88d3a82b6087bcd6095b90eecde7 
  Author: Dmitry Kravkov  
  Date: Sun Aug 17 16:47:43 2014 +0300 

  bnx2x: Utilize FW 7.10.51

  Observations:

  
inaddy@alien:~/Bugs/customer/sf00080928/sources/trusty/linux-firmware-1.127.11$ 
find . | grep bnx2x 
  ./bnx2x 
  ./bnx2x/bnx2x-e1h-7.8.19.0.fw 
  ./bnx2x/bnx2x-e1-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.8.19.0.fw 
  ./bnx2x/bnx2x-e2-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1h-7.8.17.0.fw 
  ./bnx2x/bnx2x-e2-7.8.19.0.fw 

  
inaddy@alien:~/Bugs/customer/sf00080928/sources/utopic/linux-firmware-1.138.1$ 
find . | grep bnx2x 
  ./bnx2x 
  ./bnx2x/bnx2x-e1h-7.8.19.0.fw 
  ./bnx2x/bnx2x-e1-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.8.19.0.fw 
  ./bnx2x/bnx2x-e2-7.10.51.0.fw 
  ./bnx2x/bnx2x-e1h-7.10.51.0.fw 
  ./bnx2x/bnx2x-e2-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1h-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.10.51.0.fw 
  ./bnx2x/bnx2x-e2-7.8.19.0.fw 

  Firmware 7.10.51 is already present in Utopic but the commit to support it is 
only in 3.18.  It might be feasible to backport it to 3.16 (and use HWE) but 
not sure about 3.13 (to be resolved if this new firmware/driver fixes the 
issue).
  """

  I'll provide more comments right after my backport attempt (of this
  new version) is made.

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

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

[Kernel-packages] [Bug 1538673] Re: Atheros Qualcomm Killer N1525 Wireless-AC Cannot Connect to ac/5GHz

[Corey]

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

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC Cannot Connect to ac/5GHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Gnome 15.10

  I do not know what package this error is a part of or if it is even
  part of a package as I am not familiar enough with linux.  I know it
  is the ath10k_pci module.

  Expected: The wifi would connect to the access point.

  Actual: Firmware crashes twice then NetworkManager times out the
  connection.

  This problem only occurs when either connecting to an 802.11ac or a
  5GHz access point.  I do not have the equipment and or knowledge to be
  able to narrow it down any to one specifically.  It does connect to my
  phone's hotspot on 2.4GHz (I think it is N?) but will not when the
  hotspot is set to 5GHz (Definitely AC).  It also will not connect to
  my school's AC wireless network.

  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  polomoto   1168 F pulseaudio
   /dev/snd/controlC1:  polomoto   1168 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=5018c1c5-f5d2-45e3-a3da-4e74bd9b9131
  InstallationDate: Installed on 2016-01-22 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: Micro-Star International Co., Ltd. GS60 2QE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=b7920bb6-c35c-43c5-82be-c195753bc15f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16H5IMS.104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16H5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16H5IMS.104:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS602QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H5:rvrREV0.B:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GS60 2QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1454286] Re: BNX2X firmware an hang on Trusty (3.13) and Utopic (3.16).

[Dan Streetman]

Note: commit 6260412 is *definitely* not appropriate, as it simply
updates the driver version, which is wrong to do without also updating
the driver with all the preceeding commits.

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

Title:
  BNX2X firmware an hang on Trusty (3.13) and Utopic (3.16).

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress

Bug description:
  It was brought to my attention that BNX2X FIRMWARE is causing HW hangs
  on kernels 3.13 and 3.16 (until next power-cycle):

  Messages like this one:

  """
  Mar 30 13:42:05 host kernel: [3986360.755781] device em3 left promiscuous mode
  Mar 30 13:42:05 host kernel: [3986360.755849] br1: port 1(em3) entered 
disabled state
  Mar 30 13:42:05 host kernel: [3986360.756305] IPv6: ADDRCONF(NETDEV_UP): em3: 
link is not ready
  Mar 30 13:42:08 host kernel: [3986363.354376] device em3 entered promiscuous 
mode
  Mar 30 13:42:08 host kernel: [3986363.376093] bnx2x: 
[bnx2x_open:11791(em3)]Recovery flow hasn't been properly completed yet. Try 
again later.
  Mar 30 13:42:08 host kernel: [3986363.376093] If you still see this message 
after a few retries then power cycle is required.
  Mar 30 13:42:08 host kernel: [3986363.420113] bnx2x: 
[bnx2x_open:11791(em3)]Recovery flow hasn't been properly completed yet. Try 
again later.
  Mar 30 13:42:08 host kernel: [3986363.420113] If you still see this message 
after a few retries then power cycle is required.
  Mar 30 13:42:08 host kernel: [3986363.443840] IPv6: ADDRCONF(NETDEV_UP): br1: 
link is not ready
  """

  Are likely to be given in syslog whenever this happens.

  WORKAROUND: After providing the user a "linux-lts-vivid" and an
  updated linux-firmware package
  (https://launchpad.net/~inaddy/+archive/ubuntu/sf00080928/) the issue
  was fixed after package installation and power-cycle -> Power cycle is
  needed since previous firmware hangs HW until it is shutdown.

  My comments:

  """
  Actually after reading the Changelog for FW 7.10.51 (specifically the part 
"Chip may stall in very rare cases under heavy traffic with FW GRO enabled.") I 
think we might need to upgrade not only the FIRMWARE but also the DRIVER. 

  commit 626041248d3fb5b2fca5c9af172f00fa3bb6dcfe 
  Author: Yuval Mintz  
  Date: Sun Aug 17 16:47:46 2014 +0300 

  bnx2x: Update driver version to 1.710.5

  commit e42780b66aab88d3a82b6087bcd6095b90eecde7 
  Author: Dmitry Kravkov  
  Date: Sun Aug 17 16:47:43 2014 +0300 

  bnx2x: Utilize FW 7.10.51

  Observations:

  
inaddy@alien:~/Bugs/customer/sf00080928/sources/trusty/linux-firmware-1.127.11$ 
find . | grep bnx2x 
  ./bnx2x 
  ./bnx2x/bnx2x-e1h-7.8.19.0.fw 
  ./bnx2x/bnx2x-e1-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.8.19.0.fw 
  ./bnx2x/bnx2x-e2-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1h-7.8.17.0.fw 
  ./bnx2x/bnx2x-e2-7.8.19.0.fw 

  
inaddy@alien:~/Bugs/customer/sf00080928/sources/utopic/linux-firmware-1.138.1$ 
find . | grep bnx2x 
  ./bnx2x 
  ./bnx2x/bnx2x-e1h-7.8.19.0.fw 
  ./bnx2x/bnx2x-e1-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.8.19.0.fw 
  ./bnx2x/bnx2x-e2-7.10.51.0.fw 
  ./bnx2x/bnx2x-e1h-7.10.51.0.fw 
  ./bnx2x/bnx2x-e2-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1h-7.8.17.0.fw 
  ./bnx2x/bnx2x-e1-7.10.51.0.fw 
  ./bnx2x/bnx2x-e2-7.8.19.0.fw 

  Firmware 7.10.51 is already present in Utopic but the commit to support it is 
only in 3.18.  It might be feasible to backport it to 3.16 (and use HWE) but 
not sure about 3.13 (to be resolved if this new firmware/driver fixes the 
issue).
  """

  I'll provide more comments right after my backport attempt (of this
  new version) is made.

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

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

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

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 02. February 2016 06:02 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 02. February 2016 06:02 UTC
  kernel-stable-master-bug:1540559

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

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

[Kernel-packages] [Bug 1540731] Re: SocketMessenger::update_session_creds() fails to get client PID, causing "[ FAILED ] PromptSessionClientAPI.client_pid_is_associated_with_session"

[Daniel van Vugt]

** Summary changed:

- SocketMessenger::update_session_creds() fails to get client PID
+ SocketMessenger::update_session_creds() fails to get client PID, causing "[ 
FAILED ] PromptSessionClientAPI.client_pid_is_associated_with_session"

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

Title:
  SocketMessenger::update_session_creds() fails to get client PID,
  causing "[ FAILED ]
  PromptSessionClientAPI.client_pid_is_associated_with_session"

Status in GLibC:
  New
Status in Mir:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since updating to the 4.4.0-2 kernel recvmsg() fails SCM_CREDENTIALS
  request with EOPNOTSUPP.

  This manifests as a test failure in Mir:

  [ RUN  ] PromptSessionClientAPI.client_pid_is_associated_with_session
  unknown file: Failure

  Test case:

  #include 
  #include 
  #include 
  #include 

  TEST(IsItBroken, recvmsg)
  {
  using namespace testing;

  enum { server, client, size };
  int socket_fd[size];
  int const opt = 1;

  ASSERT_THAT(socketpair(AF_LOCAL, SOCK_STREAM, 0, socket_fd),
  Eq(0));

  auto const msg = "A random message";
  send(socket_fd[client], msg, sizeof msg, MSG_DONTWAIT | MSG_NOSIGNAL);

  ASSERT_THAT(setsockopt(socket_fd[server], SOL_SOCKET, SO_PASSCRED,
  , sizeof(opt)), Ne(-1));

  union {
  struct cmsghdr cmh;
  char   control[CMSG_SPACE(sizeof(ucred))];
  } control_un;

  control_un.cmh.cmsg_len = CMSG_LEN(sizeof(ucred));
  control_un.cmh.cmsg_level = SOL_SOCKET;
  control_un.cmh.cmsg_type = SCM_CREDENTIALS;

  msghdr msgh;
  msgh.msg_name = nullptr;
  msgh.msg_namelen = 0;
  msgh.msg_iov = nullptr;
  msgh.msg_iovlen = 0;
  msgh.msg_control = control_un.control;
  msgh.msg_controllen = sizeof(control_un.control);

  errno = 0;

  EXPECT_THAT(recvmsg(socket_fd[server], , MSG_PEEK), Ne(-1))
  << "Error: " << strerror(errno);

  for (auto socket : socket_fd) close(socket);
  }

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

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

[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

[Tiago Salem Herrmann]

Yes, this is still an issue. We agreed with Alfonso that ofono will use 
AccountsService to get the default sim card for calls.
It needs some work on telephony-service and system-settings.

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

Title:
  Calling from car using bluetooth, call is placed on ril_0, even though
  ril_1 is default

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Triaged
Status in telephony-service package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  What happened
  Placed call from car over bluetooth
  Call was placed on my first SIM card, even though I selected my second SIM as 
default for calls

  What should have happened
  The call should have been placed on my second SIM

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20150124-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: armhf
  Date: Wed Feb  4 14:25:44 2015
  InstallationDate: Installed on 2015-02-02 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150202-020204)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions

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

[Kernel-packages] [Bug 1534647] Re: Collateral damage due to kernel configuration change enabling CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)

[Marc]

Okay. This should then probably be documented somewhere for users
upgrading from previous releases.

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

Title:
  Collateral damage due to kernel configuration change enabling
  CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)

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

Bug description:
  Late in the kernel 4.4 RC (Release Candidate) cycle (between rc7 and
  rc8), Ubuntu implemented an amd64 kernel configuration change enabling
  CONFIG_ZONE_DEVICE.

  The related email: https://lists.ubuntu.com/archives/kernel-
  team/2016-January/067683.html

  The commit message does mention collateral damage: "In effect, this precludes 
devices that can only DMA from memory addresses below 16MB".
  Indeed we already have a complaint about a sound card that doesn't work as of 
kernel 4.4-rc8.

  If CONFIG_ZONE_DEVICE is enabled, then CONFIG_ZONE_DMA is forced to disabled, 
which in turn forces these devices, all are sound cards, and their derivative 
devices, to be disabled:
  Avance Logic ALS300/ALS300+
  ALi M5451 PCI Audio Controller
  Aztech AZF3328 / PCI168
  Emu10k1 (SB Live!, Audigy, E-mu APS)
  Emu10k1X (Dell OEM Version)
  ESS ES1938/1946/1969 (Solo-1)
  ESS ES1968/1978 (Maestro-1/2/2E)
  ICEnsemble ICE1712 (Envy24)
  ESS Allegro/Maestro3
  S3 SonicVibes
  Trident 4D-Wave DX/NX; SiS 7018.

  References: linux/mm/Kconfig; linux/sound/pci/Kconfig

  One test done (suggested by apw on IRC) was to remove the dependency of 
ZONE_DEVICE on !ZONE_DMA, but that causes:
  "#error ZONES_SHIFT -- too many zones configured adjust calculation", as apw 
predicted.
  In a mindless way, I tried to allow more zones in 
linux/include/linux/page-flags-layout.h, but that caused a bunch of "shifting 
by too many bits type errors. Anyway it seems that MAX_NR_ZONES is, at least 
partially, hard coded to 4 in some array definitions and such.

  Please do not ask me to do "apport-collect" for this bug report as it
  is not needed, nor relevant.

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

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

[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: High => Critical

** Tags added: bluetooth

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions

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

[Kernel-packages] [Bug 1525320] Re: Aquaris E4.5 can't connect with car [Skoda Fabia] using bluetooth

[Pat McGowan]

** Tags added: bluetooth

** Changed in: canonical-devices-system-image
   Importance: Medium => Critical

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

Title:
  Aquaris E4.5 can't connect with car [Skoda Fabia] using bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Aquaris E4.5 Can't connect with my car (new skoda fabia 2015) with
  bluetooth.

  Error is:

  "Could not connect with Aquaris E4.5 Ubuntu Edition"

  
  Let me know if I can help in some way..thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1525320/+subscriptions

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

[Kernel-packages] [Bug 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot

[Pat McGowan]

** Tags removed: bluetooth-ota9
** Tags added: bluetooth

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

Title:
  power cycling Emerson EM229 headset caused phone to reboot

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  While sanity testing krillin rtm image 139, I paired a bluetooth
  headset.  I made a call with it, hung up, then turned the headset off.
  I noticed this caused the BT indicator icon to invert, which is a nice
  way to indicate whether something is connected.  So, I turned the
  device back on, waited for the icon to invert, turned the device off,
  waited, and instead of inverting the icon...  the phone rebooted.

  Not sure what exactly failed here, like which component, but it's
  definitely not good when a paired headset can cause the phone to
  spontaneously reboot.

  I don't see any relevant .crash files, and all I see in syslog from
  that time is this:

  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  Activation 
(/ril_1) failed for connection '/310410695117999/context1'
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): device 
state change: failed -> disconnected (reason 'none') [120 30 0]
  Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]:  (/ril_1): 
deactivating device (reason 'none') [0]
  Oct 30 23:43:01 ubuntu-phablet kernel: [  
747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 
(2014-10-31 05:43:01.704759580 UTC)
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.779813]mtk-tpd: TPD wake up
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816572]mtk-tpd: TPD wake up done
  Oct 30 23:43:02 ubuntu-phablet kernel: [  747.816593]  
mag_context_obj ok--->hwm_obj->early_suspend=0 
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service 
name='org.freedesktop.systemd1' (using servicehelper)
  Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated 
service 'org.freedesktop.systemd1'
  Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com;] exiting on 
signal 15.
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com;] start
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is 
deprecated, consider using the 'stop' statement instead [try 
http://www.rsyslog.com/e/2307 ]
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103
  Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on 
physical CPU 0
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup 
subsys cpu
  Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 
(root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue 
Oct 28 11:57:42 UTC 2014

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387949/+subscriptions

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

[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: High => Critical

** Tags removed: bluetooth-ota9

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  package linux-image-extra-4.3.0-7-generic 4.3.0-7.18 failed to
  install/upgrade: подпроцесс установлен сценарий post-removal возвратил
  код ошибки 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  123

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.3.0-7-generic 4.3.0-7.18
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  valera 1618 F pulseaudio
  Date: Tue Feb  2 21:32:32 2016
  ErrorMessage: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 1
  InstallationDate: Installed on 2016-01-17 (16 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: HP-Pavilion NR011AA-ACB p6041ru
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=2f6ba869-6053-4970-8790-7eca9b875aa7 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-35ubuntu1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.3.0-7-generic 4.3.0-7.18 failed to 
install/upgrade: подпроцесс установлен сценарий post-removal возвратил код 
ошибки 1
  UpgradeStatus: Upgraded to xenial on 2016-01-19 (13 days ago)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.43
  dmi.board.name: Benicia
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Asset-1234
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnNR011AA-ACBp6041ru:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: NR011AA-ACB p6041ru
  dmi.sys.vendor: HP-Pavilion

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

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

[Kernel-packages] [Bug 1541044] [NEW] package linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 25

[Юрий]

Public bug reported:

-

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
Uname: Linux 3.19.0-49-generic i686
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
Date: Tue Feb  2 12:56:05 2016
DpkgHistoryLog:
 Start-Date: 2016-02-02  12:56:00
 Commandline: aptdaemon role='role-commit-packages' sender=':1.68'
 Install: linux-image-extra-3.19.0-49-generic:i386 (3.19.0-49.55~14.04.1), 
linux-headers-3.19.0-49:i386 (3.19.0-49.55~14.04.1), 
linux-headers-3.19.0-49-generic:i386 (3.19.0-49.55~14.04.1), 
linux-image-3.19.0-49-generic:i386 (3.19.0-49.55~14.04.1)
 Upgrade: linux-generic-lts-vivid:i386 (3.19.0.47.32, 3.19.0.49.34), 
linux-libc-dev:i386 (3.13.0-76.120, 3.13.0-77.121), 
linux-headers-generic-lts-vivid:i386 (3.19.0.47.32, 3.19.0.49.34), 
linux-image-generic-lts-vivid:i386 (3.19.0.47.32, 3.19.0.49.34)
DpkgTerminalLog:
 Preparing to unpack 
.../linux-image-3.19.0-49-generic_3.19.0-49.55~14.04.1_i386.deb ...
 Can't locate object method "new" via package "Text::Iconv" (perhaps you forgot 
to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65.
 dpkg: error processing archive 
/var/cache/apt/archives/linux-image-3.19.0-49-generic_3.19.0-49.55~14.04.1_i386.deb
 (--unpack):
  subprocess new pre-installation script returned error exit status 25
DuplicateSignature: 
package:linux-image-3.19.0-49-generic:3.19.0-49.55~14.04.1:subprocess new 
pre-installation script returned error exit status 25
ErrorMessage: subprocess new pre-installation script returned error exit status 
25
InstallationDate: Installed on 2015-09-12 (143 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.5
 apt  1.0.1ubuntu2.11
SourcePackage: linux-lts-vivid
Title: package linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 25
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 need-duplicate-check trusty

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

Title:
  package linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 25

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

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Tue Feb  2 12:56:05 2016
  DpkgHistoryLog:
   Start-Date: 2016-02-02  12:56:00
   Commandline: aptdaemon role='role-commit-packages' sender=':1.68'
   Install: linux-image-extra-3.19.0-49-generic:i386 (3.19.0-49.55~14.04.1), 
linux-headers-3.19.0-49:i386 (3.19.0-49.55~14.04.1), 
linux-headers-3.19.0-49-generic:i386 (3.19.0-49.55~14.04.1), 
linux-image-3.19.0-49-generic:i386 (3.19.0-49.55~14.04.1)
   Upgrade: linux-generic-lts-vivid:i386 (3.19.0.47.32, 3.19.0.49.34), 
linux-libc-dev:i386 (3.13.0-76.120, 3.13.0-77.121), 
linux-headers-generic-lts-vivid:i386 (3.19.0.47.32, 3.19.0.49.34), 
linux-image-generic-lts-vivid:i386 (3.19.0.47.32, 3.19.0.49.34)
  DpkgTerminalLog:
   Preparing to unpack 
.../linux-image-3.19.0-49-generic_3.19.0-49.55~14.04.1_i386.deb ...
   Can't locate object method "new" via package "Text::Iconv" (perhaps you 
forgot to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-3.19.0-49-generic_3.19.0-49.55~14.04.1_i386.deb
 (--unpack):
subprocess new pre-installation script returned error exit status 25
  DuplicateSignature: 
package:linux-image-3.19.0-49-generic:3.19.0-49.55~14.04.1:subprocess new 
pre-installation script returned error exit status 25
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 25
  InstallationDate: Installed on 2015-09-12 (143 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: linux-lts-vivid
  Title: package linux-image-3.19.0-49-generic 3.19.0-49.55~14.04.1 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 25
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1534647] Re: Collateral damage due to kernel configuration change enabling CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)

[Tim Gardner]

Marc - that is currently the only choice. Upstream is discussing a fix
that might allow both configurations, but I don't know when it might get
implemented, or if it will be suitable as an SRU patch.

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

Title:
  Collateral damage due to kernel configuration change enabling
  CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)

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

Bug description:
  Late in the kernel 4.4 RC (Release Candidate) cycle (between rc7 and
  rc8), Ubuntu implemented an amd64 kernel configuration change enabling
  CONFIG_ZONE_DEVICE.

  The related email: https://lists.ubuntu.com/archives/kernel-
  team/2016-January/067683.html

  The commit message does mention collateral damage: "In effect, this precludes 
devices that can only DMA from memory addresses below 16MB".
  Indeed we already have a complaint about a sound card that doesn't work as of 
kernel 4.4-rc8.

  If CONFIG_ZONE_DEVICE is enabled, then CONFIG_ZONE_DMA is forced to disabled, 
which in turn forces these devices, all are sound cards, and their derivative 
devices, to be disabled:
  Avance Logic ALS300/ALS300+
  ALi M5451 PCI Audio Controller
  Aztech AZF3328 / PCI168
  Emu10k1 (SB Live!, Audigy, E-mu APS)
  Emu10k1X (Dell OEM Version)
  ESS ES1938/1946/1969 (Solo-1)
  ESS ES1968/1978 (Maestro-1/2/2E)
  ICEnsemble ICE1712 (Envy24)
  ESS Allegro/Maestro3
  S3 SonicVibes
  Trident 4D-Wave DX/NX; SiS 7018.

  References: linux/mm/Kconfig; linux/sound/pci/Kconfig

  One test done (suggested by apw on IRC) was to remove the dependency of 
ZONE_DEVICE on !ZONE_DMA, but that causes:
  "#error ZONES_SHIFT -- too many zones configured adjust calculation", as apw 
predicted.
  In a mindless way, I tried to allow more zones in 
linux/include/linux/page-flags-layout.h, but that caused a bunch of "shifting 
by too many bits type errors. Anyway it seems that MAX_NR_ZONES is, at least 
partially, hard coded to 4 in some array definitions and such.

  Please do not ask me to do "apport-collect" for this bug report as it
  is not needed, nor relevant.

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

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

[Kernel-packages] [Bug 1531747] Re: overlay: mkdir fails if directory exists in lowerdir in a user namespace

[Seth Forshee]

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

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

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

Title:
  overlay: mkdir fails if directory exists in lowerdir in a user
  namespace

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Wily:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  If a directory exists in the lowerdir but not in the mounted
  overlay, then mkdir of the directory in the target dir results
  in a mysterious -EPERM.  I've seen this both in wily kernel
  (4.2.0-22-generic #27-Ubuntu) and in a hand-built xenial
  master-next (with unrelated patches added).

  =
  #!/bin/sh -ex
  dir=`mktemp -d`
  cleanup() {
   umount -l $dir/t
   rm -rf $dir
  }

  trap cleanup EXIT

  echo "dir is $dir"
  mkdir -p $dir/l $dir/u $dir/w $dir/t
  mkdir $dir/l/dev
  mount -t overlay -o lowerdir=$dir/l,upperdir=$dir/u,workdir=$dir/w o $dir/t
  stat $dir/t/dev
  rmdir $dir/t/dev
  mkdir $dir/t/dev
  echo $?
  echo "mkdir should have succeeded"
  =

  The above will work on the host, but fail in a user namespace, i.e
  in a regular lxd container.

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

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

[Kernel-packages] [Bug 1494230] Re: Audio is not routed to A2DP sink when connected

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Importance: High => Critical

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

Title:
  Audio is not routed to A2DP sink when connected

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  With bluez 5.33 on Nexus 4 and silo 43 installed.

  * Pair/connect A2DP sink device
  * Play any audio

  -> Audio is not played on A2DP sink and also not on speakers

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494230/+subscriptions

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Joseph Salisbury]

Commit a689d2510 was cc'd to stable, but it was not picked up for Vivid
yet.  It may not get picked up in time before Vivid goes EOL.

I'm going to see if this issues can still be reproduced with the latest
4.5 mainline 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/1470250

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

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

[Brad Figg]

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

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

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

** Description changed:

  This bug is for tracking the 3.13.0-78.122~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 02. February 2016 06:02 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 02. February 2016 06:02 UTC
  kernel-stable-master-bug:1540559
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Wednesday, 03. February 2016 04:02 UTC
+ kernel-stable-Promote-to-proposed-start:Wednesday, 03. February 2016 04:02 UTC
+ kernel-stable-phase-changed:Wednesday, 03. February 2016 04:02 UTC

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 02. February 2016 06:02 UTC
  kernel-stable-master-bug:1540559
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Wednesday, 03. February 2016 04:02 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 03. February 2016 04:02 UTC
  kernel-stable-phase-changed:Wednesday, 03. February 2016 04:02 UTC

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

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

[Kernel-packages] [Bug 1536555] Re: USB3 devices are not active early in boot

[Christopher M. Penalver]

** Tags added: latest-bios-a12

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

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

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1540731] Re: SocketMessenger::update_session_creds() fails to get client PID, causing "[ FAILED ] PromptSessionClientAPI.client_pid_is_associated_with_session"

[Daniel van Vugt]

Is this critical? I'm not familiar with prompt sessions, but on my
xenial machine I find Unity8 still works even when this bug is present.
Does it really affect us in production right now?

** Changed in: mir
   Importance: Critical => 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/1540731

Title:
  SocketMessenger::update_session_creds() fails to get client PID,
  causing "[ FAILED ]
  PromptSessionClientAPI.client_pid_is_associated_with_session"

Status in GLibC:
  New
Status in Mir:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since updating to the 4.4.0-2 kernel recvmsg() fails SCM_CREDENTIALS
  request with EOPNOTSUPP.

  This manifests as a test failure in Mir:

  [ RUN  ] PromptSessionClientAPI.client_pid_is_associated_with_session
  unknown file: Failure

  Test case:

  #include 
  #include 
  #include 
  #include 

  TEST(IsItBroken, recvmsg)
  {
  using namespace testing;

  enum { server, client, size };
  int socket_fd[size];
  int const opt = 1;

  ASSERT_THAT(socketpair(AF_LOCAL, SOCK_STREAM, 0, socket_fd),
  Eq(0));

  auto const msg = "A random message";
  send(socket_fd[client], msg, sizeof msg, MSG_DONTWAIT | MSG_NOSIGNAL);

  ASSERT_THAT(setsockopt(socket_fd[server], SOL_SOCKET, SO_PASSCRED,
  , sizeof(opt)), Ne(-1));

  union {
  struct cmsghdr cmh;
  char   control[CMSG_SPACE(sizeof(ucred))];
  } control_un;

  control_un.cmh.cmsg_len = CMSG_LEN(sizeof(ucred));
  control_un.cmh.cmsg_level = SOL_SOCKET;
  control_un.cmh.cmsg_type = SCM_CREDENTIALS;

  msghdr msgh;
  msgh.msg_name = nullptr;
  msgh.msg_namelen = 0;
  msgh.msg_iov = nullptr;
  msgh.msg_iovlen = 0;
  msgh.msg_control = control_un.control;
  msgh.msg_controllen = sizeof(control_un.control);

  errno = 0;

  EXPECT_THAT(recvmsg(socket_fd[server], , MSG_PEEK), Ne(-1))
  << "Error: " << strerror(errno);

  for (auto socket : socket_fd) close(socket);
  }

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

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

[Kernel-packages] [Bug 1304551] Re: [Acer AO751h] suspend/resume failure

[Christopher M. Penalver]

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

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

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

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

Title:
  [Acer AO751h] suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The netbook failed to boot/resume after the lid was closed.  Removed
  the battery and then rebooted using AC.  Crash report followed.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-23-generic 3.13.0-23.45
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1668 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Apr  8 14:16:00 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=483c2287-757b-4995-9699-e353c8c6c9aa
  InstallationDate: Installed on 2014-04-02 (5 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Acer AO751h
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic 
root=UUID=b67a49dc-eba3-4420-817f-a9f1eab3acdd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-23-generic N/A
   linux-backports-modules-3.13.0-23-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  Title: [Acer AO751h] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/23/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V0.3206
  dmi.board.name: JV11-ML
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV0.3206:bd06/23/2009:svnAcer:pnAO751h:pvrNotApplicable:rvnAcer:rnJV11-ML:rvrNotApplicable:cvnAcer:ct1:cvrN/A:
  dmi.product.name: AO751h
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

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

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

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

[Michael Doube]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1536555/+attachment/4561942/+files/WifiSyslog.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Michael Doube]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1536555/+attachment/4561935/+files/ProcCpuinfo.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Michael Doube]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1536555/+attachment/4561941/+files/UdevLog.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Michael Doube]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1536555/+attachment/4561938/+files/ProcModules.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Michael Doube]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1536555/+attachment/4561939/+files/PulseList.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Michael Doube]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1536555/+attachment/4561937/+files/ProcInterrupts.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Michael Doube]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1536555/+attachment/4561936/+files/ProcEnviron.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1540576] Re: linux: 3.19.0-50.56 -proposed tracker

[Brad Figg]

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

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

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg 
(brad-figg)

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

** Description changed:

  This bug is for tracking the 3.19.0-50.56 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 01. February 2016 20:42 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Monday, 01. February 2016 20:42 UTC
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Tuesday, 02. February 2016 08:02 UTC
+ kernel-stable-Promote-to-proposed-start:Tuesday, 02. February 2016 08:02 UTC
+ kernel-stable-phase-changed:Tuesday, 02. February 2016 08:02 UTC

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

Title:
  linux: 3.19.0-50.56 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 01. February 2016 20:42 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Tuesday, 02. February 2016 08:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 02. February 2016 08:02 UTC
  kernel-stable-phase-changed:Tuesday, 02. February 2016 08:02 UTC

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

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

[Kernel-packages] [Bug 1540721] Re: linux-armadaxp: 3.2.0-1662.86 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.2.0-1662.86 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, 02. February 2016 04:02 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 02. February 2016 04:02 UTC
  kernel-stable-master-bug:1540538
+ kernel-stable-Certification-testing-end:Tuesday, 02. February 2016 08:03 UTC
+ kernel-stable-Security-signoff-end:Tuesday, 02. February 2016 08:03 UTC

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

Title:
  linux-armadaxp: 3.2.0-1662.86 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-1662.86 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, 02. February 2016 04:02 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 02. February 2016 04:02 UTC
  kernel-stable-master-bug:1540538
  kernel-stable-Certification-testing-end:Tuesday, 02. February 2016 08:03 UTC
  kernel-stable-Security-signoff-end:Tuesday, 02. February 2016 08:03 UTC

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

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

[Kernel-packages] [Bug 1540792] [NEW] linux-lts-vivid: 3.19.0-50.56~14.04.1 -proposed tracker

[Brad Figg]

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-Prepare-package-start:Tuesday, 02. February 2016 08:00 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Tuesday, 02. February 2016 08:00 UTC
kernel-stable-master-bug:1540576

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

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

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

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

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

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

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

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

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

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

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

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

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

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


** Tags: block-proposed-trusty kernel-release-tracking-bug trusty

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

** Tags added: block-proposed-trusty

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

** Tags added: trusty

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  package linux-image-3.13.0-77-generic 3.13.0-77.121 failed to
  install/upgrade: Unterprozess installiertes post-installation-Skript
  gab den Fehlerwert 17 zurück

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I accidentally deleted the accordings vmlinuz-Image from the /boot directory 
but noticed my mistake before rebooting.
  So I tried to reinstall the corresponding packages.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-77-generic 3.13.0-77.121
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stefan 2096 F pulseaudio
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
  Date: Tue Feb  2 09:20:23 2016
  DuplicateSignature: 
package:linux-image-3.13.0-77-generic:3.13.0-77.121:Unterprozess installiertes 
post-installation-Skript gab den Fehlerwert 17 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 17 zurück
  HibernationDevice: RESUME=UUID=403aef84-f703-47f1-9ce3-731791c9738f
  InstallationDate: Installed on 2014-11-07 (451 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Hewlett-Packard Compaq 615
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic 
root=UUID=1bbc39d7-9038-4ac3-886c-ff7d1d4cfa6d ro quiet nosplash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.7
  SourcePackage: linux
  Title: package linux-image-3.13.0-77-generic 3.13.0-77.121 failed to 
install/upgrade: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 17 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68GVV Ver. F.0C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 308C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 27.08
  dmi.chassis.asset.tag: CNU00435BR
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68GVVVer.F.0C:bd11/23/2009:svnHewlett-Packard:pnCompaq615:pvrF.0C:rvnHewlett-Packard:rn308C:rvrKBCVersion27.08:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: Compaq 615
  dmi.product.version: F.0C
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1540798] [NEW] package linux-image-3.13.0-77-generic 3.13.0-77.121 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 17 zurück

[Stefan Abeln]

Public bug reported:

I accidentally deleted the accordings vmlinuz-Image from the /boot directory 
but noticed my mistake before rebooting.
So I tried to reinstall the corresponding packages.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-77-generic 3.13.0-77.121
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  stefan 2096 F pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
Date: Tue Feb  2 09:20:23 2016
DuplicateSignature: 
package:linux-image-3.13.0-77-generic:3.13.0-77.121:Unterprozess installiertes 
post-installation-Skript gab den Fehlerwert 17 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 17 zurück
HibernationDevice: RESUME=UUID=403aef84-f703-47f1-9ce3-731791c9738f
InstallationDate: Installed on 2014-11-07 (451 days ago)
InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
MachineType: Hewlett-Packard Compaq 615
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic 
root=UUID=1bbc39d7-9038-4ac3-886c-ff7d1d4cfa6d ro quiet nosplash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.7
SourcePackage: linux
Title: package linux-image-3.13.0-77-generic 3.13.0-77.121 failed to 
install/upgrade: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 17 zurück
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68GVV Ver. F.0C
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 308C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 27.08
dmi.chassis.asset.tag: CNU00435BR
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68GVVVer.F.0C:bd11/23/2009:svnHewlett-Packard:pnCompaq615:pvrF.0C:rvnHewlett-Packard:rn308C:rvrKBCVersion27.08:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: Compaq 615
dmi.product.version: F.0C
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-3.13.0-77-generic 3.13.0-77.121 failed to
  install/upgrade: Unterprozess installiertes post-installation-Skript
  gab den Fehlerwert 17 zurück

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I accidentally deleted the accordings vmlinuz-Image from the /boot directory 
but noticed my mistake before rebooting.
  So I tried to reinstall the corresponding packages.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-77-generic 3.13.0-77.121
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stefan 2096 F pulseaudio
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
  Date: Tue Feb  2 09:20:23 2016
  DuplicateSignature: 
package:linux-image-3.13.0-77-generic:3.13.0-77.121:Unterprozess installiertes 
post-installation-Skript gab den Fehlerwert 17 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 17 zurück
  HibernationDevice: RESUME=UUID=403aef84-f703-47f1-9ce3-731791c9738f
  InstallationDate: Installed on 2014-11-07 (451 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Hewlett-Packard Compaq 615
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic 
root=UUID=1bbc39d7-9038-4ac3-886c-ff7d1d4cfa6d ro quiet nosplash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.7
  SourcePackage: linux
  Title: package linux-image-3.13.0-77-generic 3.13.0-77.121 failed to 
install/upgrade: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 17 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68GVV Ver. F.0C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 308C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 27.08
  dmi.chassis.asset.tag: CNU00435BR
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

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

[Michael Doube]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1536555/+attachment/4561931/+files/IwConfig.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Michael Doube]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1536555/+attachment/4561933/+files/Lsusb.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Michael Doube]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1536555/+attachment/4561932/+files/Lspci.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Michael Doube]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1536555/+attachment/4561940/+files/UdevDb.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1536555] Re: USB3 devices are not active early in boot

[Michael Doube]

apport information

** Tags added: apport-collected

** Description changed:

  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04
  
  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include USBx
  devices plugged into USB2 ports (these work fine).
  
  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu
  
  Observed outcome:
  Selection of boot options is not possible
  
  Expected outcome:
  Selection of boot options is possible
  
  Also, a few people have noticed that they can't boot from media plugged
  into their USB3 ports, for example a flash drive with a Live CD image on
  it. (e.g. http://ubuntuforums.org/showthread.php?t=1628665)
  
  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.
  
- I know I could plug my keyboard into a USB2 port as it was before, but I
- have these new monitors that have got only USB3 ports on them, and it's
- physically more convenient to plug keyboard & mouse into them than the
- workstation itself (Dell T7600), which is a bit far for the cables to
- reach.
+ I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.19
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  mdoube 2897 F pulseaudio
+  /dev/snd/controlC1:  mdoube 2897 F pulseaudio
+  /dev/snd/controlC0:  mdoube 2897 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
+ InstallationDate: Installed on 2015-10-12 (112 days ago)
+ InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
+ MachineType: Dell Inc. Precision T7600
+ NonfreeKernelModules: nvidia
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
+ ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
+ RelatedPackageVersions:
+  linux-restricted-modules-3.19.0-47-generic N/A
+  linux-backports-modules-3.19.0-47-generic  N/A
+  linux-firmware 1.127.20
+ RfKill:
+  
+ Tags:  trusty
+ Uname: Linux 3.19.0-47-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/29/2014
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A12
+ dmi.board.asset.tag: RVCDoube0
+ dmi.board.name: 082WXT
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A01
+ dmi.chassis.asset.tag: RVCDoube0
+ dmi.chassis.type: 7
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
+ dmi.product.name: Precision T7600
+ dmi.product.version: 01
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1536555/+attachment/4561927/+files/AlsaInfo.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 

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

[Michael Doube]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1536555/+attachment/4561930/+files/CurrentDmesg.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Michael Doube]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1536555/+attachment/4561929/+files/CRDA.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Michael Doube]

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1536555/+attachment/4561928/+files/BootDmesg.txt

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

Title:
  USB3 devices are not active early in boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
  lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS (up-to-date packages)
  Release:  14.04

  USB3-plugged devices do not function early in the boot process. This
  includes USB2 devices plugged into USB3 ports, but does not include
  USBx devices plugged into USB2 ports (these work fine).

  To reproduce:
  1. plug keyboard into USB3 port, computer off
  2. boot
  3. attempt to select options in the GRUB menu

  Observed outcome:
  Selection of boot options is not possible

  Expected outcome:
  Selection of boot options is possible

  Also, a few people have noticed that they can't boot from media
  plugged into their USB3 ports, for example a flash drive with a Live
  CD image on it. (e.g.
  http://ubuntuforums.org/showthread.php?t=1628665)

  I guess this has something to do with whether the usb3 drivers are
  available at this early stage of boot: later on, after the full kernel
  is loaded, USB3 works fine.

  I know I could plug my keyboard into a USB2 port as it was before, but I have 
these new monitors that have got only USB3 ports on them, and it's physically 
more convenient to plug keyboard & mouse into them than the workstation itself 
(Dell T7600), which is a bit far for the cables to reach.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mdoube 2897 F pulseaudio
   /dev/snd/controlC1:  mdoube 2897 F pulseaudio
   /dev/snd/controlC0:  mdoube 2897 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=8629e880-0342-46f8-9392-7b5444e0ef96
  InstallationDate: Installed on 2015-10-12 (112 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64+mac 
(20150805)
  MachineType: Dell Inc. Precision T7600
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-47-generic 
root=UUID=7ce67a28-3ea8-4919-8a6e-f57670d56652 ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-47-generic N/A
   linux-backports-modules-3.19.0-47-generic  N/A
   linux-firmware 1.127.20
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.19.0-47-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/29/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.asset.tag: RVCDoube0
  dmi.board.name: 082WXT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: RVCDoube0
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/29/2014:svnDellInc.:pnPrecisionT7600:pvr01:rvnDellInc.:rn082WXT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T7600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1540435] Re: Introducing ConnectX-4 Ethernet SRIOV

[Talat Batheesh]

Thank you Tim,

All this patches is accepted to upstream.

could you please tell me how can i acsess the Launchpad github ? 
can i backport them on my setup and attach the patches ? 

thanks,
Talat

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

Title:
  Introducing ConnectX-4 Ethernet SRIOV

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  This patchset introduces the support of Ethernet SRIOV in ConnectX-4 
  family of 100G Ethernet NICs.

  Basic Introduction:
  ConnectX-4 HW architecture provides two kinds of underlying HW switches.

  MPFS (Multi Physical Function Switch) or L2 Table in Software terms:

  The HCA has one MPFS switch per physical port, this switch is responsible
  of forwarding Unicast traffic to the various overlying Physical Functions 
(PFs). 
  Multicast traffic is flooded amongst all the PFs, Each PF can request to
  forward a unicast MAC to its E-Switch Uplink vport (which we will cover 
later) 
  through SET_L2_TABLE_ENTRY HW command.

  MPFS has five ports, four are connected to PFs (one for each) and one is 
connected 
  directly to the Physical Port (Physical Link).

  E-Switch (Ethernet Switch):

  The HCA has one per physical function. The main responsibility of this 
component is 
  to forward Unicast/Multicast and vlan tagged/untagged traffic to the various 
  Virtual Functions (VFs) allocated by the PF. Unlike MPFS, the PF needs to 
explicitly 
  create the E-Switch FDB table, Which is a HW flow table managed by the PF 
driver 
  whenever vport_group_manager capability bit is set for this PF.

  E-Switch has Virtual Ports (vports) entities as its ports, vport0 and uplink 
vport
  are special kind of vports that represents PF vport (vport0) and uplink vport 
which
  is connected to the MPFS switch (if exists) as the PF external link.
  vport1..vportN represent VF0..VF(N-1) egress/ingress ports.

  E-Switch FDB contains forwarding rules such as:
  UC MAC0 -> vport0(PF).
  UC MAC1 -> vport1.
  UC MAC2 -> vport2.
  MC MACX -> vport0, vport2, Uplink.
  MC MACY -> vport1, Uplink.
  
  For unmatched traffic FDB has the following default rules:
  Unmatched Traffic (src vport != Uplink) -> Uplink.
  Unmatched Traffic (src vport == Uplink) -> vport0(PF).

  NIC VPort context: 
  Each NIC (VF/PF) has its own vport context which will be used to store the 
current
  NIC vport context (UC/MC and vlan lists) and other NIC properties such as 
MTU, promisc 
  mode, etc.. NIC (VF/PF) driver is responsible of constantly updating this 
context.

  FDB rules population:
  Each NIC vport (VF/PF) will notify E-Switch manager of its UC/MC vport
  context changes via modify vport context command, which will be
  translated to an event that will be handled by E-Switch manager (PF)
  which will update FDB table accordingly.

  Both PF and VF use the same driver and submit commands directly to the 
firmware.
  The PF sees the vport_group_manager capability bit and as such runs the code
  to populate the embedded switches as explained above.

  The patch goes as follows:

  Patches 1-2 introduces the basic PCI SRIOV functionalities and the support of
  Connectx4 to enable specific VFs via enable/disable HCA commands. These two
  patches will be also in use later for the IB SRIOV flow.

  Patches 3-8 Introduces the basic E-Switch capabilities and commands to be 
used later by
  VF to modify and update its NIC vport context, and by PF (E-Switch Manager) 
driver to
  Query the VF NIC context and acts accordingly.

  Patches 9-10 Provide the needed functionality of a NIC driver VF/PF to 
support SRIOV,
  mainly vport context update support.

  Patch 11 ("net/mlx5: Introducing E-Switch and l2 table"), Introduces the basic
  E-Switch support and infrastructure to read vport context events and to update
  MPFS L2 Table of the UC mac addresses request by the PF.

  Patches 12-18 Introduces SRIOV enablemenet and E-Switch FDB table management
  It adds the Basic E-Swtich public API to set and get sriov properties to be 
used
  in PF netdev sriov ndos.

  Patchset was applied ontop of commit 3f8c0f7 "gianfar: use
  of_property_read_bool()"

  Saeed, Eli and Or.

  Eli Cohen (2):
net/mlx5_core: Modify enable/disable hca functions
net/mlx5_core: Add base sriov support

  Saeed Mahameed (18):
net/mlx5: Add HW capabilities and structs for SR-IOV E-Switch.
net/mlx5: Update access functions to Query/Modify vport MAC address
net/mlx5: Introduce access functions to modify/query vport mac lists
net/mlx5: Introduce access functions to modify/query vport state
net/mlx5: Introduce access functions to modify/query vport promisc mode
net/mlx5: Introduce access functions to modify/query vport vlans
net/mlx5e: Write UC/MC list and promisc mode into vport context
net/mlx5e: Write