[Kernel-packages] [Bug 1603862] Re: [i915_bpo] tainted kernel: lspci, udevadm crashed

[Yung Shen]

** Tags added: 201508-19027 taipei-lab

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

Title:
  [i915_bpo] tainted kernel: lspci, udevadm crashed

Status in linux package in Ubuntu:
  Triaged

Bug description:
  while verifying bug #1599109 , I'm not able to use certain commands:
  lspci, udevadm

  steps to reproduce:
  1. fresh isntall
  2. install testing kernel

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

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

[Kernel-packages] [Bug 1603719] Re: NFS client: access problems after updating to kernel 4.4.0-31-generic

[Scott Merrilees]

Same problem. Reverted to 4.4.0-28. Didn't try mainline as -28 was
sufficient.

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

Title:
  NFS client: access problems after updating to kernel 4.4.0-31-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am denied access to the subfilesystems exported by my nfs server
  (the top level filesystem itself is unaffected).

  The client is reporting that I do not have the necessary permissions.
  However, all was fine until the day before yesterday.

  When I revert my client to 4.4.0-28, everything is in working order again. I 
assume the permission problem is really a bug in kernel 4.4.0-31.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jurgen 1743 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=569da237-3a37-4fe3-b885-83213aae8b52
  InstallationDate: Installed on 2016-04-07 (101 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7514
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=f6f6bd51-4d4f-4547-b615-90319625d909 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/28/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7514
  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.1:bd05/28/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7514:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7514:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7514
  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/1603719/+subscriptions

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

[Kernel-packages] [Bug 1577099] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in linux package in Ubuntu:
  Expired

Bug description:
  Graphical glitches in Firefox.

  Gere is dmesg log when it happens.
  [97970.020983] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [97970.021023] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  linux-image-generic:
Установлен: 4.4.0.21.22
Кандидат:   4.4.0.21.22

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   sam2091 F...m pulseaudio
   /dev/snd/controlC0:  sam2091 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May  1 12:23:21 2016
  HibernationDevice: RESUME=UUID=478fdfc2-ea5f-4e80-a404-cf3230067630
  InstallationDate: Installed on 2016-04-16 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160415)
  MachineType: LENOVO 25372A2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=b5bacb2b-487f-4164-ba6f-e8d22ab6c97e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET80WW (1.40 )
  dmi.board.name: 25372A2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET80WW(1.40):bd12/01/2011:svnLENOVO:pn25372A2:pvrThinkPadT410:rvnLENOVO:rn25372A2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 25372A2
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1604099] Re: linux: 3.2.0-107.148 -proposed tracker

[Brad Figg]

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   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/1604099

Title:
  linux: 3.2.0-107.148 -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-lbm 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 verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.2.0-107.148 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

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1604134] Re: linux: 3.13.0-93.140 -proposed tracker

[Brad Figg]

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   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/1604134

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

Bug description:
  This bug is for tracking the 3.13.0-93.140 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

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

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

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

Re: [Kernel-packages] [Bug 1603810] Re: Ubuntu turns monitor permanently off during boot

[Jason Gunthorpe]

On Mon, Jul 18, 2016 at 2:48 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Does booting back into the Trusty kernel on the Xenial installed system
> make the bug go away?
>

Yes. I've done multiple reboot experiments now and have learned the bug
only happens about 80% of the time, so I did all of these will multiple
reboots each:

3.16.0-77 GOOD
3.19.0-65 GOOD
4.2.0-42 BAD
4.4.0-31 BAD

All generic versions, 4.4 was using the .efi.signed variant.

I've attached the dmesg for 3.19-65

BTW, none of the kernels manage a seamless graphical boot like Windows
does. All successes sit at black screens for a long time then transition to
the splash for maybe 0.5s then into the graphical login (after another
black screen flash). Come to think of it, I don't think I've ever seen
Ubuntu do this properly on any release on any hardware I've tried (at least
with EFI boot). Even my HP's at work sit at a black screen for more time
than the splash. So I don't understand why Canonical bothers with the
vt_handoff stuff, when it seems *worse* on than off. At least without
vt_handoff you get something that looks like a running computer instead of
black screen.. That said, I think it works better with BIOS boot ??

Windows 7 & 10 both do this perfectly in EFI mode, the monitor is never
black.

Jason

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

Title:
  Ubuntu turns monitor permanently off during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a regression, at least trusty (and prior) worked fine on this
  hardware.

  Booting the Xenial installer image off USB also worked fine.

  The system boots fine, however the monitor is in DPMS power-off and
  does not ever turn back on. Switching VTs doesn't help, I have found
  no way to get it switch on.

  Removing '$vt_handoff' from grub resolves the problem and the system
  seems to work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jgg2224 F pulseaudio
   /dev/snd/controlC0:  jgg2224 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jul 17 14:04:30 2016
  HibernationDevice: RESUME=UUID=b254872c-e84b-427c-bebe-343c031cbdcd
  InstallationDate: Installed on 2016-04-22 (86 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/main2-xenial64 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M EVO
  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.:bvr0805:bd11/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MEVO: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/1603810/+subscriptions

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

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

[Mike Rushton]

Attached is the kern.log from the Firestone PowerNV server. This one is
failing with stack traces which only started after we started testing
patched kernels.

The Habanero PowerNV failed with the typical locked up console and
OOM's.

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4703165/+files/kern.log

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

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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

[Kernel-packages] [Bug 1603449] Re: [LTCTest][Opal][OP820] Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1] while executing Froze PE Error injection

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-July/079193.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/1603449

Title:
  [LTCTest][Opal][OP820] Machine crashed with Oops: Kernel access of bad
  area, sig: 11 [#1] while executing Froze PE Error injection

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  In Progress

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2016-07-13 
01:28:56 ==
  ---Problem Description---
  Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1]
   
  ---uname output---
  Linux ltc-garri2 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  root@ltc-garri2:~# lspci
  :00:00.0 PCI bridge: IBM Device 03dc
  :01:00.0 Infiniband controller: Mellanox Technologies MT27600 [Connect-IB]
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0002:00:00.0 PCI bridge: IBM Device 03dc
  0002:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0003:00:00.0 PCI bridge: IBM Device 03dc
  0004:00:00.0 PCI bridge: IBM Device 03dc
  0005:00:00.0 PCI bridge: IBM Device 03dc
  0005:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:02.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:03.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:04.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller (rev 02)
  0005:04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 
x2 4-port SATA 6 Gb/s Controller (rev 11)
  0005:05:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge 
(rev 03)
  0005:06:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED 
Graphics Family (rev 30)
  0005:07:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0005:07:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0006:00:00.0 PCI bridge: IBM Device 03dc
  0006:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0007:00:00.0 PCI bridge: IBM Device 03dc
  0008:00:00.0 Bridge: IBM Device 04ea
  0008:00:00.1 Bridge: IBM Device 04ea
  0008:00:01.0 Bridge: IBM Device 04ea
  0008:00:01.1 Bridge: IBM Device 04ea
  0009:00:00.0 Bridge: IBM Device 04ea
  0009:00:00.1 Bridge: IBM Device 04ea
  0009:00:01.0 Bridge: IBM Device 04ea
  0009:00:01.1 Bridge: IBM Device 04ea
   

   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Install a P8 Open Power 8335-GTB Hardware with Ubuntu 16.04.1.
  Then execute the Frozen PE error injection tests as shown below:

  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0

  
  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0
  root@ltc-garri2:~# echo 0:0:4:0:0 > 
/sys/kernel/debug/powerpc/PCI0004/err_injct && lspci -ns 0004:00:00.0; echo $?
  0004:00:00.0 0604: 1014:03dc
  0

  Immediately the kernel crashes with a Oops Message.
   
  Contact Information = pavsu...@in.ibm.com 
   
  Stack trace output:
   [  289.297946] Call Trace:
  [  289.297969] [c00feeb8b9e0] [c0083c78] pnv_eeh_reset+0x58/0x170 
(unreliable)
  [  289.298042] [c00feeb8ba60] [c0038250] eeh_reset_pe+0xb0/0x1c0
  [  289.298105] [c00feeb8bb00] [c0af444c] 
eeh_reset_device+0xd8/0x228
  [  289.298165] [c00feeb8bba0] [c003c520] 
eeh_handle_normal_event+0x390/0x440
  [  289.298234] [c00feeb8bc20] [c003c9c4] 
eeh_handle_event+0x184/0x370
  [  289.298304] [c00feeb8bcd0] [c003cd88] 
eeh_event_handler+0x1d8/0x1e0
  [  289.298374] [c00feeb8bd80] [c00e6420] kthread+0x110/0x130
  [  289.298434] [c00feeb8be30] [c0009538] 
ret_from_kernel_thread+0x5c/0xa4
  [  289.298501] Instruction dump:
  [  289.298531] 6000 813f ebdf0010 792affe3 408200d4 e95e0250 812a000c 
2f890002
  [  289.298630] 419e0054 7fe3fb78 4bfb70c5 6000  2fa9 
419e00dc e9290010

   
  Oops output:
   [  289.294622] EEH: Frozen PE#0 on PHB#4 detected
  [  289.294785] EEH: PE location: N/A, PHB location: N/A
  [  289.295598] EEH: This PCI device has failed 1 times in the last hour
  [  

[Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled

[Pablo Saavedra]

BTW, I am having the issue in 14.04, after upgrading to kernel
3.19.0-65-generic. Booting with 3.19.0-64-generic and reinstalling
bcmwl-kernel-source fixes the problem.

I think we need proper instructions to sign the module, or an automated
step that takes care of that for us.

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21 when secure boot
  enabled

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works.

  If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21
  and wifi works.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1602371] Re: Touchpad incorrectly detected as PS/2 mouse in 'HP Pavillion 340G1' after Ubuntu 12.04 upgrade to 14.04.

[Daniel Ojeda]

I tried to test the kernel that you mentioned, but unfortunately, I get
an error (can't create /sys/kernel/uevent_helper), so I couldn't start
the system with that 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/1602371

Title:
  Touchpad incorrectly detected as PS/2 mouse in 'HP Pavillion 340G1'
  after Ubuntu 12.04 upgrade to 14.04.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm currently using Linux 4.2.0-38-generic Kernel.

  
  I adjunct in a .txt the outputs for 
  -dmesg
  -cat /proc/bus/input/devices 

  Regards

  Daniel Ojeda
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  do 3758 F pulseaudio
   /dev/snd/controlC0:  do 3758 F pulseaudio
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-yuanli-precise-amd64-20131009-1
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=93204dde-91fd-41de-b63a-8c49d4903331
  InstallationDate: Installed on 2015-07-13 (365 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20131009-06:05
  MachineType: Hewlett-Packard HP 340 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-38-generic 
root=UUID=8fb79e40-a483-431f-ae1f-b6430988c9fd ro quiet splash i8042.reset 
i8042.nomux i8042.nopnp i8042.noloop vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-38-generic N/A
   linux-backports-modules-4.2.0-38-generic  N/A
   linux-firmware1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 4.2.0-38-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-07-13 (364 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/12/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 21B7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 46.0B
  dmi.chassis.asset.tag: 5CG4471R2Q
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd06/12/2014:svnHewlett-Packard:pnHP340G1:pvr099810167:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 340 G1
  dmi.product.version: 099810167
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled

[Pablo Saavedra]

I tried to solve it by following the instructions in
http://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-
upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur (with 'wl' as the
module) with no luck

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21 when secure boot
  enabled

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works.

  If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21
  and wifi works.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1603655] Re: After update, xorg will not boot

[Steve Langasek]

Given that your apport output is from the previous kernel, this line is
very suggestive:

[   18.073838] fglrx: module verification failed: signature and/or
required key missing - tainting kernel

The 3.13.0-92 kernel is the first one in this series which implements
Ubuntu's updated SecureBoot policy, which requires specific action by
the machine administrator in order to allow unsigned modules.

You should have been prompted for this on upgrade.  Do you remember
seeing such a prompt?

Can you please attach the output of the following command:
$ debconf-show shim-signed

To successfully upgrade to the new kernel, you will want to:

 - run 'sudo update-secureboot-policy', and choose to disable SecureBoot
 - run 'sudo apt-get install linux-signed-image-generic'
 - reboot to the UEFI prompts, in order to confirm the SecureBoot policy change.

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

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[bugproxy]

--- Comment From gws...@au1.ibm.com 2016-07-18 21:21 EDT---
Yeah, There is only one patch should be backported and it should fix the kernel 
crash. The patch is backported to Ubuntu-4.4.0-31.50 and attached. Note I 
checked out the base kernel code from below git repo:

git://kernel.ubuntu.com/ubuntu/ubuntu-xenial.git (branch: master)

Another patch (as below link shows) cann't be backported to ubuntu 4.4.0
yet as the fix depends on EEH support for SRIOV which isn't there. Lets
backport it when needed.

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=cca0e542e02e48cce541a49c4046ec094ec27c1e
. ("powerpc/eeh: Fix wrong argument passed to eeh_rmv_device()")

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

Title:
  [LTCTest][Opal][OP820] Machine crashed with Oops: Kernel access of bad
  area, sig: 11 [#1] while executing Froze PE Error injection

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  In Progress

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2016-07-13 
01:28:56 ==
  ---Problem Description---
  Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1]
   
  ---uname output---
  Linux ltc-garri2 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  root@ltc-garri2:~# lspci
  :00:00.0 PCI bridge: IBM Device 03dc
  :01:00.0 Infiniband controller: Mellanox Technologies MT27600 [Connect-IB]
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0002:00:00.0 PCI bridge: IBM Device 03dc
  0002:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0003:00:00.0 PCI bridge: IBM Device 03dc
  0004:00:00.0 PCI bridge: IBM Device 03dc
  0005:00:00.0 PCI bridge: IBM Device 03dc
  0005:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:02.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:03.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:04.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller (rev 02)
  0005:04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 
x2 4-port SATA 6 Gb/s Controller (rev 11)
  0005:05:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge 
(rev 03)
  0005:06:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED 
Graphics Family (rev 30)
  0005:07:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0005:07:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0006:00:00.0 PCI bridge: IBM Device 03dc
  0006:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0007:00:00.0 PCI bridge: IBM Device 03dc
  0008:00:00.0 Bridge: IBM Device 04ea
  0008:00:00.1 Bridge: IBM Device 04ea
  0008:00:01.0 Bridge: IBM Device 04ea
  0008:00:01.1 Bridge: IBM Device 04ea
  0009:00:00.0 Bridge: IBM Device 04ea
  0009:00:00.1 Bridge: IBM Device 04ea
  0009:00:01.0 Bridge: IBM Device 04ea
  0009:00:01.1 Bridge: IBM Device 04ea
   

   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Install a P8 Open Power 8335-GTB Hardware with Ubuntu 16.04.1.
  Then execute the Frozen PE error injection tests as shown below:

  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0

  
  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0
  root@ltc-garri2:~# echo 0:0:4:0:0 > 
/sys/kernel/debug/powerpc/PCI0004/err_injct && lspci -ns 0004:00:00.0; echo $?
  0004:00:00.0 0604: 1014:03dc
  0

  Immediately the kernel crashes with a Oops Message.
   
  Contact Information = pavsu...@in.ibm.com 
   
  Stack trace output:
   [  289.297946] Call Trace:
  [  289.297969] [c00feeb8b9e0] [c0083c78] pnv_eeh_reset+0x58/0x170 
(unreliable)
  [  289.298042] [c00feeb8ba60] [c0038250] eeh_reset_pe+0xb0/0x1c0
  [  289.298105] [c00feeb8bb00] [c0af444c] 
eeh_reset_device+0xd8/0x228
  [  289.298165] [c00feeb8bba0] [c003c520] 
eeh_handle_normal_event+0x390/0x440
  [  289.298234] [c00feeb8bc20] [c003c9c4] 
eeh_handle_event+0x184/0x370
  [  289.298304] [c00feeb8bcd0] 

[Kernel-packages] [Bug 1603449] Backported fix to Ubuntu-4.4.0-31.50

[bugproxy]

--- Comment (attachment only) From gws...@au1.ibm.com 2016-07-18 21:15 
EDT---


** Attachment added: "Backported fix to Ubuntu-4.4.0-31.50"
   
https://bugs.launchpad.net/bugs/1603449/+attachment/4703137/+files/0001-powerpc-eeh-Fix-invalid-cached-PE-primary-bus.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/1603449

Title:
  [LTCTest][Opal][OP820] Machine crashed with Oops: Kernel access of bad
  area, sig: 11 [#1] while executing Froze PE Error injection

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  In Progress

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2016-07-13 
01:28:56 ==
  ---Problem Description---
  Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1]
   
  ---uname output---
  Linux ltc-garri2 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  root@ltc-garri2:~# lspci
  :00:00.0 PCI bridge: IBM Device 03dc
  :01:00.0 Infiniband controller: Mellanox Technologies MT27600 [Connect-IB]
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0002:00:00.0 PCI bridge: IBM Device 03dc
  0002:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0003:00:00.0 PCI bridge: IBM Device 03dc
  0004:00:00.0 PCI bridge: IBM Device 03dc
  0005:00:00.0 PCI bridge: IBM Device 03dc
  0005:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:02.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:03.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:04.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller (rev 02)
  0005:04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 
x2 4-port SATA 6 Gb/s Controller (rev 11)
  0005:05:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge 
(rev 03)
  0005:06:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED 
Graphics Family (rev 30)
  0005:07:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0005:07:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0006:00:00.0 PCI bridge: IBM Device 03dc
  0006:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0007:00:00.0 PCI bridge: IBM Device 03dc
  0008:00:00.0 Bridge: IBM Device 04ea
  0008:00:00.1 Bridge: IBM Device 04ea
  0008:00:01.0 Bridge: IBM Device 04ea
  0008:00:01.1 Bridge: IBM Device 04ea
  0009:00:00.0 Bridge: IBM Device 04ea
  0009:00:00.1 Bridge: IBM Device 04ea
  0009:00:01.0 Bridge: IBM Device 04ea
  0009:00:01.1 Bridge: IBM Device 04ea
   

   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Install a P8 Open Power 8335-GTB Hardware with Ubuntu 16.04.1.
  Then execute the Frozen PE error injection tests as shown below:

  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0

  
  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0
  root@ltc-garri2:~# echo 0:0:4:0:0 > 
/sys/kernel/debug/powerpc/PCI0004/err_injct && lspci -ns 0004:00:00.0; echo $?
  0004:00:00.0 0604: 1014:03dc
  0

  Immediately the kernel crashes with a Oops Message.
   
  Contact Information = pavsu...@in.ibm.com 
   
  Stack trace output:
   [  289.297946] Call Trace:
  [  289.297969] [c00feeb8b9e0] [c0083c78] pnv_eeh_reset+0x58/0x170 
(unreliable)
  [  289.298042] [c00feeb8ba60] [c0038250] eeh_reset_pe+0xb0/0x1c0
  [  289.298105] [c00feeb8bb00] [c0af444c] 
eeh_reset_device+0xd8/0x228
  [  289.298165] [c00feeb8bba0] [c003c520] 
eeh_handle_normal_event+0x390/0x440
  [  289.298234] [c00feeb8bc20] [c003c9c4] 
eeh_handle_event+0x184/0x370
  [  289.298304] [c00feeb8bcd0] [c003cd88] 
eeh_event_handler+0x1d8/0x1e0
  [  289.298374] [c00feeb8bd80] [c00e6420] kthread+0x110/0x130
  [  289.298434] [c00feeb8be30] [c0009538] 
ret_from_kernel_thread+0x5c/0xa4
  [  289.298501] Instruction dump:
  [  289.298531] 6000 813f ebdf0010 792affe3 408200d4 e95e0250 812a000c 
2f890002
  [  289.298630] 419e0054 7fe3fb78 4bfb70c5 6000  2fa9 
419e00dc e9290010

   
  Oops 

[Kernel-packages] [Bug 1604099] Re: linux: 3.2.0-107.148 -proposed tracker

[Brad Figg]

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

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

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

Title:
  linux: 3.2.0-107.148 -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-lbm series:
  Confirmed
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 verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.2.0-107.148 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

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1603655] Re: After update, xorg will not boot

[dualBootLaptop]

> From a terminal window please run:
> apport-collect 1603655
> and then change the status of the bug to 'Confirmed'.

...okay? As I said, I apt-get removed linux-
image-3.13.0-92-generic:amd64, so the system information *now* will show
that it's not installed. The information just posted is the state of the
system when it's *working*. Is that what you wanted? Or did you want me
to reinstall linux-image-3.13.0-92-generic:amd64?

If you *do* want me to reinstall linux-image-3.13.0-92-generic:amd64,
can you tell me exactly how to do it? The Software Updater is showing me
the available updates right now, and the new linux-image is not on the
list, probably because the Software Updater noticed that I manually
uninstalled it and is assuming that I don't want anything I manually
uninstalled...which is actually pretty smart, that's kind of cool. But
it means that I don't know how to reproduce the installation process.
Should I apt-get dist-upgrade?

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

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] PulseList.txt

[dualBootLaptop]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1603655/+attachment/4703125/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] CurrentDmesg.txt

[dualBootLaptop]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1603655/+attachment/4703117/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] UdevDb.txt

[dualBootLaptop]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1603655/+attachment/4703126/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] ProcInterrupts.txt

[dualBootLaptop]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1603655/+attachment/4703123/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] BootDmesg.txt

[dualBootLaptop]

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1603655/+attachment/4703115/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] WifiSyslog.txt

[dualBootLaptop]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1603655/+attachment/4703128/+files/WifiSyslog.txt

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

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] CRDA.txt

[dualBootLaptop]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1603655/+attachment/4703116/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] UdevLog.txt

[dualBootLaptop]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1603655/+attachment/4703127/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] Re: After update, xorg will not boot

[dualBootLaptop]

apport information

** Tags added: apport-collected

** Description changed:

  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.
  
  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.21
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  david  1900 F pulseaudio
+  /dev/snd/controlC0:  david  1900 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
+ InstallationDate: Installed on 2014-06-06 (773 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
+ MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
+ NonfreeKernelModules: fglrx
+ Package: linux (not installed)
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-91-generic N/A
+  linux-backports-modules-3.13.0-91-generic  N/A
+  linux-firmware 1.127.22
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  trusty
+ Uname: Linux 3.13.0-91-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/11/2014
+ dmi.bios.vendor: Insyde
+ dmi.bios.version: F.35
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: 1984
+ dmi.board.vendor: Hewlett-Packard
+ dmi.board.version: 01.15
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Hewlett-Packard
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
+ dmi.product.name: HP Pavilion 17 Notebook PC
+ dmi.product.version: 0880100021305B1620100
+ dmi.sys.vendor: Hewlett-Packard

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1603655/+attachment/4703114/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have 

[Kernel-packages] [Bug 1603655] ProcModules.txt

[dualBootLaptop]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1603655/+attachment/4703124/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] Lspci.txt

[dualBootLaptop]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1603655/+attachment/4703119/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] ProcCpuinfo.txt

[dualBootLaptop]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1603655/+attachment/4703121/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] Lsusb.txt

[dualBootLaptop]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1603655/+attachment/4703120/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] ProcEnviron.txt

[dualBootLaptop]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1603655/+attachment/4703122/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603655] IwConfig.txt

[dualBootLaptop]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1603655/+attachment/4703118/+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/1603655

Title:
  After update, xorg will not boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Last night, Ubuntu Software Updater installed a round of updates.
  I shut down my computer, and when I booted this morning, the GUI failed to 
load or run at all.
  I switched to a terminal with Ctrl+Alt+F1, which worked fine.
  I tried rebooting into 3.13.0-91 via GRUB, at which point the GUI worked fine.
  Examining Ubuntu Software Center History, the new linux-image stood out, so I 
tried uninstalling that first.
  The command I ran was:
  sudo apt-get remove linux-image-extra-3.13.0-92-generic:amd64 
linux-image-3.13.0-92-generic:amd64 linux-signed-image-3.13.0-92-generic:amd64 
&& sudo apt-get install linux-image-extra-3.13.0-91-generic:amd64 
linux-image-3.13.0-91-generic:amd64 linux-signed-image-3.13.0-91-generic:amd64
  My machine works fine now (with the old linux-image), but I thought I should 
inform you of the problem with the new linux-image.

  P.S. Since xorg is involved I tried to use ubuntu-bug xorg as the 
instructions said, but there was no way to enter an explanation, and reporting 
system information with no explanation *now* when my system is *working* would 
be completely misleading. There seems to be no way to attach any text or 
message to an ubuntu-bug report.
  I have attached the output from apport-bug --save=bugfilename 
linux-image-3.13.0-92-generic:amd64.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1900 F pulseaudio
   /dev/snd/controlC0:  david  1900 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=907fdd35-197c-4341-9daa-c29636443fb6
  InstallationDate: Installed on 2014-06-06 (773 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic.efi.signed 
root=UUID=1fe70a4d-bce2-4bc1-921f-d793500b9af8 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-91-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1984
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd11/11/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0880100021305B1620100:rvnHewlett-Packard:rn1984:rvr01.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0880100021305B1620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1603288] Re: package linux-image-4.4.0-31-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before installi

[David]

Jsalisbury,
Your suggetion fits what I first attempted in order to correct the problem. 
The report presented here, above, followed that correction attempt. I used 
Bleachbit to clear out the issue after sudo apt-get update -f (-m) [the dash m 
was added following failure with -f alone] also failed.

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

Title:
  package linux-image-4.4.0-31-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-31-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Install attempted by Ubuntu Mate included Update Manager along with
  Grub2 update. The Grub2 update failed and according to the pop-up
  announcement by the Update Manager it also caused the  linux-
  image-4.4.0-31-generic installation failure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  2162 F pulseaudio
   /dev/snd/controlC0:  david  2162 F pulseaudio
  Date: Thu Jul 14 20:27:23 2016
  DuplicateSignature:
   package:linux-image-4.4.0-31-generic:(not installed)
   Unpacking linux-image-4.4.0-31-generic (4.4.0-31.50) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-31-generic_4.4.0-31.50_amd64.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=cf771e35-9679-4425-89bc-cdc68ab786e6
  InstallationDate: Installed on 2016-05-23 (53 days ago)
  InstallationMedia: It
  MachineType: GizmoSphere Gizmo2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=19bf53ad-e512-4435-bbde-ae92ffe72f2a ro elevator=noop quiet splash
  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-36ubuntu3.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-31-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: SageBios_Gizmo2-121
  dmi.chassis.type: 3
  dmi.chassis.vendor: GizmoSphere
  dmi.modalias: 
dmi:bvncoreboot:bvrSageBios_Gizmo2-121:bd04/10/2014:svnGizmoSphere:pnGizmo2:pvr1.0:cvnGizmoSphere:ct3:cvr:
  dmi.product.name: Gizmo2
  dmi.product.version: 1.0
  dmi.sys.vendor: GizmoSphere

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

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

[Kernel-packages] [Bug 1604134] Re: linux: 3.13.0-93.140 -proposed tracker

[Brad Figg]

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

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

** Description changed:

  This bug is for tracking the 3.13.0-93.140 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-phase:Packaging
- kernel-stable-phase-changed:Monday, 18. July 2016 20:01 UTC
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Monday, 18. July 2016 23:01 UTC

** Description changed:

  This bug is for tracking the 3.13.0-93.140 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
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 18. July 2016 23:01 UTC
+ phase: Uploaded

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

Title:
  linux: 3.13.0-93.140 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.13.0-93.140 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

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1586748] Re: Lubuntu 16.04 does not install on a non-pae processor

[Joseph Salisbury]

12.04 was the last release that will support non-PAE. The default (and
boot) kernel for 12.04 and newer 32 bit is now the PAE kernel, so there
is no easy way to install a non-PAE kernel.

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

Title:
  Lubuntu 16.04 does not install on a non-pae processor

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I have Acer Aspire 1410 notebook with Pentium M processor.I tried to install 
Lubuntu 16.04. When I used forcepae option two times in boot menu options 
installation begin. After a while installation stops always to: 
[drm:intel_set_cpu_fifo_underrun_reporting[i915] Error Pipe A unknown] And 
acerhdf unknown.
  Previous Lubuntu 14.04 installed went just fine, with forcepae option.

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

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

[Kernel-packages] [Bug 1340461] Re: Nikon CoolPix 5600 camera not recognized

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 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.7-rc7

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

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

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

Title:
  Nikon CoolPix 5600 camera not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  My Nikon Coolpix 5600 camera is not automatically detected (no icon in the 
Launcher or in "Devices"). However it appears in Shotwell.
  I can import photos from Canon A1000 IS camera with Shotwell but not from the 
Nikon (error message: Could not claim the USB device (-53))
  All the other USB devices work (webcam, flash drives, external HDD, mouse and 
keyboard).

  Ubuntu 14.04 LTS
  shotwell 0.18.0-0ubuntu4.1
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eunice 1512 F pulseaudio
   /dev/snd/controlC0:  eunice 1512 F pulseaudio
   /dev/snd/controlC1:  eunice 1512 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=cc08f480-3f55-4795-913e-9d4e75362876
  InstallationDate: Installed on 2014-10-25 (624 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: HP-Pavilion WE277AA-ABF p6352fr
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=60a2137c-a8ce-4769-836b-2d1dbdd00d11 ro radeon.dpm=0 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (79 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.07
  dmi.board.name: EVANS
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd01/26/2010:svnHP-Pavilion:pnWE277AA-ABFp6352fr:pvr:rvnPEGATRONCORPORATION:rnEVANS:rvr1.02:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: WE277AA-ABF p6352fr
  dmi.sys.vendor: HP-Pavilion

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

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

[Kernel-packages] [Bug 1602241] Re: "[drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS" messages in syslog

[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.7 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.7-rc7

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

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

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

Title:
  "[drm:gen6_sanitize_pm] *ERROR* Power management discrepancy:
  GEN6_RP_INTERRUPT_LIMITS" messages in syslog

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have two error messages on my Asustek UX32A laptop.
  They are:

  Jul 12 12:23:23 norbert-flash kernel: [   21.384213] [drm:gen6_sanitize_pm] 
*ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 
1800, was 1206
  Jul 12 15:23:43 norbert-flash kernel: [   41.084122] [drm:gen6_sanitize_pm] 
*ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 
1807, was 1800

  It seems that 3.2 kernel is not compatible with my CPU/GPU (Intel
  i7-3537U).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-generic-pae 3.2.0.101.117
  ProcVersionSignature: Ubuntu 3.2.0-104.145-generic-pae 3.2.79
  Uname: Linux 3.2.0-104-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  norbert2360 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d18000 irq 45'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,10431507,00100100 
HDA:80862806,80860101,0010'
 Controls  : 18
 Simple ctrls  : 8
  Date: Tue Jul 12 15:30:06 2016
  HibernationDevice: RESUME=UUID=29a538af-86ee-47e2-9e0f-225270b11d48
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-104-generic-pae 
root=UUID=cd849a78-bc1b-11e4-a81b-74d435a2779c ro verbose init=/sbin/init -v 
noplymouth mem=3536M
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-104-generic-pae N/A
   linux-backports-modules-3.2.0-104-generic-pae  N/A
   linux-firmware 1.79.18
  SourcePackage: linux
  StagingDrivers: rts5139 mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1600361] Re: NVME crashes Ubuntu 16.04

[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.7 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.7-rc7

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

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

Title:
  NVME crashes Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:Ubuntu 16.04 LTS  


  Release:16.04 

  On a brand new Supermicro Chassis (SuperServer 1028R-WTNRT) we have
  installed Ubuntu 16.04 onto a pair of SAMSUNG SM863 SSDs in soft Raid
  1. We originally tried to install Ubuntu 16.04 to two NVMe drives
  (Intel® SSD DC P3700) but the Ubuntu install could not see both
  drives, Only one. Howerver Ubuntu Server 14.04 saw them and worked
  perfectly. After the install to the SSDs I plugged in the two NVMe
  drives and the server has had nothing but issues since.

  I attached the dmesg errors.

  The errors seen in the dmesg file attached just continue to repeat
  over and over again. The server locks up and no longer responds.

  Any ideas or fixes would be appreciated.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:32 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-06-30 (11 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro SYS-1028R-WTNRT
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=124ae1c9-44f6-44b3-a199-11c8d63289d7 ro
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 02/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRW-NT
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd02/03/2016:svnSupermicro:pnSYS-1028R-WTNRT:pvr0123456789:rvnSupermicro:rnX10DRW-NT:rvr1.01A:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SYS-1028R-WTNRT
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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

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

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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

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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After login.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-71-generic 3.13.0-71.114
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  randy  2531 F pulseaudio
   /dev/snd/seq:timidity   1835 F timidity
  Date: Sat Jul  9 08:09:35 2016
  DuplicateSignature: 
package:linux-image-3.13.0-71-generic:3.13.0-71.114:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=025776db-61bd-4f31-bb9d-77904edf3c06
  InstallationDate: Installed on 2014-07-18 (724 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP G62 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-91-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.8
  SourcePackage: linux
  Title: package linux-image-3.13.0-71-generic 3.13.0-71.114 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1484
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 77.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd04/26/2010:svnHewlett-Packard:pnHPG62NotebookPC:pvr04991100032027102:rvnHewlett-Packard:rn1484:rvr77.18:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP G62 Notebook PC
  dmi.product.version: 04991100032027102
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1600648] Re: Generic USB Mass Storare Failure

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 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.7-rc7

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

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

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

Title:
  Generic USB Mass Storare Failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I realize this is not a reporting a bug for a specific situation but after 
collecting numerous reports from equally numerous forums I cannot make another 
analysis that there something very wrong crept into Linux regarding mounting 
and handling USB Mass Storage. None of the suggestions I found worked, and I 
dare to say the same goes for the major part of others with their problems as 
well.
  May be it's time to stop with trying to solve each individual problem, 
usually without any success as I followed the discussions, but go back to 
"point zero" and fix this horrible bug.
  FYI: I noticed that mounting USB Mass Storage worked on earlier releases.

  BTW. my system:
  Mint 17.2 Rafaela
  Linux Kernel: 3.16.0-38-generic
  Ubuntu: 52~14.04.1-Ubuntu SMP

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

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

[Kernel-packages] [Bug 1600151] Re: CRU Dataport with 4T SATA disk get disconnected on USB3 port

[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.7 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.7-rc7


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

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

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

Title:
  CRU Dataport with 4T SATA disk get disconnected on USB3 port

Status in linux-lts-trusty package in Ubuntu:
  Incomplete

Bug description:
  When connected a CRU dataport (with a 4T HD SATA disc) connected to a USB3 
port, the volume is correctly mounted.
  I then copy the HD content to my workstation.
  But after several seconds (between 10s to 2mn), the device is disconnected 
and can't be seen anymore by the system until i power off the CRU and power on 
it back.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-36-generic 3.13.0-36.63~precise1
  ProcVersionSignature: Ubuntu 3.13.0-36.63~precise1-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-36-generic.
  ApportVersion: 2.0.1-0ubuntu17.7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: ALC668 Analog [ALC668 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf7d34000 irq 50'
 Mixer name : 'Intel Haswell HDMI'
 Components : 'HDA:80862807,80860101,0010'
 Controls  : 14
 Simple ctrls  : 2
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xf7d3 irq 49'
 Mixer name : 'Realtek ALC668'
 Components : 'HDA:10ec0668,10280625,0013'
 Controls  : 25
 Simple ctrls  : 11
  CurrentDmesg:
   [   17.211767] NFSD: starting 90-second grace period (net 81cd9040)
   [   20.657622] init: plymouth-stop pre-start process (1528) terminated with 
status 1
  Date: Fri Jul  8 10:46:50 2016
  HibernationDevice: RESUME=UUID=649b1c40-885b-43f9-8ad3-c91a7154255b
  InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release 
amd64 (20140806.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. OptiPlex 9030 AIO
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=0cb8b199-2ce9-4040-8948-2d91334c83f1 ro site=frtst14 
network=10.114.195.0/24 type=orc env=ymagis quiet
  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-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.79.18
  RfKill:
   
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0VNGWR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd03/22/2016:svnDellInc.:pnOptiPlex9030AIO:pvr00:rvnDellInc.:rn0VNGWR:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.name: OptiPlex 9030 AIO
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1600371] Re: Gnome freezes for some seconds on simultaneous touch and stylus input (palm rejection fails)

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 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.7-rc7

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

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

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

Title:
  Gnome freezes for some seconds on simultaneous touch and stylus input
  (palm rejection fails)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My notebook (Lenovo Yoga S1) has a capacitive touch screen as well as
  an inductive screen for styluses. When I rest my palm on the screen
  and then hover my stylus above the screen so that the stylus is
  recognized and the mouse pointer follows it, and then move the stylus
  around Gnome seems to freeze for some seconds. The duration of the
  freeze is proportional to the time the notebook received simultaneous
  input from the two methods.

  "Freeze" means that the screen is not updated. Keyboard inputs that I
  make during the freeze would be executed after the freezing stops.

  I do not need to touch the screen with the stylus for the bug to
  occur. The bug occurs also when I actually touch the screen with the
  stylus.

  What I expect to happen (and what actually happens in all stylus-
  supporting tablets, running with Android or Windows) is that the input
  from the touch screen is rejected as long as the stylus is hovering
  above the screen.

  I'm running Ubuntu Gnome 16.04 (non-LTS) with the latest packages. The
  problem was present in 15.10 as well.

  I attach a script as a workaround solution.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  timeshifter   1787 F pulseaudio
   /dev/snd/controlC0:  timeshifter   1787 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=87cca434-274f-4464-9598-97fd7a1338fe
  InstallationDate: Installed on 2016-03-19 (111 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 20C0003SFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e52c99ea-9646-4e8a-b8ad-c47b175ac5a3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-02 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare scanner sudo vboxusers 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0ET33WW (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0003SFR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0ET33WW(1.20):bd04/29/2016:svnLENOVO:pn20C0003SFR:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0003SFR:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0003SFR
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1600346] Re: On irq_work_run_list function issue.

[Joseph Salisbury]

Thank you for providing a patch, and making Ubuntu better.

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

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

Title:
  On irq_work_run_list function issue.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Below is result of perf report:

  irq_work_run_list  /proc/kcore
   
 │  
  ◆
 │  
  ▒
 │  
  ▒
 │Disassembly of section load0: 
  ▒
 │  
  ▒
 │811713a0 : 
  ▒
 │  pushfq  
  ▒
 │  pop%rax 
  ▒
 │  nop 
  ▒
 │  and$0x200,%eax  
  ▒
 │↓ jne69   
  ▒
 │  push   %rbp 
  ▒
 │  mov%rsp,%rbp
  ▒
 │  push   %r14 
  ▒
 │  push   %r13 
  ▒
 │  push   %r12 
  ▒
 │  push   %rbx 
  ▒
 │  mov%rax,%rbx
  ▒
 │  mov(%rdi),%rax  
  ▒
  100,00 │  test   %rax,%rax
  ▒
 │↓ je 60   
  ▒
 │  xchg   %rbx,(%rdi)  
  ▒
 │  test   %rbx,%rbx
  ..

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu2945 F pulseaudio
  CurrentDesktop: MATE
  Date: Fri Jul  8 22:16:46 2016
  InstallationDate: Installed on 2016-04-29 (70 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no 

[Kernel-packages] [Bug 1602282] Re: On __pollwait function issue.

[Joseph Salisbury]

Thank you for providing a patch, and making Ubuntu better.

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

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

Title:
  On __pollwait function issue.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Below is result of perf report:

  ...
 │  mov%r13,%rdi
  ▒
 │  mov0x8(%rdx),%rax   
  ▒
 │  add$0x10,%rsi   
  ▒
 │  movl   $0x0,(%rsi)  
  ▒
   38,10 │  movq   $0x81221860,0x10(%rsi)   
  ▒
 │  mov%rdx,0x8(%rsi)   
  ▒
 │  mov%rax,-0x8(%rsi)  
  ▒
 │  callq  0x810c3490   
  ▒
 │7e:┌─→add$0x8,%rsp
  ▒
4,76 │   │  pop%rbx 
  ▒
 │   │  pop%r12 
  ▒
 │   │  pop%r13 
  ▒
 │   │  pop%rbp 
  ▒
 │   │← retq
  ▒
 │89:│  xor%esi,%esi
  ▒
 │   │  mov$0x24000c0,%edi  
  ▒
 │   │  mov%rdx,-0x20(%rbp) 
  ▒
 │   │  callq  0x81192200   
  ▒
 │   │  test   %rax,%rax
  ▒
 │   │  mov-0x20(%rbp),%rdx 
  ▒
 │   │↓ je d2   
  ▒
 │   │  lea0x10(%rax),%rcx  
  ▒
 │   │  mov%rbx,(%rax)  
  ▒
4,76 │   │  mov%rax,%rbx
  ▒
 │   │  mov%rcx,0x8(%rax)   
  ▒
 │   │  mov%rax,0x10(%rdx)  
  ▒
 │   │  mov0x8(%rax),%rsi   
  ▒
9,52 │   │  lea0x40(%rsi),%rcx  
  ▒
 │   │↑ jmp42   
 

[Kernel-packages] [Bug 1600795] Re: On timerqueue_add function issue.

[Joseph Salisbury]

Thank you for providing a patch, and making Ubuntu better.

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

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

Title:
  On timerqueue_add function issue.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Below is result of perf report:

  timerqueue_add  /proc/kcore   
   
 │  
  ◆
 │  
  ▒
 │  
  ▒
 │Disassembly of section load0: 
  ▒
 │  
  ▒
 │813f3fd0 : 
  ▒
 │  push   %rbp 
  ▒
 │  mov%rsp,%rbp
  ▒
 │  push   %r12 
  ▒
 │  push   %rbx 
  ▒
 │  cmp(%rsi),%rsi  
  ▒
 │  mov%rdi,%r12
  ▒
 │  mov%rsi,%rbx
  ▒
 │↓ jne7e   
  ▒
 │12:   mov%r12,%rdx
  ▒
 │  xor%ecx,%ecx
  ▒
 │↓ jmp30   
  ▒
 │19:   mov0x18(%rax),%rsi  
  ▒
  100,00 │  cmp%rsi,0x18(%rbx)  
  ▒
 │  lea0x10(%rax),%rcx  
  ▒
 │  lea0x8(%rax),%rdx   
  ▒
 │  cmovl  %rcx,%rdx
  ▒
 │  mov%rax,%rcx 
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu3073 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Jul 11 15:23:50 2016
  InstallationDate: Installed on 2016-04-29 (72 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0 

[Kernel-packages] [Bug 1601867] Re: On reschedule_interrupt function issue.

[Joseph Salisbury]

Thank you for providing a patch, and making Ubuntu better.

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

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

Title:
  On reschedule_interrupt function issue.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Below is result of perf report:

  reschedule_interrupt  /proc/kcore 
   
 │  
  ▒
 │  
  ▒
 │  
  ▒
 │Disassembly of section load0: 
  ▒
 │  
  ▒
 │81828ca0 : 
  ▒
   50,00 │  nop 
  ▒
   50,00 │  pushq  $0xff02  
  ▒
 │  cld 
  ▒
 │  add$0xff88,%rsp 
  ▒
 │  mov%r11,0x30(%rsp)  
  ▒
 │  mov%r10,0x38(%rsp)  
  ▒
 │  mov%r9,0x40(%rsp)   
  ▒
 │  mov%r8,0x48(%rsp)   
  ▒
 │  mov%rax,0x50(%rsp)  
  ▒
 │  mov%rcx,0x58(%rsp)  
  ▒
 │  mov%rdx,0x60(%rsp)  
  ▒
 │  mov%rsi,0x68(%rsp)
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu3056 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Jul 11 18:49:42 2016
  InstallationDate: Installed on 2016-04-29 (73 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  

[Kernel-packages] [Bug 1600763] Re: On find_vma function issue.

[Joseph Salisbury]

Thank you for providing a patch, and making Ubuntu better.

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

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

Title:
  On find_vma function issue.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Below is result of perf report:

  find_vma  /proc/kcore 
   
 │  
  ◆
 │  
  ▒
 │  
  ▒
 │Disassembly of section load0: 
  ▒
 │  
  ▒
 │811c49c0 : 
  ▒
   14,29 │  nop 
  ▒
 │  push   %rbp 
  ▒
 │  mov%rsp,%rbp
  ▒
 │  push   %r12 
  ▒
 │  push   %rbx 
  ▒
 │  mov%rdi,%r12
  ▒
 │  mov%rsi,%rbx
  ▒
 │  sub$0x8,%rsp
  ▒
 │  callq  0x811b8b50   
  ▒
 │  test   %rax,%rax
  ▒
 │↓ je 29   
  ▒
 │20:   add$0x8,%rsp
  ▒
 │  pop%rbx 
  ▒
 │  pop%r12 
  ▒
 │  pop%rbp 
  ▒
 │← retq
  ▒
 │29:   mov0x8(%r12),%rdx   
  ▒
 │  test   %rdx,%rdx
  ▒
 │↓ jne48   
  ▒
 │↑ jmp20   
  ▒
 │35:   cmp-0x20(%rdx),%rbx 
  ▒
   14,29 │  lea-0x20(%rdx),%rax 
  ▒
 │↓ jae

[Kernel-packages] [Bug 1602405] Re: On copy_page_to_iter_iovec function issue.

[Joseph Salisbury]

Thank you for providing a patch, and making Ubuntu better.

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

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

Title:
  On copy_page_to_iter_iovec function issue.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Below is result of perf report:

  opy_page_to_iter_iovec  /proc/kcore   
  
 │ Disassembly of section load0:
  ▒
 │  
  ▒
 │ 813ff690 :
  ▒
   75,00 │   mov0x10(%rcx),%rax 
  ▒
 │   cmp%rdx,%rax   
  ▒
 │   cmovbe %rax,%rdx   
  ▒
 │   test   %rdx,%rdx   
  ▒
 │ ↓ je 29a 
  ◆
 │   push   %rbp
  ▒
 │   mov%rsi,%r8
  ▒
 │   mov%rsp,%rbp   
  ▒
 │   push   %r15
  ▒
 │   push   %r14
  ▒
 │   push   %r13
  ▒
 │   push   %r12
  ▒
 │   mov%rdx,%r15   
  ▒
 │   push   %rbx
  ▒
 │   mov%rcx,%rbx   
  ▒
 │   sub$0x20,%rsp  
  ▒
 │   mov0x18(%rcx),%r13 
  ▒
 │   mov0x8(%rcx),%r12  
  ▒
 │   mov0x8(%r13),%r14  
  ▒
 │   mov%r12,%rax   
  ▒
 │   add0x0(%r13),%rax  
  ▒
 │   sub%r12,%r14   
  ▒
 │   cmp%rdx,%r14   
  ▒
 │   mov%rax,%rsi   
  ▒
 │   mov%rax,-0x38(%rbp)
  ▒
 

[Kernel-packages] [Bug 1602409] Re: Ubuntu 16.04 Should package zfs-auto-snapshot

[Joseph Salisbury]

** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => Wishlist

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

** Tags added: xenial

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

Title:
  Ubuntu 16.04 Should package zfs-auto-snapshot

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  ZFS on Linux provide a handy script for automatically creating hourly,
  weekly, and monthly snapshots of ZFS pools. I can't think of a good
  reason for it not being packaged with the official Ubuntu ZFS support.
  The ZoL PPA includes the script and crontabs, so why isn't in the
  official repositories too?

  https://github.com/zfsonlinux/zfs-auto-snapshot

  lsb_release
  -
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

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

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

[Kernel-packages] [Bug 1602371] Re: Touchpad incorrectly detected as PS/2 mouse in 'HP Pavillion 340G1' after Ubuntu 12.04 upgrade to 14.04.

[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.7 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.7-rc7


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

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

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

Title:
  Touchpad incorrectly detected as PS/2 mouse in 'HP Pavillion 340G1'
  after Ubuntu 12.04 upgrade to 14.04.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm currently using Linux 4.2.0-38-generic Kernel.

  
  I adjunct in a .txt the outputs for 
  -dmesg
  -cat /proc/bus/input/devices 

  Regards

  Daniel Ojeda
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  do 3758 F pulseaudio
   /dev/snd/controlC0:  do 3758 F pulseaudio
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-yuanli-precise-amd64-20131009-1
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=93204dde-91fd-41de-b63a-8c49d4903331
  InstallationDate: Installed on 2015-07-13 (365 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20131009-06:05
  MachineType: Hewlett-Packard HP 340 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-38-generic 
root=UUID=8fb79e40-a483-431f-ae1f-b6430988c9fd ro quiet splash i8042.reset 
i8042.nomux i8042.nopnp i8042.noloop vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-38-generic N/A
   linux-backports-modules-4.2.0-38-generic  N/A
   linux-firmware1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 4.2.0-38-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-07-13 (364 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/12/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 21B7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 46.0B
  dmi.chassis.asset.tag: 5CG4471R2Q
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd06/12/2014:svnHewlett-Packard:pnHP340G1:pvr099810167:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 340 G1
  dmi.product.version: 099810167
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1602304] Re: Syslog is full of erros for DRM

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 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.7-rc7


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

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

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

Title:
  Syslog is full of erros for DRM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Many times per second. This needs to stop if we can.
  lsb_release -rd
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-91-generic 3.13.0-91.138
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  geekmonk   2162 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Jul 12 10:33:46 2016
  HibernationDevice: RESUME=UUID=ac68d222-2e0d-4072-be09-23b15e8b5451
  InstallationDate: Installed on 2014-09-23 (657 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0557:2213 ATEN International Co., Ltd CS682 2-Port 
USB 2.0 DVI KVM Switch
   Bus 002 Device 002: ID 0557:8021 ATEN International Co., Ltd CS1764A [CubiQ 
DVI KVMP Switch]
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: HP-Pavilion GG781AA-ABA a6110n
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic 
root=UUID=fc69fd4c-0e1f-422f-827f-2bcd9a13fde6 ro drm.debug=0xe plymouth:debug
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-91-generic N/A
   linux-backports-modules-3.13.0-91-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.13
  dmi.board.name: NARRA2
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 2.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.13:bd10/29/2007:svnHP-Pavilion:pnGG781AA-ABAa6110n:pvr:rvnASUSTekComputerINC.:rnNARRA2:rvr2.00:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: GG781AA-ABA a6110n
  dmi.sys.vendor: HP-Pavilion

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

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

[Kernel-packages] [Bug 1598457] Re: ubuntu does not power off when the laptop is plugged in

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 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.7-rc7


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

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

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

Title:
  ubuntu does not  power off when the laptop is plugged in

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever my laptop (HP pavilion 15) is plugged in and when I try to
  shutdown or hibernate, the system stops the process somewhere in the
  middle and stays in the plymouth logo. Hard drive is stopped, fan is
  in working, power and wifi indicator light are glowing. Suspend and
  resume work both without any problems. When my laptop is not plugged
  in, the system is shutdown or hibernate correctly.

  OS: All ubuntu OS and its derivatives (ubuntu 14.04,...,16.04, Linux
  mint, Elementary OS)

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

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

[Kernel-packages] [Bug 1602299] Re: bcache is unstable on ppc64el

[Joseph Salisbury]

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

** Tags added: kernel-da-key

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

Title:
  bcache is unstable on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Stopping and unregistering bcache caches and backing devices results
  in losing the bcache superblock on devices rendering bcached devices
  corrupt or broken.

  1. Ubuntu 4.4.0-28.47-generic 4.4.13
  2. attaching lspci log
  3. 

  Description:Ubuntu 16.04 LTS
  Release:16.04

  4. # apt-cache policy linux-image
  linux-image:
Installed: (none)
Candidate: (none)
Version table:
  root@rharper-vm1:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: (none)
Candidate: 4.4.0.28.30
Version table:
   4.4.0.28.30 500
  500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main ppc64el 
Packages
  500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el 
Packages
   4.4.0.21.22 500
  500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages

  5. After creating bcache devices, upon reboot they continue to remain as 
bcache devices for use
  6. Sometimes after reboot either the cache device, or the backing device 
loses the bcache-super-block rendering them useless to the bcache module (it 
fails to detect them).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 21:30 seq
   crw-rw 1 root audio 116, 33 Jul 11 21:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Tue Jul 12 14:20:24 2016
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 OFfb vga
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-28-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  ProcLoadAvg: 6.28 4.78 4.12 1/133 4838
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1306 00:11:541 0 EOF
   2: FLOCK  ADVISORY  WRITE 918 00:11:521 0 EOF
   3: POSIX  ADVISORY  WRITE 875 00:11:507 0 EOF
   4: POSIX  ADVISORY  WRITE 870 00:11:123 0 EOF
   5: POSIX  ADVISORY  WRITE 682 00:11:358 0 EOF
  ProcSwaps: Filename   TypeSizeUsed
Priority
  ProcVersion: Linux version 4.4.0-28-generic (buildd@bos01-ppc64el-018) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #47-Ubuntu SMP Fri Jun 
24 10:09:20 UTC 2016
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.684 GHz (cpu 0)
   max: 3.684 GHz (cpu 0)
   avg: 3.684 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

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

[Kernel-packages] [Bug 1602827] Re: NFS server "shutting down socket" during large file copies Ubunutu 14.04.4 LTS

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 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.7-rc7


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

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

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

Title:
  NFS server "shutting down socket" during large file copies Ubunutu
  14.04.4 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is very similar to bug 585657: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/585657
  Difference is my server doesn't freeze, it closes the socket. System 
integrity is still responsive.

  I'm running NFS version 4 on Ubuntu 14.04.4 LTS and during large rsync
  file copies (200MB+) they die midway. This is killing my zimbra email
  backups :(. I haven't had the system freeze during this scenario but
  what ends up happening is the copy fails on the client side and then
  my NFS server shuts the socket down due to excessive failures. Smaller
  file copies work perfectly fine.

  Here are the client/server logs.

  #Client
  Jul  9 01:00:39 mailserv01 kernel: [591473.216168] nfs: server NFS-Backup01 
not responding, still trying
  Jul  9 01:00:39 mailserv01 kernel: [591473.216174] nfs: server NFS-Backup01 
not responding, still trying
  Jul  9 01:00:39 mailserv01 kernel: [591473.218841] nfs: server NFS-Backup01 OK
  Jul  9 01:00:39 mailserv01 kernel: [591473.219159] nfs: server NFS-Backup01 OK
  Jul  9 01:01:14 mailserv01 kernel: [591508.710863] nfs: server NFS-Backup01 
not responding, still trying
  Jul  9 01:08:16 mailserv01 kernel: [591929.870358] nfs: server NFS-Backup01 OK
  Jul  9 01:08:44 mailserv01 kernel: [591958.514953] nfs: server NFS-Backup01 
not responding, still trying
  Jul  9 01:10:23 mailserv01 kernel: [592056.840273] nfs: server NFS-Backup01 OK
  Jul  9 01:11:19 mailserv01 kernel: [592113.298900] nfs: server NFS-Backup01 
not responding, still trying
  Jul  9 01:13:07 mailserv01 kernel: [592221.275966] nfs: server NFS-Backup01 OK
  Jul  9 01:15:22 mailserv01 kernel: [592355.580401] nfs: server NFS-Backup01 
not responding, still trying
  Jul  9 01:15:22 mailserv01 kernel: [592355.615649] nfs: server NFS-Backup01 OK
  Jul  9 01:16:03 mailserv01 kernel: [592397.459848] nfs: server NFS-Backup01 
not responding, still trying
  Jul  9 01:16:08 mailserv01 kernel: [592401.663381] nfs: server NFS-Backup01 OK
  Jul  9 01:17:06 mailserv01 kernel: [592460.381059] nfs: server NFS-Backup01 
not responding, still trying

  #NFS Server
  Jul  9 01:01:51 NFS-Backup01 kernel: [130980.762798] RPC request reserved 156 
but used 176
  Jul  9 01:08:28 NFS-Backup01 kernel: [131377.839675] RPC request reserved 156 
but used 176
  Jul  9 01:08:46 NFS-Backup01 kernel: [131395.943517] rpc-srv/tcp: nfsd: got 
error -32 when sending 136 bytes - shutting down socket
  Jul  9 01:10:17 NFS-Backup01 kernel: [131486.962508] RPC request reserved 156 
but used 176
  Jul  9 01:10:22 NFS-Backup01 kernel: [131492.447565] RPC request reserved 156 
but used 176
  Jul  9 01:10:27 NFS-Backup01 kernel: [131496.837561] rpc-srv/tcp: nfsd: got 
error -32 when sending 136 bytes - shutting down socket
  Jul  9 01:10:54 NFS-Backup01 kernel: [131524.423501] RPC request reserved 156 
but used 176
  Jul  9 01:15:31 NFS-Backup01 kernel: [131801.603553] rpc-srv/tcp: nfsd: got 
error -32 when sending 136 bytes - shutting down socket
  Jul  9 01:16:55 NFS-Backup01 kernel: [131885.232973] rpc-srv/tcp: nfsd: got 
error -32 when sending 136 bytes - shutting down socket

  #Client fstab
  NFS-Backup01:/mnt/backup /mnt/backup nfs 
rsize=8192,wsize=8192,nfsvers=4,hard,timeo=14,intr

  #NFS Server fstab
  /mnt/backup/mnt/backup  nonebind  0  0

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

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

[Kernel-packages] [Bug 1603578] Re: unable to enumerate USB device

[Joseph Salisbury]

Thanks for the update.  I'll mark this bug as invalid per your comment.
If the bug does happen again, just change the status back to confirmed.

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

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

Title:
  unable to enumerate USB device

Status in linux package in Ubuntu:
  Invalid

Bug description:
  ubuntu 16.04 LTS

  When I start the operating system, I get the messages:
  usb 5-1: device descriptor read/64, error -71
  usb 5-1: device not accepting address 4, error -71
  usb 5-1: device not accepting address 5, error -71
  usb usb5-port1: unable to enumerate USB device

  My external Seagate USB harddisk does not work.

  This problem started after the latest software update.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 16 08:30:51 2016
  HotplugNewDevices: /dev/sdd1 /dev/sdd
  HotplugNewMounts: /dev/sdd1 /media/colin/Seagate\040Expansion\040Drive 
fuseblk 
rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
  InstallationDate: Installed on 2016-06-11 (34 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. P55-UD3
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=8c0c09d5-9860-4049-a4db-3e06124c9601 ro quiet splash
  SourcePackage: udisks2
  Symptom: storage
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: P55-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd06/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1603397] Re: booting new 3.19.0-65, monitor stays in power save

[Joseph Salisbury]

It might be best to upgrade to 16.04(Xenial) since Vivid is now EOL.

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1436940] Re: Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041] is not supported

[Kees Cook]

Adding ath10k/QCA6174/hw2.1/board-pci-168c:0041:17aa:3545.bin (from the
working board.bin in this thread) seems to fix it, though:

e6adc90ecaf55edc656990c6c50193ac  board-pci-168c:0041:17aa:3545.bin

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

Title:
  Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041]
  is not supported

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in linux source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Confirmed

Bug description:
  The firmware for this card isn't included with Ubuntu.  The firmware
  provided in /lib/firmware/ath10k/QCA6174 in Ubuntu 16.04 crashes when
  used with this card.  This included firmware is likely for the QCA6174
  instead of this card, the QCA6164.

  Yes, you read that right: the files for the QCA6164 need to be a
  folder called QCA6174 in order for the card to work.  Running
  "modprobe ath10k_pci" shows that the ath10k_pci module looks for
  firmware in a folder called QCA6174, but not in any folder called
  QCA6164.

  It seems that before this issue can be resolved, the ath10k_pci module
  must be changed so that it recognizes firmware for both the QCA6164
  and QCA6174, in separate folders.

  ---

  HOW TO GET THIS CARD TO WORK:

  1) Use a kernel that supports this card

  According to WikiDevi, support for this card was added in kernel 4.3.
  If you're running Ubuntu 16.04 LTS or above, your kernel is fine; skip
  to the next step.  If you're running Ubuntu 15.10 or below, see
  https://wiki.ubuntu.com/Kernel/MainlineBuilds for info on installing a
  newer kernel.  Alternatively, you can use backports.  This is a lot
  more work, but if you really need to keep using an older kernel for
  some reason, there are some guides to installing backports in the
  comments below.

  2) Get rid of the firmware folder for this card that's included with
  Ubuntu:

  sudo rm -r /lib/firmware/ath10k/QCA6174/

  3) Download the latest firmware:

  wget https://github.com/kvalo/ath10k-firmware/archive/master.zip

  4) Unzip the downloaded file.  Inside the ath10k-firmware-master
  folder is a folder named QCA6174.  Copy the QCA6174 folder to
  /lib/firmware/ath10k:

  unzip master.zip
  sudo cp -r ath10k-firmware-master/QCA6174/ /lib/firmware/ath10k/

  5) Rename two of the firmware files like so:

  cd /lib/firmware/ath10k/QCA6174/hw2.1/
  sudo mv firmware-5.bin_SW_RM.1.1.1-00157-QCARMSWPZ-1 firmware-5.bin
  cd /lib/firmware/ath10k/QCA6174/hw3.0/
  sudo mv firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 firmware-4.bin

  6) Reboot your computer.  Run "lshw -C network" to see if your card is
  recognized.  You can delete the files you downloaded earlier:

  cd ~
  rm master.zip
  rm -r ath10k-firmware-master/

  I've verified that this works with Ubuntu 16.04 LTS (with kernel
  4.4.0-21-generic); let me know if it doesn't work for you in the
  comments below.

  ---

  Miles Krell

  Last updated May 23, 2016

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

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

[Kernel-packages] [Bug 1603397] Re: booting new 3.19.0-65, monitor stays in power save

[Joseph Salisbury]

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

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1603328] Re: Application perf fail to start.

[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

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

Title:
  Application perf fail to start.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When run on terminal below error occur:

  asu@asu-ALABAMA:~$ sudo perf record -e cycles -ag
  [sudo] password for asu: 
  /usr/lib/linux-tools/4.4.0-28-generic/perf: error while loading shared 
libraries: libbfd-2.26-system.so: cannot open shared object file: No such file 
or directory

  Because binutils, binutils-dev packages was updated and perf must be
  recompiled again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu2875 F pulseaudio
  CurrentDesktop: MATE
  Date: Fri Jul 15 10:11:54 2016
  InstallationDate: Installed on 2016-04-29 (76 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

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

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the 3.19.0-66.74~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
  -- swm properties --
  kernel-stable-master-bug: 1604153
+ kernel-stable-phase-changed:Monday, 18. July 2016 22:02 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 3.19.0-66.74~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
  -- swm properties --
+ derivative-trackers-created: true
  kernel-stable-master-bug: 1604153
- kernel-stable-phase-changed:Monday, 18. July 2016 22:02 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-lts-vivid: 3.19.0-66.74~14.04.1 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
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-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.19.0-66.74~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
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1604153
  phase: Packaging

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

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

[Kernel-packages] [Bug 1603283] Re: REGRESSION: resume fails on recent 4.4.0-31, works on -28

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

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

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

** Tags added: kernel-da-key

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

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

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

** Tags added: needs-bisect

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

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

[Max Bowsher]

Acting on Cyril's suggestion above, I downloaded the Debian 8.0-2 source
package, rebuilt it locally, and installed it. It seems to have fixed
the problem for me. So perhaps the problem really is in the Ubuntu
delta?

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

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

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

[Kernel-packages] [Bug 1603288] Re: package linux-image-4.4.0-31-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before installi

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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


** Tags added: kernel-da-key

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

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

Title:
  package linux-image-4.4.0-31-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-31-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Install attempted by Ubuntu Mate included Update Manager along with
  Grub2 update. The Grub2 update failed and according to the pop-up
  announcement by the Update Manager it also caused the  linux-
  image-4.4.0-31-generic installation failure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  2162 F pulseaudio
   /dev/snd/controlC0:  david  2162 F pulseaudio
  Date: Thu Jul 14 20:27:23 2016
  DuplicateSignature:
   package:linux-image-4.4.0-31-generic:(not installed)
   Unpacking linux-image-4.4.0-31-generic (4.4.0-31.50) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-31-generic_4.4.0-31.50_amd64.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=cf771e35-9679-4425-89bc-cdc68ab786e6
  InstallationDate: Installed on 2016-05-23 (53 days ago)
  InstallationMedia: It
  MachineType: GizmoSphere Gizmo2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=19bf53ad-e512-4435-bbde-ae92ffe72f2a ro elevator=noop quiet splash
  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-36ubuntu3.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-31-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: SageBios_Gizmo2-121
  dmi.chassis.type: 3
  dmi.chassis.vendor: GizmoSphere
  dmi.modalias: 
dmi:bvncoreboot:bvrSageBios_Gizmo2-121:bd04/10/2014:svnGizmoSphere:pnGizmo2:pvr1.0:cvnGizmoSphere:ct3:cvr:
  dmi.product.name: Gizmo2
  dmi.product.version: 1.0
  dmi.sys.vendor: GizmoSphere

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

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

[Kernel-packages] [Bug 1436940] Re: Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041] is not supported

[Kees Cook]

Hm, not fixed for me. still seeing firmware crashes. :(


** Changed in: linux-firmware (Ubuntu Xenial)
   Status: Fix Released => Confirmed

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

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

Title:
  Qualcomm Atheros QCA6164 802.11ac Wireless Network Adapter [168c:0041]
  is not supported

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in linux source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux-firmware source package in Xenial:
  Confirmed

Bug description:
  The firmware for this card isn't included with Ubuntu.  The firmware
  provided in /lib/firmware/ath10k/QCA6174 in Ubuntu 16.04 crashes when
  used with this card.  This included firmware is likely for the QCA6174
  instead of this card, the QCA6164.

  Yes, you read that right: the files for the QCA6164 need to be a
  folder called QCA6174 in order for the card to work.  Running
  "modprobe ath10k_pci" shows that the ath10k_pci module looks for
  firmware in a folder called QCA6174, but not in any folder called
  QCA6164.

  It seems that before this issue can be resolved, the ath10k_pci module
  must be changed so that it recognizes firmware for both the QCA6164
  and QCA6174, in separate folders.

  ---

  HOW TO GET THIS CARD TO WORK:

  1) Use a kernel that supports this card

  According to WikiDevi, support for this card was added in kernel 4.3.
  If you're running Ubuntu 16.04 LTS or above, your kernel is fine; skip
  to the next step.  If you're running Ubuntu 15.10 or below, see
  https://wiki.ubuntu.com/Kernel/MainlineBuilds for info on installing a
  newer kernel.  Alternatively, you can use backports.  This is a lot
  more work, but if you really need to keep using an older kernel for
  some reason, there are some guides to installing backports in the
  comments below.

  2) Get rid of the firmware folder for this card that's included with
  Ubuntu:

  sudo rm -r /lib/firmware/ath10k/QCA6174/

  3) Download the latest firmware:

  wget https://github.com/kvalo/ath10k-firmware/archive/master.zip

  4) Unzip the downloaded file.  Inside the ath10k-firmware-master
  folder is a folder named QCA6174.  Copy the QCA6174 folder to
  /lib/firmware/ath10k:

  unzip master.zip
  sudo cp -r ath10k-firmware-master/QCA6174/ /lib/firmware/ath10k/

  5) Rename two of the firmware files like so:

  cd /lib/firmware/ath10k/QCA6174/hw2.1/
  sudo mv firmware-5.bin_SW_RM.1.1.1-00157-QCARMSWPZ-1 firmware-5.bin
  cd /lib/firmware/ath10k/QCA6174/hw3.0/
  sudo mv firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 firmware-4.bin

  6) Reboot your computer.  Run "lshw -C network" to see if your card is
  recognized.  You can delete the files you downloaded earlier:

  cd ~
  rm master.zip
  rm -r ath10k-firmware-master/

  I've verified that this works with Ubuntu 16.04 LTS (with kernel
  4.4.0-21-generic); let me know if it doesn't work for you in the
  comments below.

  ---

  Miles Krell

  Last updated May 23, 2016

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

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

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[Joseph Salisbury]

Do you have a machine that could be used to test some kernels?  If so,
we can perform a kernel bisect to identify the commit that caused the
regression.

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

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

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

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

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

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

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[Joseph Salisbury]

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

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

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

Re: [Kernel-packages] [Bug 1603578] Re: unable to enumerate USB device

[Colin Middleton]

On 19/07/16 06:49, Joseph Salisbury wrote:
> Does booting back into the prior kernel make the bug go away?
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => High
>
> ** Tags added: kernel-da-key
>
The bug has gone away.  It was there a couple of times and then it did
not reappear.

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

Title:
  unable to enumerate USB device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04 LTS

  When I start the operating system, I get the messages:
  usb 5-1: device descriptor read/64, error -71
  usb 5-1: device not accepting address 4, error -71
  usb 5-1: device not accepting address 5, error -71
  usb usb5-port1: unable to enumerate USB device

  My external Seagate USB harddisk does not work.

  This problem started after the latest software update.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 16 08:30:51 2016
  HotplugNewDevices: /dev/sdd1 /dev/sdd
  HotplugNewMounts: /dev/sdd1 /media/colin/Seagate\040Expansion\040Drive 
fuseblk 
rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
  InstallationDate: Installed on 2016-06-11 (34 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. P55-UD3
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=8c0c09d5-9860-4049-a4db-3e06124c9601 ro quiet splash
  SourcePackage: udisks2
  Symptom: storage
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: P55-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd06/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1603483] Re: [Xenial] Include Huawei PCIe SSD hio kernel driver

[Kamal Mostafa]

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

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

Title:
  [Xenial] Include Huawei PCIe SSD hio kernel driver

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==
  Huawei servers, including Huawei PCIe SSD's require the hio driver which is 
currently not included in our kernels.  We would like to carry this driver in 
our kernels for Xenial and newer in order to support platforms with these 
drives.

  == Source ==
  
http://support.huawei.com/enterprisesearch/ebgSearch#sp.keyword=HUAWEI%20ES3000%20V2%20Driver%20SRC

  == Testing ==
  TBD

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

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

[Kernel-packages] [Bug 1603449] Re: [LTCTest][Opal][OP820] Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1] while executing Froze PE Error injection

[Tim Gardner]

Guo Wen Shan - how about if you take a stab at the backports for these 2
patches, 'cause I don't think they make sense for a 4.4 kernel.

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

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

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

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

Title:
  [LTCTest][Opal][OP820] Machine crashed with Oops: Kernel access of bad
  area, sig: 11 [#1] while executing Froze PE Error injection

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  In Progress

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2016-07-13 
01:28:56 ==
  ---Problem Description---
  Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1]
   
  ---uname output---
  Linux ltc-garri2 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  root@ltc-garri2:~# lspci
  :00:00.0 PCI bridge: IBM Device 03dc
  :01:00.0 Infiniband controller: Mellanox Technologies MT27600 [Connect-IB]
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0002:00:00.0 PCI bridge: IBM Device 03dc
  0002:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0003:00:00.0 PCI bridge: IBM Device 03dc
  0004:00:00.0 PCI bridge: IBM Device 03dc
  0005:00:00.0 PCI bridge: IBM Device 03dc
  0005:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:02.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:03.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:04.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller (rev 02)
  0005:04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 
x2 4-port SATA 6 Gb/s Controller (rev 11)
  0005:05:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge 
(rev 03)
  0005:06:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED 
Graphics Family (rev 30)
  0005:07:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0005:07:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0006:00:00.0 PCI bridge: IBM Device 03dc
  0006:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0007:00:00.0 PCI bridge: IBM Device 03dc
  0008:00:00.0 Bridge: IBM Device 04ea
  0008:00:00.1 Bridge: IBM Device 04ea
  0008:00:01.0 Bridge: IBM Device 04ea
  0008:00:01.1 Bridge: IBM Device 04ea
  0009:00:00.0 Bridge: IBM Device 04ea
  0009:00:00.1 Bridge: IBM Device 04ea
  0009:00:01.0 Bridge: IBM Device 04ea
  0009:00:01.1 Bridge: IBM Device 04ea
   

   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Install a P8 Open Power 8335-GTB Hardware with Ubuntu 16.04.1.
  Then execute the Frozen PE error injection tests as shown below:

  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0

  
  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0
  root@ltc-garri2:~# echo 0:0:4:0:0 > 
/sys/kernel/debug/powerpc/PCI0004/err_injct && lspci -ns 0004:00:00.0; echo $?
  0004:00:00.0 0604: 1014:03dc
  0

  Immediately the kernel crashes with a Oops Message.
   
  Contact Information = pavsu...@in.ibm.com 
   
  Stack trace output:
   [  289.297946] Call Trace:
  [  289.297969] [c00feeb8b9e0] [c0083c78] pnv_eeh_reset+0x58/0x170 
(unreliable)
  [  289.298042] [c00feeb8ba60] [c0038250] eeh_reset_pe+0xb0/0x1c0
  [  289.298105] [c00feeb8bb00] [c0af444c] 
eeh_reset_device+0xd8/0x228
  [  289.298165] [c00feeb8bba0] [c003c520] 
eeh_handle_normal_event+0x390/0x440
  [  289.298234] [c00feeb8bc20] [c003c9c4] 
eeh_handle_event+0x184/0x370
  [  289.298304] [c00feeb8bcd0] [c003cd88] 
eeh_event_handler+0x1d8/0x1e0
  [  289.298374] [c00feeb8bd80] [c00e6420] kthread+0x110/0x130
  [  289.298434] [c00feeb8be30] [c0009538] 
ret_from_kernel_thread+0x5c/0xa4
  [  289.298501] Instruction dump:
  [  289.298531] 6000 813f ebdf0010 792affe3 408200d4 e95e0250 

[Kernel-packages] [Bug 1603564] Re: USB unplug crashes system - Assuming host is dying, halting host

[Guru Prasad]

First off, sorry if this comment is redundant.

I cannot say for sure whether the issue happened after an update. I run
apt-get upgrade very often and thus cannot peg it down to an update. I
have definitely not upgraded (dist-upgrade) my Ubuntu version.

I will give the latest kernel a shot, but, I have no way to 100%
reproduce this bug every time. This may lead to false negatives.

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

Title:
  USB unplug crashes system - Assuming host is dying, halting host

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, when I unplug my Android phone (connected over USB), my machine 
crashes.
  At first, I presumed the entire machine had halted since the keyboard and 
mouse stopped working.
  However, I'm still able to SSH in although the screen is completely 
non-responsive. Pressing the power button on the CPU seems to bring up a window 
with Ubuntu's power options.

  My Ubuntu version:
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Codename: trusty

  Kernel version:
  Linux nixentor 3.13.0-91-generic #138-Ubuntu SMP Fri Jun 24 17:00:34 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  I see the following output on dmesg:
  [15563.650717] [ cut here ]
  [15563.650730] WARNING: CPU: 7 PID: 0 at 
/build/linux-3r7mVb/linux-3.13.0/drivers/usb/host/xhci-ring.c:1590 
handle_cmd_completion+0xe56/0xe60()
  [15563.650732] Modules linked in: qcserial usb_wwan usbserial ip6table_filter 
ip6_tables iptable_filter ip_tables x_tables cachefiles cfg80211 rfcomm bnep 
nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_hdmi btusb 
bluetooth usb_storage mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd uvcvideo videobuf2_vmalloc videobuf2_memops 
joydev videobuf2_core snd_hda_codec_realtek videodev snd_usb_audio 
snd_usbmidi_lib 8812au(OX) snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_hda_intel snd_hda_codec snd_seq serio_raw snd_hwdep radeon snd_pcm mei_me 
snd_page_alloc mei snd_seq_device snd_timer snd ttm drm_kms_helper soundcore 
drm parport_pc i2c_algo_bit ppdev lp wmi parport video intel_smartconnect 
shpchp acpi_pad mac_hid hid_generic usbhid hid e1000e ahci psmouse ptp libahci 
pps_core
  [15563.650804] CPU: 7 PID: 0 Comm: swapper/7 Tainted: G   OX 
3.13.0-91-generic #138-Ubuntu
  [15563.650807] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Z97 Extreme4, BIOS P1.30 05/23/2014
  [15563.650809]   88041edc3d90 81729906 

  [15563.650813]  0009 88041edc3dc8 8106987d 
880404062d60
  [15563.650817]  8804040606b0 0010 0004040606b0 
8804041a
  [15563.650822] Call Trace:
  [15563.650824][] dump_stack+0x64/0x82
  [15563.650836]  [] warn_slowpath_common+0x7d/0xa0
  [15563.650840]  [] warn_slowpath_null+0x1a/0x20
  [15563.650845]  [] handle_cmd_completion+0xe56/0xe60
  [15563.650852]  [] ? check_preempt_curr+0x75/0xa0
  [15563.650857]  [] xhci_irq+0x33b/0xa50
  [15563.650861]  [] ? sched_clock_cpu+0xb5/0x100
  [15563.650865]  [] xhci_msi_irq+0x11/0x20
  [15563.650870]  [] handle_irq_event_percpu+0x4e/0x220
  [15563.650874]  [] handle_irq_event+0x3d/0x60
  [15563.650878]  [] handle_edge_irq+0x77/0x130
  [15563.650886]  [] handle_irq+0x1e/0x30
  [15563.650893]  [] do_IRQ+0x4d/0xc0
  [15563.650898]  [] common_interrupt+0x6d/0x6d
  [15563.650900][] ? cpuidle_enter_state+0x52/0xc0
  [15563.650910]  [] ? cpuidle_enter_state+0x48/0xc0
  [15563.650915]  [] cpuidle_idle_call+0xdc/0x220
  [15563.650921]  [] arch_cpu_idle+0xe/0x30
  [15563.650924]  [] cpu_startup_entry+0xc1/0x2b0
  [15563.650931]  [] start_secondary+0x21d/0x2d0
  [15563.650934] ---[ end trace d9b5447d0ddb440a ]---
  [15565.486066] xhci_hcd :00:14.0: xHCI host not responding to stop 
endpoint command.
  [15565.486075] xhci_hcd :00:14.0: Assuming host is dying, halting host.
  [15565.486120] xhci_hcd :00:14.0: HC died; cleaning up
  [15568.853140] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [15568.853149] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15569.057055] usb 3-14: device not accepting address 92, error -108
  [15574.055575] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15574.055587] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15579.054167] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15579.054176] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15584.052706] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15584.052715] xhci_hcd :00:14.0: Abort the command ring, 

[Kernel-packages] [Bug 1603564] Re: USB unplug crashes system - Assuming host is dying, halting host

[Guru Prasad]

I don't think I can run apport-collect. So far, I've had it happen about
3-4 times over 30 hours of uptime. If it does happen again, _and_ I'm
able to start a vnc session, _and_ said vnc session works, I will
definitely update this bug report with the logs.

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

Title:
  USB unplug crashes system - Assuming host is dying, halting host

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, when I unplug my Android phone (connected over USB), my machine 
crashes.
  At first, I presumed the entire machine had halted since the keyboard and 
mouse stopped working.
  However, I'm still able to SSH in although the screen is completely 
non-responsive. Pressing the power button on the CPU seems to bring up a window 
with Ubuntu's power options.

  My Ubuntu version:
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Codename: trusty

  Kernel version:
  Linux nixentor 3.13.0-91-generic #138-Ubuntu SMP Fri Jun 24 17:00:34 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  I see the following output on dmesg:
  [15563.650717] [ cut here ]
  [15563.650730] WARNING: CPU: 7 PID: 0 at 
/build/linux-3r7mVb/linux-3.13.0/drivers/usb/host/xhci-ring.c:1590 
handle_cmd_completion+0xe56/0xe60()
  [15563.650732] Modules linked in: qcserial usb_wwan usbserial ip6table_filter 
ip6_tables iptable_filter ip_tables x_tables cachefiles cfg80211 rfcomm bnep 
nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_hdmi btusb 
bluetooth usb_storage mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd uvcvideo videobuf2_vmalloc videobuf2_memops 
joydev videobuf2_core snd_hda_codec_realtek videodev snd_usb_audio 
snd_usbmidi_lib 8812au(OX) snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_hda_intel snd_hda_codec snd_seq serio_raw snd_hwdep radeon snd_pcm mei_me 
snd_page_alloc mei snd_seq_device snd_timer snd ttm drm_kms_helper soundcore 
drm parport_pc i2c_algo_bit ppdev lp wmi parport video intel_smartconnect 
shpchp acpi_pad mac_hid hid_generic usbhid hid e1000e ahci psmouse ptp libahci 
pps_core
  [15563.650804] CPU: 7 PID: 0 Comm: swapper/7 Tainted: G   OX 
3.13.0-91-generic #138-Ubuntu
  [15563.650807] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Z97 Extreme4, BIOS P1.30 05/23/2014
  [15563.650809]   88041edc3d90 81729906 

  [15563.650813]  0009 88041edc3dc8 8106987d 
880404062d60
  [15563.650817]  8804040606b0 0010 0004040606b0 
8804041a
  [15563.650822] Call Trace:
  [15563.650824][] dump_stack+0x64/0x82
  [15563.650836]  [] warn_slowpath_common+0x7d/0xa0
  [15563.650840]  [] warn_slowpath_null+0x1a/0x20
  [15563.650845]  [] handle_cmd_completion+0xe56/0xe60
  [15563.650852]  [] ? check_preempt_curr+0x75/0xa0
  [15563.650857]  [] xhci_irq+0x33b/0xa50
  [15563.650861]  [] ? sched_clock_cpu+0xb5/0x100
  [15563.650865]  [] xhci_msi_irq+0x11/0x20
  [15563.650870]  [] handle_irq_event_percpu+0x4e/0x220
  [15563.650874]  [] handle_irq_event+0x3d/0x60
  [15563.650878]  [] handle_edge_irq+0x77/0x130
  [15563.650886]  [] handle_irq+0x1e/0x30
  [15563.650893]  [] do_IRQ+0x4d/0xc0
  [15563.650898]  [] common_interrupt+0x6d/0x6d
  [15563.650900][] ? cpuidle_enter_state+0x52/0xc0
  [15563.650910]  [] ? cpuidle_enter_state+0x48/0xc0
  [15563.650915]  [] cpuidle_idle_call+0xdc/0x220
  [15563.650921]  [] arch_cpu_idle+0xe/0x30
  [15563.650924]  [] cpu_startup_entry+0xc1/0x2b0
  [15563.650931]  [] start_secondary+0x21d/0x2d0
  [15563.650934] ---[ end trace d9b5447d0ddb440a ]---
  [15565.486066] xhci_hcd :00:14.0: xHCI host not responding to stop 
endpoint command.
  [15565.486075] xhci_hcd :00:14.0: Assuming host is dying, halting host.
  [15565.486120] xhci_hcd :00:14.0: HC died; cleaning up
  [15568.853140] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [15568.853149] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15569.057055] usb 3-14: device not accepting address 92, error -108
  [15574.055575] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15574.055587] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15579.054167] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15579.054176] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15584.052706] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15584.052715] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15584.052841] usb 3-3: USB disconnect, device number 2
  [15584.052854] usb 3-3.2: USB disconnect, 

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

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the 3.13.0-93.140~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
  -- swm properties --
  kernel-stable-master-bug: 1604134
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Monday, 18. July 2016 21:06 UTC

** Description changed:

  This bug is for tracking the 3.13.0-93.140~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
  -- swm properties --
+ derivative-trackers-created: true
  kernel-stable-master-bug: 1604134
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Monday, 18. July 2016 21:06 UTC
+ phase: Packaging

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

Title:
  linux-lts-trusty: 3.13.0-93.140~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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
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:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-93.140~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
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1604134
  phase: Packaging

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

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

[Kernel-packages] [Bug 1604153] Re: linux: 3.19.0-66.74 -proposed tracker

[Brad Figg]

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

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

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

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

** Description changed:

  This bug is for tracking the 3.19.0-66.74 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-phase:Packaging
+ kernel-stable-phase-changed:Monday, 18. July 2016 21:03 UTC

** Description changed:

  This bug is for tracking the 3.19.0-66.74 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-phase:Packaging
  kernel-stable-phase-changed:Monday, 18. July 2016 21:03 UTC
+ 
+ -- swm properties --
+ derivative-trackers-created: true
+ phase: Packaging

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

Title:
  linux: 3.19.0-66.74 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  New

Bug description:
  This bug is for tracking the 3.19.0-66.74 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-phase:Packaging
  kernel-stable-phase-changed:Monday, 18. July 2016 21:03 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1604099] Re: linux: 3.2.0-107.148 -proposed tracker

[Brad Figg]

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

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

** Description changed:

  This bug is for tracking the 3.2.0-107.148 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-phase:Packaging
- kernel-stable-phase-changed:Monday, 18. July 2016 18:01 UTC
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Monday, 18. July 2016 21:01 UTC

** Description changed:

  This bug is for tracking the 3.2.0-107.148 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
  
  -- swm properties --
  derivative-trackers-created: true
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 18. July 2016 21:01 UTC
+ phase: Uploaded

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

Title:
  linux: 3.2.0-107.148 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-lbm series:
  Confirmed
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 verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.2.0-107.148 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

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1604159] [NEW] linux-lts-vivid: 3.19.0-66.74~14.04.1 -proposed tracker

[Brad Figg]

Public bug reported:

This bug is for tracking the 3.19.0-66.74~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
-- swm properties --
kernel-stable-master-bug: 1604153

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

** 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: Undecided => Medium

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

[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

[John Mazzie]

This version is working correctly.

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

Title:
  Broadwell ECRC Support missing in Ubuntu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Here is the problem statement from the Dell team:

  When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel
  Quick Assist Card, the memory location that corresponds to ECRC is set
  to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot.
  This causes the card to not function unless we implement the following
  workaround using setpci.

  “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for
  the Intel Quick Assit Card.

  We’ve verified the memory location is correct when booting to other
  OSes, such as RHEL 7.2 and Windows Server 2012 R2.

  If there is any information you can give as to why this may be
  occurring in Ubuntu or where we may start to debug when the memory is
  changed, we would appreciate it.

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

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

[Kernel-packages] [Bug 1603483] Re: [Xenial] Include Huawei PCIe SSD hio kernel driver

[Kamal Mostafa]

Attached, @jjo reports positive bcache smoke test results with the lts-x
'hio' test kernel.

** Attachment added: "hio-bcache-test-result-jjo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603483/+attachment/4703082/+files/hio-bcache-test-result-jjo.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/1603483

Title:
  [Xenial] Include Huawei PCIe SSD hio kernel driver

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

Bug description:
  == SRU Justification ==
  Huawei servers, including Huawei PCIe SSD's require the hio driver which is 
currently not included in our kernels.  We would like to carry this driver in 
our kernels for Xenial and newer in order to support platforms with these 
drives.

  == Source ==
  
http://support.huawei.com/enterprisesearch/ebgSearch#sp.keyword=HUAWEI%20ES3000%20V2%20Driver%20SRC

  == Testing ==
  TBD

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

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

[Kernel-packages] [Bug 1603880] Re: On preempt_enable preemt_disable and others issue

[Joseph Salisbury]

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

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

Title:
  On preempt_enable preemt_disable and others  issue

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Function preept_enable, preempt_disable and others spmake spann.
  Original these func is on loop but on most cases working sycronised with 
current cpu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu3075 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Jul 18 10:17:51 2016
  InstallationDate: Installed on 2016-04-29 (79 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

[Kernel-packages] [Bug 1603564] Re: USB unplug crashes system - Assuming host is dying, halting host

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 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.7-rc7


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

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

Title:
  USB unplug crashes system - Assuming host is dying, halting host

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, when I unplug my Android phone (connected over USB), my machine 
crashes.
  At first, I presumed the entire machine had halted since the keyboard and 
mouse stopped working.
  However, I'm still able to SSH in although the screen is completely 
non-responsive. Pressing the power button on the CPU seems to bring up a window 
with Ubuntu's power options.

  My Ubuntu version:
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Codename: trusty

  Kernel version:
  Linux nixentor 3.13.0-91-generic #138-Ubuntu SMP Fri Jun 24 17:00:34 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  I see the following output on dmesg:
  [15563.650717] [ cut here ]
  [15563.650730] WARNING: CPU: 7 PID: 0 at 
/build/linux-3r7mVb/linux-3.13.0/drivers/usb/host/xhci-ring.c:1590 
handle_cmd_completion+0xe56/0xe60()
  [15563.650732] Modules linked in: qcserial usb_wwan usbserial ip6table_filter 
ip6_tables iptable_filter ip_tables x_tables cachefiles cfg80211 rfcomm bnep 
nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_hdmi btusb 
bluetooth usb_storage mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd uvcvideo videobuf2_vmalloc videobuf2_memops 
joydev videobuf2_core snd_hda_codec_realtek videodev snd_usb_audio 
snd_usbmidi_lib 8812au(OX) snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_hda_intel snd_hda_codec snd_seq serio_raw snd_hwdep radeon snd_pcm mei_me 
snd_page_alloc mei snd_seq_device snd_timer snd ttm drm_kms_helper soundcore 
drm parport_pc i2c_algo_bit ppdev lp wmi parport video intel_smartconnect 
shpchp acpi_pad mac_hid hid_generic usbhid hid e1000e ahci psmouse ptp libahci 
pps_core
  [15563.650804] CPU: 7 PID: 0 Comm: swapper/7 Tainted: G   OX 
3.13.0-91-generic #138-Ubuntu
  [15563.650807] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Z97 Extreme4, BIOS P1.30 05/23/2014
  [15563.650809]   88041edc3d90 81729906 

  [15563.650813]  0009 88041edc3dc8 8106987d 
880404062d60
  [15563.650817]  8804040606b0 0010 0004040606b0 
8804041a
  [15563.650822] Call Trace:
  [15563.650824][] dump_stack+0x64/0x82
  [15563.650836]  [] warn_slowpath_common+0x7d/0xa0
  [15563.650840]  [] warn_slowpath_null+0x1a/0x20
  [15563.650845]  [] handle_cmd_completion+0xe56/0xe60
  [15563.650852]  [] ? check_preempt_curr+0x75/0xa0
  [15563.650857]  [] xhci_irq+0x33b/0xa50
  [15563.650861]  [] ? sched_clock_cpu+0xb5/0x100
  [15563.650865]  [] xhci_msi_irq+0x11/0x20
  [15563.650870]  [] handle_irq_event_percpu+0x4e/0x220
  [15563.650874]  [] handle_irq_event+0x3d/0x60
  [15563.650878]  [] handle_edge_irq+0x77/0x130
  [15563.650886]  [] handle_irq+0x1e/0x30
  [15563.650893]  [] do_IRQ+0x4d/0xc0
  [15563.650898]  [] common_interrupt+0x6d/0x6d
  [15563.650900][] ? cpuidle_enter_state+0x52/0xc0
  [15563.650910]  [] ? cpuidle_enter_state+0x48/0xc0
  [15563.650915]  [] cpuidle_idle_call+0xdc/0x220
  [15563.650921]  [] arch_cpu_idle+0xe/0x30
  [15563.650924]  [] cpu_startup_entry+0xc1/0x2b0
  [15563.650931]  [] start_secondary+0x21d/0x2d0
  [15563.650934] ---[ end trace d9b5447d0ddb440a ]---
  [15565.486066] xhci_hcd :00:14.0: xHCI host not responding to stop 
endpoint command.
  [15565.486075] xhci_hcd :00:14.0: Assuming host is dying, halting host.
  [15565.486120] xhci_hcd :00:14.0: HC died; cleaning up
  [15568.853140] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [15568.853149] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15569.057055] usb 3-14: device not accepting address 92, error -108
  [15574.055575] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15574.055587] xhci_hcd 

[Kernel-packages] [Bug 1603788] Re: usb mouse doesn't work in ubuntu 16.04

[Joseph Salisbury]

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

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 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.7-rc7


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

Title:
  usb mouse doesn't work in ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  mouse works in bios, not in ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity 2.21.63
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  Date: Sun Jul 17 17:32:59 2016
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
  SourcePackage: grub-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1604001] Re: igb: Detected TX unit hang

[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.7 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.7-rc7

** Tags added: kernel-da-key

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

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

Title:
  igb: Detected TX unit hang

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When putting network load onto the Intel I210 network card using
  iperf, i can reproducible get the igb driver to hang after 10-60
  seconds. This regression was also discovered on 3.16er kernels (see
  #LP: 1492146) - and it's still existing on newer kernels as well. This
  is on an ASRock C2550D4I mainboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.31.33
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Jul 18 15:07 seq
   crw-rw+ 1 root audio 116, 33 Jul 18 15:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Jul 18 15:12:12 2016
  HibernationDevice: RESUME=UUID=0ab9225c-c25b-4206-97c4-22d5f149db00
  InstallationDate: Installed on 2016-04-25 (83 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 003: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 002: ID 8087:07db Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=5f39676e-4001-4e75-bccc-19082ed6036d ro pci=nommconf pcie_aspm=off
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.30
  dmi.board.name: C2550D4I
  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.30:bd01/26/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnC2550D4I: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/1604001/+subscriptions

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

[Kernel-packages] [Bug 1603799] Re: On update_curr update_curr_rt issue

[Joseph Salisbury]

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

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

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

Title:
  On update_curr update_curr_rt issue

Status in linux package in Ubuntu:
  Triaged

Bug description:
  These functions spanning proc due multiple invocations.
  After appling follow patches time processor on pulseaudio, firefox, 
flash-playes descrease .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asu2840 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun Jul 17 21:39:35 2016
  InstallationDate: Installed on 2016-04-29 (79 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: Olidata S.p.A. ALABAMA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=/dev/mapper/192--168--0--108--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: S0101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ALABAMA
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Olidata S.p.A.

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

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

[Kernel-packages] [Bug 1603862] Re: [i915_bpo] tainted kernel: lspci, udevadm crashed

[Joseph Salisbury]

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

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

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

Title:
  [i915_bpo] tainted kernel: lspci, udevadm crashed

Status in linux package in Ubuntu:
  Triaged

Bug description:
  while verifying bug #1599109 , I'm not able to use certain commands:
  lspci, udevadm

  steps to reproduce:
  1. fresh isntall
  2. install testing kernel

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

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

[Kernel-packages] [Bug 1603810] Re: Ubuntu turns monitor permanently off during boot

[Joseph Salisbury]

Does booting back into the Trusty kernel on the Xenial installed system
make the bug go away?

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

** Tags added: kernel-da-key

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

Title:
  Ubuntu turns monitor permanently off during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a regression, at least trusty (and prior) worked fine on this
  hardware.

  Booting the Xenial installer image off USB also worked fine.

  The system boots fine, however the monitor is in DPMS power-off and
  does not ever turn back on. Switching VTs doesn't help, I have found
  no way to get it switch on.

  Removing '$vt_handoff' from grub resolves the problem and the system
  seems to work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jgg2224 F pulseaudio
   /dev/snd/controlC0:  jgg2224 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jul 17 14:04:30 2016
  HibernationDevice: RESUME=UUID=b254872c-e84b-427c-bebe-343c031cbdcd
  InstallationDate: Installed on 2016-04-22 (86 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/main2-xenial64 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M EVO
  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.:bvr0805:bd11/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MEVO: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/1603810/+subscriptions

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

[Kernel-packages] [Bug 1604153] [NEW] linux: 3.19.0-66.74 -proposed tracker

[Seth Forshee]

Public bug reported:

This bug is for tracking the 3.19.0-66.74 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

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

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


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

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

** Tags added: block-proposed-vivid

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

** Tags added: vivid

** 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-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => 

[Kernel-packages] [Bug 1603578] Re: unable to enumerate USB device

[Joseph Salisbury]

Does booting back into the prior kernel make the bug go away?

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

** Tags added: kernel-da-key

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

Title:
  unable to enumerate USB device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 16.04 LTS

  When I start the operating system, I get the messages:
  usb 5-1: device descriptor read/64, error -71
  usb 5-1: device not accepting address 4, error -71
  usb 5-1: device not accepting address 5, error -71
  usb usb5-port1: unable to enumerate USB device

  My external Seagate USB harddisk does not work.

  This problem started after the latest software update.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 16 08:30:51 2016
  HotplugNewDevices: /dev/sdd1 /dev/sdd
  HotplugNewMounts: /dev/sdd1 /media/colin/Seagate\040Expansion\040Drive 
fuseblk 
rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
  InstallationDate: Installed on 2016-06-11 (34 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. P55-UD3
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=8c0c09d5-9860-4049-a4db-3e06124c9601 ro quiet splash
  SourcePackage: udisks2
  Symptom: storage
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: P55-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd06/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
134cd00d766fc7014b53d9cea67a6bcb894ae51e

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1571798

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Broadwell ECRC Support missing in Ubuntu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Here is the problem statement from the Dell team:

  When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel
  Quick Assist Card, the memory location that corresponds to ECRC is set
  to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot.
  This causes the card to not function unless we implement the following
  workaround using setpci.

  “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for
  the Intel Quick Assit Card.

  We’ve verified the memory location is correct when booting to other
  OSes, such as RHEL 7.2 and Windows Server 2012 R2.

  If there is any information you can give as to why this may be
  occurring in Ubuntu or where we may start to debug when the memory is
  changed, we would appreciate it.

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

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

[Kernel-packages] [Bug 1587885] Re: NULL pointer dereference in radeon drm code

[Joseph Salisbury]

Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team
doesn't just apply the patch and fix it. The reason is that the kernel
team is reluctant (not opposed) to apply any patch to a stable kernel
that is not from upstream. Applying patches that don't come from
upstream add greatly to the support of the kernel as other upstream
patches may touch the same area as the non-upstream patch and may
prevent them from applying cleanly.

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu kernel.

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

Title:
  NULL pointer dereference in radeon drm code

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On one of my systems I use, display connector 0 does not have DDC.
  This results in the DRM code trying to use radeon_connector->ddc_bus
  when it is not set. This is known to have been an issue since the 3.2
  series kernels.

  Known Problem Kernels: uBuntu 12.04 LTS (linux-3.2.55), uBuntu-MATE 14.04 LTS 
(linux-3.16.7) and uBuntu-MATE 16.04 LTS (linux-4.4.8) and linux-4.6.0 (git:/
  /git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux).

  Trying to use the uBuntu-MATE 16.04 LTS LiveCD ubuntu-mate-16.04
  -desktop-amd64.iso (from uBuntu-MATE website) showed the problem.

  Using a serial console I extracted the following information when
  trying to boot from a uBuntu-MATE 16.04 LTS LiveCD USB Stick (it had
  been upgraded from 4.4.0-21-generic in an attempt to get something
  usable):

  
  [0.00] Linux version 4.4.0-22-generic (buildd@lgw01-41) (gcc version 
5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #40-Ubuntu SMP Thu May 12 22:03:46 
UTC 2
  016 (Ubuntu 4.4.0-22.40-generic 4.4.8)
  [0.00] Command line: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/ubuntu-mate.seed boot=casper locale=en_GB 
console-setup/layoutcode=gb console=u
  art,io,0x3f8,115200n8 earlyprintk=ttyS0,115200n8 debug ---
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  
  [0.00] efi: EFI v2.00 by Phoenix Technologies Ltd.
  [0.00] efi: EFI v2.00 by Phoenix Technologies Ltd.
  [0.00] efi: [0.00] efi:  ACPI=0x973c7000  ACPI=0x973c7000  
ACPI 2.0=0x973c7014  ACPI 2.0=0x973c7014  SMBIOS=0x9726b000  SMBIOS=0x9726b000 

  [0.00] SMBIOS 2.6 present.
  [0.00] SMBIOS 2.6 present.
  [0.00] DMI: AMD Corporation EBrazos Platform/Persimmon, BIOS LV-683 
Version: 1.1 02/14/2012
  [0.00] DMI: AMD Corporation EBrazos Platform/Persimmon, BIOS LV-683 
Version: 1.1 02/14/2012
  
  [8.262990] [drm] ib test on ring 5 succeeded
  [8.288897] [drm] Radeon Display Connectors
  [8.293175] [drm] Connector 0:
  [8.296252] [drm]   DP-1
  [8.298791] [drm]   Encoders:
  [8.301770] [drm] DFP1: INTERNAL_UNIPHY
  [8.305973] [drm] Connector 1:
  [8.309043] [drm]   DP-2
  [8.311598] [drm]   HPD2
  [8.314169] [drm]   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 
0x644c
  [8.321609] [drm]   Encoders:
  [8.324589] [drm] DFP2: INTERNAL_UNIPHY
  [8.328793] [drm] Connector 2:
  [8.331856] [drm]   VGA-1
  [8.332316] scsi 0:0:0:0: Direct-Access SMI  USB DISK 1100 
PQ: 0 ANSI: 0 CCS
  [8.342947] [drm]   DDC: 0x64d8 0x64d8 0x64dc 0x64dc 0x64e0 0x64e0 0x64e4 
0x64e4
  [8.350341] [drm]   Encoders:
  [8.353310] [drm] CRT1: INTERNAL_KLDSCP_DAC1
  [8.358195] BUG: unable to handle kernel NULL pointer dereference at 
0409
  [8.366104] IP:[8.367176] sd 0:0:0:0: Attached scsi generic sg1 type 0
  [8.368538] sd 0:0:0:0: [sdb] 7831552 512-byte logical blocks: (4.01 
GB/3.73 GiB)
  [8.369421] sd 0:0:0:0: [sdb] Write Protect is off
  [8.369427] sd 0:0:0:0: [sdb] Mode Sense: 43 00 00 00
  [8.370288] sd 0:0:0:0: [sdb] No Caching mode page found
  [8.370292] sd 0:0:0:0: [sdb] Assuming drive cache: write through
  [8.374944]  sdb: sdb1
  [8.378398] sd 0:0:0:0: [sdb] Attached SCSI removable disk

  [8.409733]  [] radeon_dp_getsinktype+0x1a/0x30 [radeon]
  [8.416805] PGD 0 
  [8.418841] Oops:  [#1] SMP 
  [8.422104] Modules linked in: hid_generic e1000e psmouse amdkfd 

[Kernel-packages] [Bug 1593261] Re: Using "splash" Linux boot option causes IPMI console view to blank

[Joseph Salisbury]

Can you also test the latest upstream 4.4 kernel?  This will tell us if
the fix in mainline was already sent to stable or not.  The 4.4.15
kernel can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.15

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

Title:
  Using "splash" Linux boot option causes IPMI console view to blank

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using a set of blade servers with SuperMicro BIOS and IPMI console
  viewing capabilities.  I use the Ubuntu netboot options with a PXE
  server to install.

  I've installed Ubuntu 12.04 and 14.04 on these systems, and everything
  works great.

  However, when I install Ubuntu 16.04 (and this is true both if I
  upgrade from Ubuntu 14.04 with do-release-upgrade AND when I install a
  fresh copy directly via the Ubuntu 16.04 netboot image via PXE), then
  the install works but when I reboot the IPMI console is completely
  blank: no cursor, no text, no typing shows anything.

  I can still SSH to the system (except of course the default netboot
  install doesn't include sshd for some bizarre reason so I had to play
  some tricks and rerun the install multiple times :-/).

  After a lot of experimentation I discovered that if I edit the
  /etc/default/grub file and remove the "splash" setting from
  GRUB_CMDLINE_LINUX_DEFAULT variable and re-run update-grub, then
  things worked fine and I was able to boot properly without losing
  access to the IPMI console.

  One more note: this is definitely a kernel issue because when I choose
  the older 14.04 kernel (3.13 or similar) from the boot menu on the
  system I upgraded from 14.04 to 16.04, with the "splash" setting still
  in the grub config and no other changes (so userspace is still all
  16.04), I had no problems with the IPMI console viewer.

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

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

[Kernel-packages] [Bug 1602801] Re: linux: 4.6.0-9.11 -proposed tracker

[Brad Figg]

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

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

** Changed in: kernel-development-workflow/promote-to-proposed
   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/1602801

Title:
  linux: 4.6.0-9.11 -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:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Confirmed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Yakkety:
  New

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

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

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

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

[Brad Figg]

Public bug reported:

This bug is for tracking the 3.13.0-93.140~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
-- swm properties --
kernel-stable-master-bug: 1604134

** 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-trusty (Ubuntu)
 Importance: Undecided
 Status: Invalid

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


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

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

** Tags added: block-proposed-precise

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

** Tags added: precise

** 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-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team 

[Kernel-packages] [Bug 1604134] Re: linux: 3.13.0-93.140 -proposed tracker

[Brad Figg]

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

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

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

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

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

** Description changed:

  This bug is for tracking the 3.13.0-93.140 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-phase:Packaging
+ kernel-stable-phase-changed:Monday, 18. July 2016 20:01 UTC

** Description changed:

  This bug is for tracking the 3.13.0-93.140 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-phase:Packaging
  kernel-stable-phase-changed:Monday, 18. July 2016 20:01 UTC
+ 
+ -- swm properties --
+ derivative-trackers-created: true
+ phase: Packaging

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

Title:
  linux: 3.13.0-93.140 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.13.0-93.140 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-phase:Packaging
  kernel-stable-phase-changed:Monday, 18. July 2016 20:01 UTC

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1604134] [NEW] linux: 3.13.0-93.140 -proposed tracker

[Seth Forshee]

Public bug reported:

This bug is for tracking the 3.13.0-93.140 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

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

** Affects: linux (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 (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-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided 

[Kernel-packages] [Bug 1603719] Re: NFS client: access problems after updating to kernel 4.4.0-31-generic

[Jurgen Schellaert]

Thanks for your helpful instructions.

The most recent mainline kernel (= 4.7.0-040700rc7-generic) appears to
be unaffected.

I can now enter the exported subfilesystems again with the expected
permissions.


** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.7rc7

** Tags removed: kernel-fixed-upstream-4.7rc7
** Tags added: kernel-fixed-upstream-4.7-rc7

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

Title:
  NFS client: access problems after updating to kernel 4.4.0-31-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am denied access to the subfilesystems exported by my nfs server
  (the top level filesystem itself is unaffected).

  The client is reporting that I do not have the necessary permissions.
  However, all was fine until the day before yesterday.

  When I revert my client to 4.4.0-28, everything is in working order again. I 
assume the permission problem is really a bug in kernel 4.4.0-31.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jurgen 1743 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=569da237-3a37-4fe3-b885-83213aae8b52
  InstallationDate: Installed on 2016-04-07 (101 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7514
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=f6f6bd51-4d4f-4547-b615-90319625d909 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/28/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7514
  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.1:bd05/28/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7514:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7514:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7514
  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/1603719/+subscriptions

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

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

[bugproxy]

--- Comment From ru...@us.ibm.com 2016-07-18 15:08 EDT---
.

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

Title:
  mounts cgroups unconditionally which causes undesired effects with cpu
  hotplug

Status in cgmanager package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Preeti U. Murthy  - 2014-10-20 
04:40:12 ==
  ---Problem Description---
  Systemd mounts cgroups explicitly every boot. Since the user had no say in 
it, undesired consequences are observed in reaction to cpu hotplug operations.  
Here is how.

  Systemd moves the tasks to the cgroup mounted by it. This cgroup 
automatically becomes the child of the root cgroup which is present by default. 
The children cgroups are not expected to remember their configured cpusets 
after hotplug operations in the kernel. Hence when cpus are taken offline and 
brought back online they are no longer used for load balancing of tasks and 
hence remain unused. 
 This is an undesired consequence because the user had not even asked for 
cgroups to be mounted, yet is not able to use the full capacity of the system.

  Only when the user himself creates cgroup hierarchies, should he be
  exposed to the side effects of cpu hotplug on cpusets. Else all online
  cpus must be made available to him which is not happening since
  systemd mounts cgroups on every boot.

  Hence please revert this feature or provide an explaination as to why this is 
being done.
   
  ---uname output---
  Linux tul181p1 3.16.0-18-generic #25-Ubuntu SMP Fri Sep 26 02:39:53 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Tuleta 8286-42A 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   $ taskset -p $$
  $ 0-127
  $ echo 0 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
  $ echo 1 > /sys/devices/system/cpu/cpu7/online
  $ taskset -p $$
  $ 0-6,8-127
   
   
  Userspace tool common name: systemd 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd_208-8ubuntu8_ppc64el.deb

  Userspace tool obtained from project website:   208-8ubuntu8

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

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

[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

[John Mazzie]

This kernel version is broken.

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

Title:
  Broadwell ECRC Support missing in Ubuntu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Here is the problem statement from the Dell team:

  When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel
  Quick Assist Card, the memory location that corresponds to ECRC is set
  to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot.
  This causes the card to not function unless we implement the following
  workaround using setpci.

  “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for
  the Intel Quick Assit Card.

  We’ve verified the memory location is correct when booting to other
  OSes, such as RHEL 7.2 and Windows Server 2012 R2.

  If there is any information you can give as to why this may be
  occurring in Ubuntu or where we may start to debug when the memory is
  changed, we would appreciate it.

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

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

[Kernel-packages] [Bug 1600624] Re: MacBook wifi doesn't work (brcmfmac)

[Lars Peter Thomsen]

Issue remains on 4.7-rc7

$ dmesg | grep brcm
[5.972119] usbcore: registered new interface driver brcmfmac
[6.100313] brcmfmac :03:00.0: Direct firmware load for 
brcm/brcmfmac43602-pcie.txt failed with error -2
[6.585372] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 
2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c
[6.616459] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code (0x30 
0x30)
[6.621156] brcmfmac :03:00.0 wlp3s0: renamed from wlan0
[  312.109760] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table 
err:-23
$ sudo find / -name brcmfmac43602*
/lib/firmware/brcm/brcmfmac43602-pcie.bin
/lib/firmware/brcm/brcmfmac43602-pcie.ap.bin
$ uname -a
Linux Saturn 4.7.0-040700rc7-generic #201607110032 SMP Mon Jul 11 04:34:25 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux


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

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

Title:
  MacBook wifi doesn't work (brcmfmac)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  wifi doesn't work at all. Output from dmesg:
  [...]
  brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt 
failed with error -2
  ...
  brcmf_cfg80211_reg_notifier: not a ISO3166 code

  There is no file brcmfmac43602-pcie.txt anywhere on the system.
  However, /lib/firmware/brcm/brcmfmac43602-pcie.bin does exist.

  Iw reg get outputs:
  sudo iw reg get
  country DK: DFS-ETSI
   (2402 - 2482 @ 40), (N/A, 20), (N/A)
   (5170 - 5250 @ 80), (N/A, 20), (N/A)
   (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
   (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
   (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lars   2010 F pulseaudio
   /dev/snd/controlC0:  lars   2010 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jul 10 19:41:18 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a45b9984-4de8-49e3-ba57-a98ae560ad61
  InstallationDate: Installed on 2016-01-30 (162 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=d3ba9d27-321b-45cb-99f2-776b10c1dc7a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (78 days ago)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

[Joseph Salisbury]

Thanks for re-running the test, John.  I restarted the bisect and marked
ea584595fc85e65796335033dfca25ed655cd0ed as good this time.


I built the next test kernel, up to the following commit:
783a28ec0bf2c2d560d8004c92919d112a777e55

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1571798

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Broadwell ECRC Support missing in Ubuntu

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Here is the problem statement from the Dell team:

  When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel
  Quick Assist Card, the memory location that corresponds to ECRC is set
  to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot.
  This causes the card to not function unless we implement the following
  workaround using setpci.

  “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for
  the Intel Quick Assit Card.

  We’ve verified the memory location is correct when booting to other
  OSes, such as RHEL 7.2 and Windows Server 2012 R2.

  If there is any information you can give as to why this may be
  occurring in Ubuntu or where we may start to debug when the memory is
  changed, we would appreciate it.

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

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

[Kernel-packages] [Bug 1604099] [NEW] linux: 3.2.0-107.148 -proposed tracker

[Seth Forshee]

Public bug reported:

This bug is for tracking the 3.2.0-107.148 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

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

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

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

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

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


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

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

** Tags added: block-proposed-precise

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

** Tags added: precise

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

** Also affects: kernel-sru-workflow/prepare-package-meta
   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-lbm
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-lbm
 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/promote-to-proposed
   

[Kernel-packages] [Bug 1589036] Re: CVE-2016-5243

[Seth Forshee]

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

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

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

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

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

Title:
  CVE-2016-5243

Status in linux package in Ubuntu:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish 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-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  New
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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-lts-xenial 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-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon 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-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-lts-vivid source package in Trusty:
  New
Status in linux-lts-wily source package in Trusty:
  New
Status in linux-lts-xenial 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-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon 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:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  New
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily 

[Kernel-packages] [Bug 1601831] Re: qeth: delete napi struct when removing a qeth device

[Seth Forshee]

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

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

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

Title:
  qeth: delete napi struct when removing a qeth device

Status in Linux:
  New
Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  == Comment: #0 - Hendrik Brueckner  - 2016-07-08 
10:59:08 ==
  Please backport:
  commit 7831b4ff0d926e0deeaabef9db8800ed069a2757
  Author: Ursula Braun 
  Date:   Mon Jul 4 14:07:16 2016 +0200

  qeth: delete napi struct when removing a qeth device
  
  A qeth_card contains a napi_struct linked to the net_device during
  device probing. This struct must be deleted when removing the qeth
  device, otherwise Panic on oops can occur when qeth devices are
  repeatedly removed and added.
  
  Fixes: a1c3ed4c9ca ("qeth: NAPI support for l2 and l3 discipline")
  Cc: sta...@vger.kernel.org # v2.6.37+
  Signed-off-by: Ursula Braun 
  Tested-by: Alexander Klein 
  Signed-off-by: David S. Miller 

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

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