[Kernel-packages] [Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

2016-06-14 Thread cooloutac
I get missing firmware for noveau.  don't know what i'm supposed to do
sorry.

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

Title:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

  ecryptfs_readpage: Error decrypting page; rc = [-4]

  I dont' have this issue showing in dmesg when using 3.19 kernel,  only
  with later kernels.  Is it related to selecting encrypted home on
  install or something?

   I don't notice any issues with performance because of it or have any
  other error messages.  I am using default ubuntu xenial 16.04 with
  unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cooloutac   2054 F pulseaudio
   /dev/snd/pcmC0D0p:   cooloutac   2054 F...m pulseaudio
   /dev/snd/controlC0:  cooloutac   2054 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 22:38:44 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1
  InstallationDate: Installed on 2016-05-20 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Studio XPS 7100
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NWWY0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 7100
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1578493] Re: CVE-2016-4482

2016-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-raspi2 - 4.4.0-1013.17

---
linux-raspi2 (4.4.0-1013.17) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1591461

  [ Ubuntu: 4.4.0-25.44 ]

  * Xenial update to v4.4.13 stable release (LP: #1590455)
- MIPS64: R6: R2 emulation bugfix
- MIPS: math-emu: Fix jalr emulation when rd == $0
- MIPS: MSA: Fix a link error on `_init_msa_upper' with older GCC
- MIPS: Don't unwind to user mode with EVA
- MIPS: Avoid using unwind_stack() with usermode
- MIPS: Fix siginfo.h to use strict posix types
- MIPS: Fix uapi include in exported asm/siginfo.h
- MIPS: Fix watchpoint restoration
- MIPS: Flush highmem pages in __flush_dcache_page
- MIPS: Handle highmem pages in __update_cache
- MIPS: Sync icache & dcache in set_pte_at
- MIPS: ath79: make bootconsole wait for both THRE and TEMT
- MIPS: Reserve nosave data for hibernation
- MIPS: Loongson-3: Reserve 32MB for RS780E integrated GPU
- MIPS: Use copy_s.fmt rather than copy_u.fmt
- MIPS: Fix MSA ld_*/st_* asm macros to use PTR_ADDU
- MIPS: Prevent "restoration" of MSA context in non-MSA kernels
- MIPS: Disable preemption during prctl(PR_SET_FP_MODE, ...)
- MIPS: ptrace: Fix FP context restoration FCSR regression
- MIPS: ptrace: Prevent writes to read-only FCSR bits
- MIPS: Fix sigreturn via VDSO on microMIPS kernel
- MIPS: Build microMIPS VDSO for microMIPS kernels
- MIPS: lib: Mark intrinsics notrace
- MIPS: VDSO: Build with `-fno-strict-aliasing'
- affs: fix remount failure when there are no options changed
- ASoC: ak4642: Enable cache usage to fix crashes on resume
- Input: uinput - handle compat ioctl for UI_SET_PHYS
- ARM: mvebu: fix GPIO config on the Linksys boards
- ARM: dts: at91: fix typo in sama5d2 PIN_PD24 description
- ARM: dts: exynos: Add interrupt line to MAX8997 PMIC on exynos4210-trats
- ARM: dts: imx35: restore existing used clock enumeration
- ath9k: Add a module parameter to invert LED polarity.
- ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- ath10k: fix debugfs pktlog_filter write
- ath10k: fix firmware assert in monitor mode
- ath10k: fix rx_channel during hw reconfigure
- ath10k: fix kernel panic, move arvifs list head init before htt init
- ath5k: Change led pin configuration for compaq c700 laptop
- hwrng: exynos - Fix unbalanced PM runtime put on timeout error path
- rtlwifi: rtl8723be: Add antenna select module parameter
- rtlwifi: btcoexist: Implement antenna selection
- rtlwifi: Fix logic error in enter/exit power-save mode
- rtlwifi: pci: use dev_kfree_skb_irq instead of kfree_skb in
  rtl_pci_reset_trx_ring
- aacraid: Relinquish CPU during timeout wait
- aacraid: Fix for aac_command_thread hang
- aacraid: Fix for KDUMP driver hang
- hwmon: (ads7828) Enable internal reference
- mfd: intel-lpss: Save register context on suspend
- mfd: intel_soc_pmic_core: Terminate panel control GPIO lookup table
  correctly
- PM / Runtime: Fix error path in pm_runtime_force_resume()
- cpuidle: Indicate when a device has been unregistered
- cpuidle: Fix cpuidle_state_is_coupled() argument in cpuidle_enter()
- clk: bcm2835: Fix PLL poweron
- clk: at91: fix check of clk_register() returned value
- clk: bcm2835: pll_off should only update CM_PLL_ANARST
- clk: bcm2835: divider value has to be 1 or more
- pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- PCI: Disable all BAR sizing for devices with non-compliant BARs
- media: v4l2-compat-ioctl32: fix missing reserved field copy in
  put_v4l2_create32
- mm: use phys_addr_t for reserve_bootmem_region() arguments
- wait/ptrace: assume __WALL if the child is traced
- QE-UART: add "fsl,t1040-ucc-uart" to of_device_id
- powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- powerpc/eeh: Don't report error in eeh_pe_reset_and_recover()
- powerpc/eeh: Restore initial state in eeh_pe_reset_and_recover()
- xen/events: Don't move disabled irqs
- xen: use same main loop for counting and remapping pages
- sunrpc: fix stripping of padded MIC tokens
- drm/gma500: Fix possible out of bounds read
- drm/vmwgfx: Enable SVGA_3D_CMD_DX_SET_PREDICATION
- drm/vmwgfx: use vmw_cmd_dx_cid_check for query commands.
- drm/vmwgfx: Fix order of operation
- drm/amdgpu: use drm_mode_vrefresh() rather than mode->vrefresh
- drm/amdgpu: Fix hdmi deep color support.
- drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config()
- drm/fb_helper: Fix references to dev->mode_config.num_connector
- drm/atomic: Verify connector->funcs != NULL when clearing states
- drm/i915: Don't leave old junk in ilk active watermarks on readout
- drm/imx: Match imx-ipuv3-crtc components using device 

[Kernel-packages] [Bug 1580379] Re: CVE-2016-4569

2016-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-raspi2 - 4.4.0-1013.17

---
linux-raspi2 (4.4.0-1013.17) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1591461

  [ Ubuntu: 4.4.0-25.44 ]

  * Xenial update to v4.4.13 stable release (LP: #1590455)
- MIPS64: R6: R2 emulation bugfix
- MIPS: math-emu: Fix jalr emulation when rd == $0
- MIPS: MSA: Fix a link error on `_init_msa_upper' with older GCC
- MIPS: Don't unwind to user mode with EVA
- MIPS: Avoid using unwind_stack() with usermode
- MIPS: Fix siginfo.h to use strict posix types
- MIPS: Fix uapi include in exported asm/siginfo.h
- MIPS: Fix watchpoint restoration
- MIPS: Flush highmem pages in __flush_dcache_page
- MIPS: Handle highmem pages in __update_cache
- MIPS: Sync icache & dcache in set_pte_at
- MIPS: ath79: make bootconsole wait for both THRE and TEMT
- MIPS: Reserve nosave data for hibernation
- MIPS: Loongson-3: Reserve 32MB for RS780E integrated GPU
- MIPS: Use copy_s.fmt rather than copy_u.fmt
- MIPS: Fix MSA ld_*/st_* asm macros to use PTR_ADDU
- MIPS: Prevent "restoration" of MSA context in non-MSA kernels
- MIPS: Disable preemption during prctl(PR_SET_FP_MODE, ...)
- MIPS: ptrace: Fix FP context restoration FCSR regression
- MIPS: ptrace: Prevent writes to read-only FCSR bits
- MIPS: Fix sigreturn via VDSO on microMIPS kernel
- MIPS: Build microMIPS VDSO for microMIPS kernels
- MIPS: lib: Mark intrinsics notrace
- MIPS: VDSO: Build with `-fno-strict-aliasing'
- affs: fix remount failure when there are no options changed
- ASoC: ak4642: Enable cache usage to fix crashes on resume
- Input: uinput - handle compat ioctl for UI_SET_PHYS
- ARM: mvebu: fix GPIO config on the Linksys boards
- ARM: dts: at91: fix typo in sama5d2 PIN_PD24 description
- ARM: dts: exynos: Add interrupt line to MAX8997 PMIC on exynos4210-trats
- ARM: dts: imx35: restore existing used clock enumeration
- ath9k: Add a module parameter to invert LED polarity.
- ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- ath10k: fix debugfs pktlog_filter write
- ath10k: fix firmware assert in monitor mode
- ath10k: fix rx_channel during hw reconfigure
- ath10k: fix kernel panic, move arvifs list head init before htt init
- ath5k: Change led pin configuration for compaq c700 laptop
- hwrng: exynos - Fix unbalanced PM runtime put on timeout error path
- rtlwifi: rtl8723be: Add antenna select module parameter
- rtlwifi: btcoexist: Implement antenna selection
- rtlwifi: Fix logic error in enter/exit power-save mode
- rtlwifi: pci: use dev_kfree_skb_irq instead of kfree_skb in
  rtl_pci_reset_trx_ring
- aacraid: Relinquish CPU during timeout wait
- aacraid: Fix for aac_command_thread hang
- aacraid: Fix for KDUMP driver hang
- hwmon: (ads7828) Enable internal reference
- mfd: intel-lpss: Save register context on suspend
- mfd: intel_soc_pmic_core: Terminate panel control GPIO lookup table
  correctly
- PM / Runtime: Fix error path in pm_runtime_force_resume()
- cpuidle: Indicate when a device has been unregistered
- cpuidle: Fix cpuidle_state_is_coupled() argument in cpuidle_enter()
- clk: bcm2835: Fix PLL poweron
- clk: at91: fix check of clk_register() returned value
- clk: bcm2835: pll_off should only update CM_PLL_ANARST
- clk: bcm2835: divider value has to be 1 or more
- pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- PCI: Disable all BAR sizing for devices with non-compliant BARs
- media: v4l2-compat-ioctl32: fix missing reserved field copy in
  put_v4l2_create32
- mm: use phys_addr_t for reserve_bootmem_region() arguments
- wait/ptrace: assume __WALL if the child is traced
- QE-UART: add "fsl,t1040-ucc-uart" to of_device_id
- powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- powerpc/eeh: Don't report error in eeh_pe_reset_and_recover()
- powerpc/eeh: Restore initial state in eeh_pe_reset_and_recover()
- xen/events: Don't move disabled irqs
- xen: use same main loop for counting and remapping pages
- sunrpc: fix stripping of padded MIC tokens
- drm/gma500: Fix possible out of bounds read
- drm/vmwgfx: Enable SVGA_3D_CMD_DX_SET_PREDICATION
- drm/vmwgfx: use vmw_cmd_dx_cid_check for query commands.
- drm/vmwgfx: Fix order of operation
- drm/amdgpu: use drm_mode_vrefresh() rather than mode->vrefresh
- drm/amdgpu: Fix hdmi deep color support.
- drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config()
- drm/fb_helper: Fix references to dev->mode_config.num_connector
- drm/atomic: Verify connector->funcs != NULL when clearing states
- drm/i915: Don't leave old junk in ilk active watermarks on readout
- drm/imx: Match imx-ipuv3-crtc components using device 

[Kernel-packages] [Bug 1581866] Re: CVE-2016-4578

2016-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-raspi2 - 4.4.0-1013.17

---
linux-raspi2 (4.4.0-1013.17) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1591461

  [ Ubuntu: 4.4.0-25.44 ]

  * Xenial update to v4.4.13 stable release (LP: #1590455)
- MIPS64: R6: R2 emulation bugfix
- MIPS: math-emu: Fix jalr emulation when rd == $0
- MIPS: MSA: Fix a link error on `_init_msa_upper' with older GCC
- MIPS: Don't unwind to user mode with EVA
- MIPS: Avoid using unwind_stack() with usermode
- MIPS: Fix siginfo.h to use strict posix types
- MIPS: Fix uapi include in exported asm/siginfo.h
- MIPS: Fix watchpoint restoration
- MIPS: Flush highmem pages in __flush_dcache_page
- MIPS: Handle highmem pages in __update_cache
- MIPS: Sync icache & dcache in set_pte_at
- MIPS: ath79: make bootconsole wait for both THRE and TEMT
- MIPS: Reserve nosave data for hibernation
- MIPS: Loongson-3: Reserve 32MB for RS780E integrated GPU
- MIPS: Use copy_s.fmt rather than copy_u.fmt
- MIPS: Fix MSA ld_*/st_* asm macros to use PTR_ADDU
- MIPS: Prevent "restoration" of MSA context in non-MSA kernels
- MIPS: Disable preemption during prctl(PR_SET_FP_MODE, ...)
- MIPS: ptrace: Fix FP context restoration FCSR regression
- MIPS: ptrace: Prevent writes to read-only FCSR bits
- MIPS: Fix sigreturn via VDSO on microMIPS kernel
- MIPS: Build microMIPS VDSO for microMIPS kernels
- MIPS: lib: Mark intrinsics notrace
- MIPS: VDSO: Build with `-fno-strict-aliasing'
- affs: fix remount failure when there are no options changed
- ASoC: ak4642: Enable cache usage to fix crashes on resume
- Input: uinput - handle compat ioctl for UI_SET_PHYS
- ARM: mvebu: fix GPIO config on the Linksys boards
- ARM: dts: at91: fix typo in sama5d2 PIN_PD24 description
- ARM: dts: exynos: Add interrupt line to MAX8997 PMIC on exynos4210-trats
- ARM: dts: imx35: restore existing used clock enumeration
- ath9k: Add a module parameter to invert LED polarity.
- ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- ath10k: fix debugfs pktlog_filter write
- ath10k: fix firmware assert in monitor mode
- ath10k: fix rx_channel during hw reconfigure
- ath10k: fix kernel panic, move arvifs list head init before htt init
- ath5k: Change led pin configuration for compaq c700 laptop
- hwrng: exynos - Fix unbalanced PM runtime put on timeout error path
- rtlwifi: rtl8723be: Add antenna select module parameter
- rtlwifi: btcoexist: Implement antenna selection
- rtlwifi: Fix logic error in enter/exit power-save mode
- rtlwifi: pci: use dev_kfree_skb_irq instead of kfree_skb in
  rtl_pci_reset_trx_ring
- aacraid: Relinquish CPU during timeout wait
- aacraid: Fix for aac_command_thread hang
- aacraid: Fix for KDUMP driver hang
- hwmon: (ads7828) Enable internal reference
- mfd: intel-lpss: Save register context on suspend
- mfd: intel_soc_pmic_core: Terminate panel control GPIO lookup table
  correctly
- PM / Runtime: Fix error path in pm_runtime_force_resume()
- cpuidle: Indicate when a device has been unregistered
- cpuidle: Fix cpuidle_state_is_coupled() argument in cpuidle_enter()
- clk: bcm2835: Fix PLL poweron
- clk: at91: fix check of clk_register() returned value
- clk: bcm2835: pll_off should only update CM_PLL_ANARST
- clk: bcm2835: divider value has to be 1 or more
- pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- PCI: Disable all BAR sizing for devices with non-compliant BARs
- media: v4l2-compat-ioctl32: fix missing reserved field copy in
  put_v4l2_create32
- mm: use phys_addr_t for reserve_bootmem_region() arguments
- wait/ptrace: assume __WALL if the child is traced
- QE-UART: add "fsl,t1040-ucc-uart" to of_device_id
- powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- powerpc/eeh: Don't report error in eeh_pe_reset_and_recover()
- powerpc/eeh: Restore initial state in eeh_pe_reset_and_recover()
- xen/events: Don't move disabled irqs
- xen: use same main loop for counting and remapping pages
- sunrpc: fix stripping of padded MIC tokens
- drm/gma500: Fix possible out of bounds read
- drm/vmwgfx: Enable SVGA_3D_CMD_DX_SET_PREDICATION
- drm/vmwgfx: use vmw_cmd_dx_cid_check for query commands.
- drm/vmwgfx: Fix order of operation
- drm/amdgpu: use drm_mode_vrefresh() rather than mode->vrefresh
- drm/amdgpu: Fix hdmi deep color support.
- drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config()
- drm/fb_helper: Fix references to dev->mode_config.num_connector
- drm/atomic: Verify connector->funcs != NULL when clearing states
- drm/i915: Don't leave old junk in ilk active watermarks on readout
- drm/imx: Match imx-ipuv3-crtc components using device 

[Kernel-packages] [Bug 1585365] Re: CVE-2016-4951

2016-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-raspi2 - 4.4.0-1013.17

---
linux-raspi2 (4.4.0-1013.17) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1591461

  [ Ubuntu: 4.4.0-25.44 ]

  * Xenial update to v4.4.13 stable release (LP: #1590455)
- MIPS64: R6: R2 emulation bugfix
- MIPS: math-emu: Fix jalr emulation when rd == $0
- MIPS: MSA: Fix a link error on `_init_msa_upper' with older GCC
- MIPS: Don't unwind to user mode with EVA
- MIPS: Avoid using unwind_stack() with usermode
- MIPS: Fix siginfo.h to use strict posix types
- MIPS: Fix uapi include in exported asm/siginfo.h
- MIPS: Fix watchpoint restoration
- MIPS: Flush highmem pages in __flush_dcache_page
- MIPS: Handle highmem pages in __update_cache
- MIPS: Sync icache & dcache in set_pte_at
- MIPS: ath79: make bootconsole wait for both THRE and TEMT
- MIPS: Reserve nosave data for hibernation
- MIPS: Loongson-3: Reserve 32MB for RS780E integrated GPU
- MIPS: Use copy_s.fmt rather than copy_u.fmt
- MIPS: Fix MSA ld_*/st_* asm macros to use PTR_ADDU
- MIPS: Prevent "restoration" of MSA context in non-MSA kernels
- MIPS: Disable preemption during prctl(PR_SET_FP_MODE, ...)
- MIPS: ptrace: Fix FP context restoration FCSR regression
- MIPS: ptrace: Prevent writes to read-only FCSR bits
- MIPS: Fix sigreturn via VDSO on microMIPS kernel
- MIPS: Build microMIPS VDSO for microMIPS kernels
- MIPS: lib: Mark intrinsics notrace
- MIPS: VDSO: Build with `-fno-strict-aliasing'
- affs: fix remount failure when there are no options changed
- ASoC: ak4642: Enable cache usage to fix crashes on resume
- Input: uinput - handle compat ioctl for UI_SET_PHYS
- ARM: mvebu: fix GPIO config on the Linksys boards
- ARM: dts: at91: fix typo in sama5d2 PIN_PD24 description
- ARM: dts: exynos: Add interrupt line to MAX8997 PMIC on exynos4210-trats
- ARM: dts: imx35: restore existing used clock enumeration
- ath9k: Add a module parameter to invert LED polarity.
- ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- ath10k: fix debugfs pktlog_filter write
- ath10k: fix firmware assert in monitor mode
- ath10k: fix rx_channel during hw reconfigure
- ath10k: fix kernel panic, move arvifs list head init before htt init
- ath5k: Change led pin configuration for compaq c700 laptop
- hwrng: exynos - Fix unbalanced PM runtime put on timeout error path
- rtlwifi: rtl8723be: Add antenna select module parameter
- rtlwifi: btcoexist: Implement antenna selection
- rtlwifi: Fix logic error in enter/exit power-save mode
- rtlwifi: pci: use dev_kfree_skb_irq instead of kfree_skb in
  rtl_pci_reset_trx_ring
- aacraid: Relinquish CPU during timeout wait
- aacraid: Fix for aac_command_thread hang
- aacraid: Fix for KDUMP driver hang
- hwmon: (ads7828) Enable internal reference
- mfd: intel-lpss: Save register context on suspend
- mfd: intel_soc_pmic_core: Terminate panel control GPIO lookup table
  correctly
- PM / Runtime: Fix error path in pm_runtime_force_resume()
- cpuidle: Indicate when a device has been unregistered
- cpuidle: Fix cpuidle_state_is_coupled() argument in cpuidle_enter()
- clk: bcm2835: Fix PLL poweron
- clk: at91: fix check of clk_register() returned value
- clk: bcm2835: pll_off should only update CM_PLL_ANARST
- clk: bcm2835: divider value has to be 1 or more
- pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- PCI: Disable all BAR sizing for devices with non-compliant BARs
- media: v4l2-compat-ioctl32: fix missing reserved field copy in
  put_v4l2_create32
- mm: use phys_addr_t for reserve_bootmem_region() arguments
- wait/ptrace: assume __WALL if the child is traced
- QE-UART: add "fsl,t1040-ucc-uart" to of_device_id
- powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- powerpc/eeh: Don't report error in eeh_pe_reset_and_recover()
- powerpc/eeh: Restore initial state in eeh_pe_reset_and_recover()
- xen/events: Don't move disabled irqs
- xen: use same main loop for counting and remapping pages
- sunrpc: fix stripping of padded MIC tokens
- drm/gma500: Fix possible out of bounds read
- drm/vmwgfx: Enable SVGA_3D_CMD_DX_SET_PREDICATION
- drm/vmwgfx: use vmw_cmd_dx_cid_check for query commands.
- drm/vmwgfx: Fix order of operation
- drm/amdgpu: use drm_mode_vrefresh() rather than mode->vrefresh
- drm/amdgpu: Fix hdmi deep color support.
- drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config()
- drm/fb_helper: Fix references to dev->mode_config.num_connector
- drm/atomic: Verify connector->funcs != NULL when clearing states
- drm/i915: Don't leave old junk in ilk active watermarks on readout
- drm/imx: Match imx-ipuv3-crtc components using device 

[Kernel-packages] [Bug 203473] Re: rejected 1 configuration due to insufficient available bus power

2016-06-14 Thread -None-
Hi, guys
I have the same situation with USB flash drive in the DELL (SK-8135) keyboard 
at Ubuntu 16.04 LTS

dmesg:
[ 2677.375539] usb 7-1.3: new full-speed USB device number 6 using xhci_hcd
[ 2677.487556] usb 7-1.3: not running at top speed; connect to a high speed hub
[ 2677.511560] usb 7-1.3: New USB device found, idVendor=0781, idProduct=5571
[ 2677.511567] usb 7-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 2677.511571] usb 7-1.3: Product: Cruzer Fit
[ 2677.511575] usb 7-1.3: Manufacturer: SanDisk
[ 2677.511578] usb 7-1.3: SerialNumber: 4C530012740827123152
[ 2677.512059] usb 7-1.3: rejected 1 configuration due to insufficient 
available bus power
[ 2677.512067] usb 7-1.3: no configuration chosen from 1 choice
[ 2704.060356] usb 7-1.3: USB disconnect, device number 6

uname -a:
Linux xubuntu 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  rejected 1 configuration due to insufficient available bus power

Status in devicekit package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: hal

  I'm not sure wether this is the right package, but I hope somebody will point 
me to the right direction if it is not.
  When I connect my portable music player (a cmx stingray 888) to the USB port 
on the front panel of my pc, it works without any problem. When I connect it to 
my keyboard which has an USB hub included, nothing happens. So I looked into my 
syslog and found the following lines:

  Mar 18 09:24:11 weintraube kernel: [  215.220320] usb 2-2.2: new full speed 
USB device using uhci_hcd and address 7
  Mar 18 09:24:11 weintraube kernel: [  215.322158] usb 2-2.2: not running at 
top speed; connect to a high speed hub
  Mar 18 09:24:11 weintraube kernel: [  215.344246] usb 2-2.2: rejected 1 
configuration due to insufficient available bus power
  Mar 18 09:24:11 weintraube kernel: [  215.344252] usb 2-2.2: no configuration 
chosen from 1 choice

  I think there should be a notification in this case, because a user
  new to ubuntu would expect the device to do something but instead gets
  no visible action. The message could be something like "the usb
  connector where you attached your device does not have enough power,
  try connecting on another one" (of course not by word - my english is
  not that good).

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

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


[Kernel-packages] [Bug 1591293] Re: kernel fails to boot from SSD on non AHCI chipset (NCQ unsupported)

2016-06-14 Thread FerVira
I did test the kernel Joseph said:
linux-image-4.7.0-040700rc1-lowlatency_4.7.0-040700rc1.201606100619_amd64.deb

Bug is still there.

I did reset the PC as soon as kernel take too long to boot and began to inform 
that NCQ command was failing, with similar errors than with xenial kernel, such 
as:
equipment kernel: [ 64.970612] ata4.00: failed command: READ FPDMA QUEUED
equipment kernel: [ 64.970638] ata4.00: status: { DRDY }
equipment kernel: [ 64.994812] ata4: hard resetting link 

After reset and reboot with libata.force=noncq nothing was logged to syslog.  I 
didn't want to complete a fifteen minutes boot with a failing upstream kernel 
oriented to yakkety in my xenial installation, fearing it could break some 
bytes.  I already spent too much time to install and configure xenial.
I hope this helps anyway.
BTW can't you just check if something has been done with upstream kernels to 
correct this behaviour?
Thanks for your job.

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

Title:
  kernel fails to boot from SSD on non AHCI chipset (NCQ unsupported)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 64bits WON'T BOOT from a SSD Kinsgton Savage (2016) on chipset 
ASUS M2N68-AM SE (2010) with non-AHCI SATA2
  SATA Settings: 32 bit transfers: ENABLED,  AHCI mode: not available.
  Fresh installed system FREEZES inmediatly after starting to boot, PC looses 
its video signal.
  kern.log does not register anything.

  This motherboard does not support AHCI, but the SSD does.  Fresh
  installed 16.04 kernel does not disable NCQ (AHCI).

  Same system will slowly boot with errors when disabling 32 Bit transfers from 
BIOS, and freeze.
  Same PC boot ubuntustudio 12.04 live usb automatically disabling NCQ when SSD 
is connected.
  SAME SSD WILL BOOT without erros on chipset Intel Pinetrail-M with SATA3 and 
AHCI.
  (Same SSD and both PC boot fresh Windows 10 in sixteen seconds without any 
issue.)

  Expected behaviour:
  Kernel recognizes that AHCI is not supported by the hardware, and then 
disables NCQ because it requires AHCI,
  OR kernel recognizes that NCQ commands are failing and then disables NCQ,
  and by disabling NCQ the system can boot without any problem.

  Real behaviour:
  Kernel only disables NCQ when SSD drives are on a blacklist, but does not 
disable it when the chipset does not support AHCI (NCQ).  Kernel isn't 
disabling NCQ even when NCQ commands are failing.  This way system won't boot, 
or will boot but then freeze.

  It's not easy to understand why the system isn't booting. Many users
  are replacing their hard drives with SSD to improve the performance of
  their not-so-old PC, and if chipset does not support AHCI they will
  need to do expert diagnosis and tweaks to make ubuntu boot.

  Other tests:
  SATA Settings: 32 BIT TRANSFER: DISABLED, AHCI: not available.
  System boots from SSD with ATA errors and taking some minutes when it should 
take some seconds.
  Kernel DOES NOT disable NCQ after failing (it does on 12.04 live, same PC)
  System becomes definetly unresponsive a few minutes after start up, mouse 
pointer still moves but does not respond to clicks, and PC has to be hard reset.
  (In the posterior boot, system cleans some orphan inodes for one of the 
dm-crypt volumes)

  kern.log:

  Jun  9 22:24:41 equipment kernel: [0.00] Linux version 
4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 (Ubuntu 
5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 (Ubuntu 
4.4.0-21.37-generic 4.4.6)
  Jun  9 22:24:41 equipment kernel: [0.00] Command line: 
BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=88b24888-31fd-4a8e-98cd-f7e34b2bcc39 ro quiet splash
  
  Jun  9 22:24:41 equipment kernel: [0.00] DMI: System manufacturer 
System Product Name/M2N68-AM SE, BIOS 080407/26/2010
  ...
  Jun  9 22:24:41 equipment kernel: [2.073694] ata4.00: ATA-9: KINGSTON 
SHSS37A480G, SAFM00.U, max UDMA/133
  Jun  9 22:24:41 equipment kernel: [2.073697] ata4.00: 937703088 sectors, 
multi 16: LBA48 NCQ (depth 31/32)
  Jun  9 22:24:41 equipment kernel: [2.073777] ata4.00: configured for 
UDMA/133
  Jun  9 22:24:41 equipment kernel: [2.076892] ata3: SATA link down 
(SStatus 0 SControl 300)
  Jun  9 22:24:41 equipment kernel: [2.077116] scsi 3:0:0:0: Direct-Access  
   ATA  KINGSTON SHSS37A 00.U PQ: 0 ANSI: 5
  Jun  9 22:24:41 equipment kernel: [2.077421] sd 3:0:0:0: [sda] 937703088 
512-byte logical blocks: (480 GB/447 GiB)
  Jun  9 22:24:41 equipment kernel: [2.077494] sd 3:0:0:0: [sda] Write 
Protect is off
  Jun  9 22:24:41 equipment kernel: [2.077496] sd 3:0:0:0: [sda] Mode 
Sense: 00 3a 00 00
  Jun  9 22:24:41 equipment kernel: [2.077528] sd 3:0:0:0: [sda] Write 
cache: enabled, read cache: enabled, doesn't support DPO or FUA
  ...
  Jun  9 22:24:41 equipment 

[Kernel-packages] [Bug 1591293] Re: kernel fails to boot from SSD on non AHCI chipset (NCQ unsupported)

2016-06-14 Thread FerVira
** Tags added: kernel-bug-exists-upstream

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

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

Title:
  kernel fails to boot from SSD on non AHCI chipset (NCQ unsupported)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 64bits WON'T BOOT from a SSD Kinsgton Savage (2016) on chipset 
ASUS M2N68-AM SE (2010) with non-AHCI SATA2
  SATA Settings: 32 bit transfers: ENABLED,  AHCI mode: not available.
  Fresh installed system FREEZES inmediatly after starting to boot, PC looses 
its video signal.
  kern.log does not register anything.

  This motherboard does not support AHCI, but the SSD does.  Fresh
  installed 16.04 kernel does not disable NCQ (AHCI).

  Same system will slowly boot with errors when disabling 32 Bit transfers from 
BIOS, and freeze.
  Same PC boot ubuntustudio 12.04 live usb automatically disabling NCQ when SSD 
is connected.
  SAME SSD WILL BOOT without erros on chipset Intel Pinetrail-M with SATA3 and 
AHCI.
  (Same SSD and both PC boot fresh Windows 10 in sixteen seconds without any 
issue.)

  Expected behaviour:
  Kernel recognizes that AHCI is not supported by the hardware, and then 
disables NCQ because it requires AHCI,
  OR kernel recognizes that NCQ commands are failing and then disables NCQ,
  and by disabling NCQ the system can boot without any problem.

  Real behaviour:
  Kernel only disables NCQ when SSD drives are on a blacklist, but does not 
disable it when the chipset does not support AHCI (NCQ).  Kernel isn't 
disabling NCQ even when NCQ commands are failing.  This way system won't boot, 
or will boot but then freeze.

  It's not easy to understand why the system isn't booting. Many users
  are replacing their hard drives with SSD to improve the performance of
  their not-so-old PC, and if chipset does not support AHCI they will
  need to do expert diagnosis and tweaks to make ubuntu boot.

  Other tests:
  SATA Settings: 32 BIT TRANSFER: DISABLED, AHCI: not available.
  System boots from SSD with ATA errors and taking some minutes when it should 
take some seconds.
  Kernel DOES NOT disable NCQ after failing (it does on 12.04 live, same PC)
  System becomes definetly unresponsive a few minutes after start up, mouse 
pointer still moves but does not respond to clicks, and PC has to be hard reset.
  (In the posterior boot, system cleans some orphan inodes for one of the 
dm-crypt volumes)

  kern.log:

  Jun  9 22:24:41 equipment kernel: [0.00] Linux version 
4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 (Ubuntu 
5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 (Ubuntu 
4.4.0-21.37-generic 4.4.6)
  Jun  9 22:24:41 equipment kernel: [0.00] Command line: 
BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=UUID=88b24888-31fd-4a8e-98cd-f7e34b2bcc39 ro quiet splash
  
  Jun  9 22:24:41 equipment kernel: [0.00] DMI: System manufacturer 
System Product Name/M2N68-AM SE, BIOS 080407/26/2010
  ...
  Jun  9 22:24:41 equipment kernel: [2.073694] ata4.00: ATA-9: KINGSTON 
SHSS37A480G, SAFM00.U, max UDMA/133
  Jun  9 22:24:41 equipment kernel: [2.073697] ata4.00: 937703088 sectors, 
multi 16: LBA48 NCQ (depth 31/32)
  Jun  9 22:24:41 equipment kernel: [2.073777] ata4.00: configured for 
UDMA/133
  Jun  9 22:24:41 equipment kernel: [2.076892] ata3: SATA link down 
(SStatus 0 SControl 300)
  Jun  9 22:24:41 equipment kernel: [2.077116] scsi 3:0:0:0: Direct-Access  
   ATA  KINGSTON SHSS37A 00.U PQ: 0 ANSI: 5
  Jun  9 22:24:41 equipment kernel: [2.077421] sd 3:0:0:0: [sda] 937703088 
512-byte logical blocks: (480 GB/447 GiB)
  Jun  9 22:24:41 equipment kernel: [2.077494] sd 3:0:0:0: [sda] Write 
Protect is off
  Jun  9 22:24:41 equipment kernel: [2.077496] sd 3:0:0:0: [sda] Mode 
Sense: 00 3a 00 00
  Jun  9 22:24:41 equipment kernel: [2.077528] sd 3:0:0:0: [sda] Write 
cache: enabled, read cache: enabled, doesn't support DPO or FUA
  ...
  Jun  9 22:24:41 equipment kernel: [   33.997707] ata4.00: exception Emask 0x0 
SAct 0x7ff4000 SErr 0x0 action 0x6 frozen
  Jun  9 22:24:41 equipment kernel: [   33.997731] ata4.00: failed command: 
READ FPDMA QUEUED
  Jun  9 22:24:41 equipment kernel: [   33.997742] ata4.00: cmd 
60/08:70:f8:2f:80/00:00:11:00:00/40 tag 14 ncq 4096 in
  Jun  9 22:24:41 equipment kernel: [   33.997742]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  Jun  9 22:24:41 equipment kernel: [   33.997757] ata4.00: status: { DRDY }
  ... ( 1 time for each partition ) ...
  Jun  9 22:24:41 equipment kernel: [   33.998050] ata4.00: status: { DRDY }
  Jun  9 22:24:41 equipment kernel: [   33.998059] ata4: hard resetting link
  Jun  9 22:24:41 equipment kernel: [   34.317656] ata4: SATA link up 3.0 Gbps 
(SStatus 123 SControl 300)
  Jun  9 22:24:41 

[Kernel-packages] [Bug 1591436] Re: linux-armadaxp: 3.2.0-1668.93 -proposed tracker

2016-06-14 Thread Ike Panhc
** Tags added: qa-testing-passed

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

Title:
  linux-armadaxp: 3.2.0-1668.93 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-1668.93 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: 1591329
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1591790] Re: Resume from suspend, lock screen causes gpu hang

2016-06-14 Thread James Ferguson
Numerous suspend/resumes and no sign of the bug.  For reference, I never
had this problem on 14.04.

** Tags added: kernel-fixed-upstream

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

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

Title:
  Resume from suspend, lock screen causes gpu hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Frequently, returning from suspend, the lock screen 'crashes'.  I
  typically enter my password, it freezes (sometimes shows me my
  desktop) and then I get the lock screen again, presumably it's
  respawned.  My syslog shows a kernel stack trace and "drm/i915:
  Resetting chip after gpu hang"

  Just before reporting this it happened twice before I got past the lockscreen 
to my desktop
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-24-generic 4.4.0-24.43
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1988 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jun 12 20:58:31 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-21 (22 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2325KZ5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=72122534-7dd5-411b-9c56-c4844502e0ad ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA0WW (2.60 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325KZ5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 518896
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA0WW(2.60):bd03/05/2013:svnLENOVO:pn2325KZ5:pvrThinkPadX230:rvnLENOVO:rn2325KZ5:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325KZ5
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1591790] Re: Resume from suspend, lock screen causes gpu hang

2016-06-14 Thread James Ferguson
(to clarify - I meant no sign of this bug with the 4.7 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/1591790

Title:
  Resume from suspend, lock screen causes gpu hang

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Frequently, returning from suspend, the lock screen 'crashes'.  I
  typically enter my password, it freezes (sometimes shows me my
  desktop) and then I get the lock screen again, presumably it's
  respawned.  My syslog shows a kernel stack trace and "drm/i915:
  Resetting chip after gpu hang"

  Just before reporting this it happened twice before I got past the lockscreen 
to my desktop
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-24-generic 4.4.0-24.43
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1988 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jun 12 20:58:31 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-21 (22 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2325KZ5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=72122534-7dd5-411b-9c56-c4844502e0ad ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA0WW (2.60 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325KZ5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 518896
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA0WW(2.60):bd03/05/2013:svnLENOVO:pn2325KZ5:pvrThinkPadX230:rvnLENOVO:rn2325KZ5:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325KZ5
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1589889] Re: Bluetooth search gets nothing on Dell XPS 15 9550

2016-06-14 Thread Cruz Fernandez
After some digging, as suggested in 
http://ubuntuforums.org/showthread.php?t=2317843 says:
"""
Following https://bbs.archlinux.org/viewtopic.php?id=204739 I downloaded the 
missing firmware file (thanks @ZombieMeat) at Dropbox and copied it to 
/lib/firmware/brcm/
"""
Actually that worked. Attaching file that fixed it

** Attachment added: "bluetooth firmware for directory /lib/firmware/bcrm/"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1589889/+attachment/4683974/+files/BCM-0a5c-6410.hcd

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

Title:
  Bluetooth search gets nothing on Dell XPS 15 9550

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Title: Bluetooth search gets nothing on Dell XPS 15 9550

  Summary:
  Bluetooth search gets nothing on Dell XPS 15 9550

  Steps:
  1. Open Bluetooth Setting
  2. Click "+" to search nearby bluetooth devices

  Expected results: BT search could get nearby BT devices

  Actual results: Nothing shows from BT search

  Additional information:
  BT device:
  Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
  Couldn't open device, some information will be missing
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.00
    bDeviceClass  255 Vendor Specific Class
    bDeviceSubClass 1
    bDeviceProtocol 1
    bMaxPacketSize064
    idVendor   0x0a5c Broadcom Corp.
    idProduct  0x6410

  CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8x)

  GPU: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics
  530 (rev 06)

  Manufacturer: Dell

  ProductName: XPS 15 9550

  BiosVersion: 01.02.00

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

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


[Kernel-packages] [Bug 1592597] Re: 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630

2016-06-14 Thread Jill Rouleau
https://private-fileshare.canonical.com/~jillr/lp1592597/sosreport-
os-1-20160614233237.tar.xz

md5: c27d8c988ee155cf61532285866907d4

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

Title:
  3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Following recent update to 3.13.0-88, R630 on Trusty panics on boot.
  Recovery boot just hangs.  3.13.0-87 was able to be booted normally
  once, then kernel panics on subsequent attempts.  Booting is
  successful with the previously running kernel, 3.13.0-61.

  will upload an sosreport.

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

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


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

2016-06-14 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1592597

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

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

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

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

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

Title:
  3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Following recent update to 3.13.0-88, R630 on Trusty panics on boot.
  Recovery boot just hangs.  3.13.0-87 was able to be booted normally
  once, then kernel panics on subsequent attempts.  Booting is
  successful with the previously running kernel, 3.13.0-61.

  will upload an sosreport.

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

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


[Kernel-packages] [Bug 1592597] [NEW] 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630

2016-06-14 Thread Jill Rouleau
Public bug reported:

Following recent update to 3.13.0-88, R630 on Trusty panics on boot.
Recovery boot just hangs.  3.13.0-87 was able to be booted normally
once, then kernel panics on subsequent attempts.  Booting is successful
with the previously running kernel, 3.13.0-61.

will upload an sosreport.

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


** Tags: canonical-bootstack

** Attachment added: "consolescreenshots.tar.gz"
   
https://bugs.launchpad.net/bugs/1592597/+attachment/4683973/+files/consolescreenshots.tar.gz

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

Title:
  3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630

Status in linux package in Ubuntu:
  New

Bug description:
  Following recent update to 3.13.0-88, R630 on Trusty panics on boot.
  Recovery boot just hangs.  3.13.0-87 was able to be booted normally
  once, then kernel panics on subsequent attempts.  Booting is
  successful with the previously running kernel, 3.13.0-61.

  will upload an sosreport.

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

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


[Kernel-packages] [Bug 1581866] Re: CVE-2016-4578

2016-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-snapdragon - 4.4.0-1016.19

---
linux-snapdragon (4.4.0-1016.19) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1591462

  [ Ubuntu: 4.4.0-25.44 ]

  * Xenial update to v4.4.13 stable release (LP: #1590455)
- MIPS64: R6: R2 emulation bugfix
- MIPS: math-emu: Fix jalr emulation when rd == $0
- MIPS: MSA: Fix a link error on `_init_msa_upper' with older GCC
- MIPS: Don't unwind to user mode with EVA
- MIPS: Avoid using unwind_stack() with usermode
- MIPS: Fix siginfo.h to use strict posix types
- MIPS: Fix uapi include in exported asm/siginfo.h
- MIPS: Fix watchpoint restoration
- MIPS: Flush highmem pages in __flush_dcache_page
- MIPS: Handle highmem pages in __update_cache
- MIPS: Sync icache & dcache in set_pte_at
- MIPS: ath79: make bootconsole wait for both THRE and TEMT
- MIPS: Reserve nosave data for hibernation
- MIPS: Loongson-3: Reserve 32MB for RS780E integrated GPU
- MIPS: Use copy_s.fmt rather than copy_u.fmt
- MIPS: Fix MSA ld_*/st_* asm macros to use PTR_ADDU
- MIPS: Prevent "restoration" of MSA context in non-MSA kernels
- MIPS: Disable preemption during prctl(PR_SET_FP_MODE, ...)
- MIPS: ptrace: Fix FP context restoration FCSR regression
- MIPS: ptrace: Prevent writes to read-only FCSR bits
- MIPS: Fix sigreturn via VDSO on microMIPS kernel
- MIPS: Build microMIPS VDSO for microMIPS kernels
- MIPS: lib: Mark intrinsics notrace
- MIPS: VDSO: Build with `-fno-strict-aliasing'
- affs: fix remount failure when there are no options changed
- ASoC: ak4642: Enable cache usage to fix crashes on resume
- Input: uinput - handle compat ioctl for UI_SET_PHYS
- ARM: mvebu: fix GPIO config on the Linksys boards
- ARM: dts: at91: fix typo in sama5d2 PIN_PD24 description
- ARM: dts: exynos: Add interrupt line to MAX8997 PMIC on exynos4210-trats
- ARM: dts: imx35: restore existing used clock enumeration
- ath9k: Add a module parameter to invert LED polarity.
- ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- ath10k: fix debugfs pktlog_filter write
- ath10k: fix firmware assert in monitor mode
- ath10k: fix rx_channel during hw reconfigure
- ath10k: fix kernel panic, move arvifs list head init before htt init
- ath5k: Change led pin configuration for compaq c700 laptop
- hwrng: exynos - Fix unbalanced PM runtime put on timeout error path
- rtlwifi: rtl8723be: Add antenna select module parameter
- rtlwifi: btcoexist: Implement antenna selection
- rtlwifi: Fix logic error in enter/exit power-save mode
- rtlwifi: pci: use dev_kfree_skb_irq instead of kfree_skb in
  rtl_pci_reset_trx_ring
- aacraid: Relinquish CPU during timeout wait
- aacraid: Fix for aac_command_thread hang
- aacraid: Fix for KDUMP driver hang
- hwmon: (ads7828) Enable internal reference
- mfd: intel-lpss: Save register context on suspend
- mfd: intel_soc_pmic_core: Terminate panel control GPIO lookup table
  correctly
- PM / Runtime: Fix error path in pm_runtime_force_resume()
- cpuidle: Indicate when a device has been unregistered
- cpuidle: Fix cpuidle_state_is_coupled() argument in cpuidle_enter()
- clk: bcm2835: Fix PLL poweron
- clk: at91: fix check of clk_register() returned value
- clk: bcm2835: pll_off should only update CM_PLL_ANARST
- clk: bcm2835: divider value has to be 1 or more
- pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- PCI: Disable all BAR sizing for devices with non-compliant BARs
- media: v4l2-compat-ioctl32: fix missing reserved field copy in
  put_v4l2_create32
- mm: use phys_addr_t for reserve_bootmem_region() arguments
- wait/ptrace: assume __WALL if the child is traced
- QE-UART: add "fsl,t1040-ucc-uart" to of_device_id
- powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- powerpc/eeh: Don't report error in eeh_pe_reset_and_recover()
- powerpc/eeh: Restore initial state in eeh_pe_reset_and_recover()
- xen/events: Don't move disabled irqs
- xen: use same main loop for counting and remapping pages
- sunrpc: fix stripping of padded MIC tokens
- drm/gma500: Fix possible out of bounds read
- drm/vmwgfx: Enable SVGA_3D_CMD_DX_SET_PREDICATION
- drm/vmwgfx: use vmw_cmd_dx_cid_check for query commands.
- drm/vmwgfx: Fix order of operation
- drm/amdgpu: use drm_mode_vrefresh() rather than mode->vrefresh
- drm/amdgpu: Fix hdmi deep color support.
- drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config()
- drm/fb_helper: Fix references to dev->mode_config.num_connector
- drm/atomic: Verify connector->funcs != NULL when clearing states
- drm/i915: Don't leave old junk in ilk active watermarks on readout
- drm/imx: Match imx-ipuv3-crtc components using 

[Kernel-packages] [Bug 1580379] Re: CVE-2016-4569

2016-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-snapdragon - 4.4.0-1016.19

---
linux-snapdragon (4.4.0-1016.19) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1591462

  [ Ubuntu: 4.4.0-25.44 ]

  * Xenial update to v4.4.13 stable release (LP: #1590455)
- MIPS64: R6: R2 emulation bugfix
- MIPS: math-emu: Fix jalr emulation when rd == $0
- MIPS: MSA: Fix a link error on `_init_msa_upper' with older GCC
- MIPS: Don't unwind to user mode with EVA
- MIPS: Avoid using unwind_stack() with usermode
- MIPS: Fix siginfo.h to use strict posix types
- MIPS: Fix uapi include in exported asm/siginfo.h
- MIPS: Fix watchpoint restoration
- MIPS: Flush highmem pages in __flush_dcache_page
- MIPS: Handle highmem pages in __update_cache
- MIPS: Sync icache & dcache in set_pte_at
- MIPS: ath79: make bootconsole wait for both THRE and TEMT
- MIPS: Reserve nosave data for hibernation
- MIPS: Loongson-3: Reserve 32MB for RS780E integrated GPU
- MIPS: Use copy_s.fmt rather than copy_u.fmt
- MIPS: Fix MSA ld_*/st_* asm macros to use PTR_ADDU
- MIPS: Prevent "restoration" of MSA context in non-MSA kernels
- MIPS: Disable preemption during prctl(PR_SET_FP_MODE, ...)
- MIPS: ptrace: Fix FP context restoration FCSR regression
- MIPS: ptrace: Prevent writes to read-only FCSR bits
- MIPS: Fix sigreturn via VDSO on microMIPS kernel
- MIPS: Build microMIPS VDSO for microMIPS kernels
- MIPS: lib: Mark intrinsics notrace
- MIPS: VDSO: Build with `-fno-strict-aliasing'
- affs: fix remount failure when there are no options changed
- ASoC: ak4642: Enable cache usage to fix crashes on resume
- Input: uinput - handle compat ioctl for UI_SET_PHYS
- ARM: mvebu: fix GPIO config on the Linksys boards
- ARM: dts: at91: fix typo in sama5d2 PIN_PD24 description
- ARM: dts: exynos: Add interrupt line to MAX8997 PMIC on exynos4210-trats
- ARM: dts: imx35: restore existing used clock enumeration
- ath9k: Add a module parameter to invert LED polarity.
- ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- ath10k: fix debugfs pktlog_filter write
- ath10k: fix firmware assert in monitor mode
- ath10k: fix rx_channel during hw reconfigure
- ath10k: fix kernel panic, move arvifs list head init before htt init
- ath5k: Change led pin configuration for compaq c700 laptop
- hwrng: exynos - Fix unbalanced PM runtime put on timeout error path
- rtlwifi: rtl8723be: Add antenna select module parameter
- rtlwifi: btcoexist: Implement antenna selection
- rtlwifi: Fix logic error in enter/exit power-save mode
- rtlwifi: pci: use dev_kfree_skb_irq instead of kfree_skb in
  rtl_pci_reset_trx_ring
- aacraid: Relinquish CPU during timeout wait
- aacraid: Fix for aac_command_thread hang
- aacraid: Fix for KDUMP driver hang
- hwmon: (ads7828) Enable internal reference
- mfd: intel-lpss: Save register context on suspend
- mfd: intel_soc_pmic_core: Terminate panel control GPIO lookup table
  correctly
- PM / Runtime: Fix error path in pm_runtime_force_resume()
- cpuidle: Indicate when a device has been unregistered
- cpuidle: Fix cpuidle_state_is_coupled() argument in cpuidle_enter()
- clk: bcm2835: Fix PLL poweron
- clk: at91: fix check of clk_register() returned value
- clk: bcm2835: pll_off should only update CM_PLL_ANARST
- clk: bcm2835: divider value has to be 1 or more
- pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- PCI: Disable all BAR sizing for devices with non-compliant BARs
- media: v4l2-compat-ioctl32: fix missing reserved field copy in
  put_v4l2_create32
- mm: use phys_addr_t for reserve_bootmem_region() arguments
- wait/ptrace: assume __WALL if the child is traced
- QE-UART: add "fsl,t1040-ucc-uart" to of_device_id
- powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- powerpc/eeh: Don't report error in eeh_pe_reset_and_recover()
- powerpc/eeh: Restore initial state in eeh_pe_reset_and_recover()
- xen/events: Don't move disabled irqs
- xen: use same main loop for counting and remapping pages
- sunrpc: fix stripping of padded MIC tokens
- drm/gma500: Fix possible out of bounds read
- drm/vmwgfx: Enable SVGA_3D_CMD_DX_SET_PREDICATION
- drm/vmwgfx: use vmw_cmd_dx_cid_check for query commands.
- drm/vmwgfx: Fix order of operation
- drm/amdgpu: use drm_mode_vrefresh() rather than mode->vrefresh
- drm/amdgpu: Fix hdmi deep color support.
- drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config()
- drm/fb_helper: Fix references to dev->mode_config.num_connector
- drm/atomic: Verify connector->funcs != NULL when clearing states
- drm/i915: Don't leave old junk in ilk active watermarks on readout
- drm/imx: Match imx-ipuv3-crtc components using 

[Kernel-packages] [Bug 1578493] Re: CVE-2016-4482

2016-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-snapdragon - 4.4.0-1016.19

---
linux-snapdragon (4.4.0-1016.19) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1591462

  [ Ubuntu: 4.4.0-25.44 ]

  * Xenial update to v4.4.13 stable release (LP: #1590455)
- MIPS64: R6: R2 emulation bugfix
- MIPS: math-emu: Fix jalr emulation when rd == $0
- MIPS: MSA: Fix a link error on `_init_msa_upper' with older GCC
- MIPS: Don't unwind to user mode with EVA
- MIPS: Avoid using unwind_stack() with usermode
- MIPS: Fix siginfo.h to use strict posix types
- MIPS: Fix uapi include in exported asm/siginfo.h
- MIPS: Fix watchpoint restoration
- MIPS: Flush highmem pages in __flush_dcache_page
- MIPS: Handle highmem pages in __update_cache
- MIPS: Sync icache & dcache in set_pte_at
- MIPS: ath79: make bootconsole wait for both THRE and TEMT
- MIPS: Reserve nosave data for hibernation
- MIPS: Loongson-3: Reserve 32MB for RS780E integrated GPU
- MIPS: Use copy_s.fmt rather than copy_u.fmt
- MIPS: Fix MSA ld_*/st_* asm macros to use PTR_ADDU
- MIPS: Prevent "restoration" of MSA context in non-MSA kernels
- MIPS: Disable preemption during prctl(PR_SET_FP_MODE, ...)
- MIPS: ptrace: Fix FP context restoration FCSR regression
- MIPS: ptrace: Prevent writes to read-only FCSR bits
- MIPS: Fix sigreturn via VDSO on microMIPS kernel
- MIPS: Build microMIPS VDSO for microMIPS kernels
- MIPS: lib: Mark intrinsics notrace
- MIPS: VDSO: Build with `-fno-strict-aliasing'
- affs: fix remount failure when there are no options changed
- ASoC: ak4642: Enable cache usage to fix crashes on resume
- Input: uinput - handle compat ioctl for UI_SET_PHYS
- ARM: mvebu: fix GPIO config on the Linksys boards
- ARM: dts: at91: fix typo in sama5d2 PIN_PD24 description
- ARM: dts: exynos: Add interrupt line to MAX8997 PMIC on exynos4210-trats
- ARM: dts: imx35: restore existing used clock enumeration
- ath9k: Add a module parameter to invert LED polarity.
- ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- ath10k: fix debugfs pktlog_filter write
- ath10k: fix firmware assert in monitor mode
- ath10k: fix rx_channel during hw reconfigure
- ath10k: fix kernel panic, move arvifs list head init before htt init
- ath5k: Change led pin configuration for compaq c700 laptop
- hwrng: exynos - Fix unbalanced PM runtime put on timeout error path
- rtlwifi: rtl8723be: Add antenna select module parameter
- rtlwifi: btcoexist: Implement antenna selection
- rtlwifi: Fix logic error in enter/exit power-save mode
- rtlwifi: pci: use dev_kfree_skb_irq instead of kfree_skb in
  rtl_pci_reset_trx_ring
- aacraid: Relinquish CPU during timeout wait
- aacraid: Fix for aac_command_thread hang
- aacraid: Fix for KDUMP driver hang
- hwmon: (ads7828) Enable internal reference
- mfd: intel-lpss: Save register context on suspend
- mfd: intel_soc_pmic_core: Terminate panel control GPIO lookup table
  correctly
- PM / Runtime: Fix error path in pm_runtime_force_resume()
- cpuidle: Indicate when a device has been unregistered
- cpuidle: Fix cpuidle_state_is_coupled() argument in cpuidle_enter()
- clk: bcm2835: Fix PLL poweron
- clk: at91: fix check of clk_register() returned value
- clk: bcm2835: pll_off should only update CM_PLL_ANARST
- clk: bcm2835: divider value has to be 1 or more
- pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- PCI: Disable all BAR sizing for devices with non-compliant BARs
- media: v4l2-compat-ioctl32: fix missing reserved field copy in
  put_v4l2_create32
- mm: use phys_addr_t for reserve_bootmem_region() arguments
- wait/ptrace: assume __WALL if the child is traced
- QE-UART: add "fsl,t1040-ucc-uart" to of_device_id
- powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- powerpc/eeh: Don't report error in eeh_pe_reset_and_recover()
- powerpc/eeh: Restore initial state in eeh_pe_reset_and_recover()
- xen/events: Don't move disabled irqs
- xen: use same main loop for counting and remapping pages
- sunrpc: fix stripping of padded MIC tokens
- drm/gma500: Fix possible out of bounds read
- drm/vmwgfx: Enable SVGA_3D_CMD_DX_SET_PREDICATION
- drm/vmwgfx: use vmw_cmd_dx_cid_check for query commands.
- drm/vmwgfx: Fix order of operation
- drm/amdgpu: use drm_mode_vrefresh() rather than mode->vrefresh
- drm/amdgpu: Fix hdmi deep color support.
- drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config()
- drm/fb_helper: Fix references to dev->mode_config.num_connector
- drm/atomic: Verify connector->funcs != NULL when clearing states
- drm/i915: Don't leave old junk in ilk active watermarks on readout
- drm/imx: Match imx-ipuv3-crtc components using 

[Kernel-packages] [Bug 1585365] Re: CVE-2016-4951

2016-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-snapdragon - 4.4.0-1016.19

---
linux-snapdragon (4.4.0-1016.19) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1591462

  [ Ubuntu: 4.4.0-25.44 ]

  * Xenial update to v4.4.13 stable release (LP: #1590455)
- MIPS64: R6: R2 emulation bugfix
- MIPS: math-emu: Fix jalr emulation when rd == $0
- MIPS: MSA: Fix a link error on `_init_msa_upper' with older GCC
- MIPS: Don't unwind to user mode with EVA
- MIPS: Avoid using unwind_stack() with usermode
- MIPS: Fix siginfo.h to use strict posix types
- MIPS: Fix uapi include in exported asm/siginfo.h
- MIPS: Fix watchpoint restoration
- MIPS: Flush highmem pages in __flush_dcache_page
- MIPS: Handle highmem pages in __update_cache
- MIPS: Sync icache & dcache in set_pte_at
- MIPS: ath79: make bootconsole wait for both THRE and TEMT
- MIPS: Reserve nosave data for hibernation
- MIPS: Loongson-3: Reserve 32MB for RS780E integrated GPU
- MIPS: Use copy_s.fmt rather than copy_u.fmt
- MIPS: Fix MSA ld_*/st_* asm macros to use PTR_ADDU
- MIPS: Prevent "restoration" of MSA context in non-MSA kernels
- MIPS: Disable preemption during prctl(PR_SET_FP_MODE, ...)
- MIPS: ptrace: Fix FP context restoration FCSR regression
- MIPS: ptrace: Prevent writes to read-only FCSR bits
- MIPS: Fix sigreturn via VDSO on microMIPS kernel
- MIPS: Build microMIPS VDSO for microMIPS kernels
- MIPS: lib: Mark intrinsics notrace
- MIPS: VDSO: Build with `-fno-strict-aliasing'
- affs: fix remount failure when there are no options changed
- ASoC: ak4642: Enable cache usage to fix crashes on resume
- Input: uinput - handle compat ioctl for UI_SET_PHYS
- ARM: mvebu: fix GPIO config on the Linksys boards
- ARM: dts: at91: fix typo in sama5d2 PIN_PD24 description
- ARM: dts: exynos: Add interrupt line to MAX8997 PMIC on exynos4210-trats
- ARM: dts: imx35: restore existing used clock enumeration
- ath9k: Add a module parameter to invert LED polarity.
- ath9k: Fix LED polarity for some Mini PCI AR9220 MB92 cards.
- ath10k: fix debugfs pktlog_filter write
- ath10k: fix firmware assert in monitor mode
- ath10k: fix rx_channel during hw reconfigure
- ath10k: fix kernel panic, move arvifs list head init before htt init
- ath5k: Change led pin configuration for compaq c700 laptop
- hwrng: exynos - Fix unbalanced PM runtime put on timeout error path
- rtlwifi: rtl8723be: Add antenna select module parameter
- rtlwifi: btcoexist: Implement antenna selection
- rtlwifi: Fix logic error in enter/exit power-save mode
- rtlwifi: pci: use dev_kfree_skb_irq instead of kfree_skb in
  rtl_pci_reset_trx_ring
- aacraid: Relinquish CPU during timeout wait
- aacraid: Fix for aac_command_thread hang
- aacraid: Fix for KDUMP driver hang
- hwmon: (ads7828) Enable internal reference
- mfd: intel-lpss: Save register context on suspend
- mfd: intel_soc_pmic_core: Terminate panel control GPIO lookup table
  correctly
- PM / Runtime: Fix error path in pm_runtime_force_resume()
- cpuidle: Indicate when a device has been unregistered
- cpuidle: Fix cpuidle_state_is_coupled() argument in cpuidle_enter()
- clk: bcm2835: Fix PLL poweron
- clk: at91: fix check of clk_register() returned value
- clk: bcm2835: pll_off should only update CM_PLL_ANARST
- clk: bcm2835: divider value has to be 1 or more
- pinctrl: exynos5440: Use off-stack memory for pinctrl_gpio_range
- PCI: Disable all BAR sizing for devices with non-compliant BARs
- media: v4l2-compat-ioctl32: fix missing reserved field copy in
  put_v4l2_create32
- mm: use phys_addr_t for reserve_bootmem_region() arguments
- wait/ptrace: assume __WALL if the child is traced
- QE-UART: add "fsl,t1040-ucc-uart" to of_device_id
- powerpc/book3s64: Fix branching to OOL handlers in relocatable kernel
- powerpc/eeh: Don't report error in eeh_pe_reset_and_recover()
- powerpc/eeh: Restore initial state in eeh_pe_reset_and_recover()
- xen/events: Don't move disabled irqs
- xen: use same main loop for counting and remapping pages
- sunrpc: fix stripping of padded MIC tokens
- drm/gma500: Fix possible out of bounds read
- drm/vmwgfx: Enable SVGA_3D_CMD_DX_SET_PREDICATION
- drm/vmwgfx: use vmw_cmd_dx_cid_check for query commands.
- drm/vmwgfx: Fix order of operation
- drm/amdgpu: use drm_mode_vrefresh() rather than mode->vrefresh
- drm/amdgpu: Fix hdmi deep color support.
- drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config()
- drm/fb_helper: Fix references to dev->mode_config.num_connector
- drm/atomic: Verify connector->funcs != NULL when clearing states
- drm/i915: Don't leave old junk in ilk active watermarks on readout
- drm/imx: Match imx-ipuv3-crtc components using 

[Kernel-packages] [Bug 1590069] Re: vDSO syscalls don't work on yakkety/master-next (and unstable/master)

2016-06-14 Thread Tycho Andersen
Hi Tim,

I just tested this in a fresh yakkety VM using the daily cloud images
and the kernel team PPA you mentioned and reproduced it with your
program:

ubuntu@yakkety:~$ strace ./tester
execve("./tester", ["./tester"], [/* 17 vars */]) = 0
brk(NULL)   = 0x55dbbabdf000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f444ba48000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=23765, ...}) = 0
mmap(NULL, 23765, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f444ba42000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0
mmap(NULL, 3967488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f444b45c000
mprotect(0x7f444b61c000, 2093056, PROT_NONE) = 0
mmap(0x7f444b81b000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bf000) = 0x7f444b81b000
mmap(0x7f444b821000, 14848, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f444b821000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f444ba41000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f444ba4
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f444ba3f000
arch_prctl(ARCH_SET_FS, 0x7f444ba40700) = 0
mprotect(0x7f444b81b000, 16384, PROT_READ) = 0
mprotect(0x55dbb9616000, 4096, PROT_READ) = 0
mprotect(0x7f444ba4a000, 4096, PROT_READ) = 0
munmap(0x7f444ba42000, 23765)   = 0
nanosleep({1, 0}, 0x7ffd91f7c6c0)   = 0
gettimeofday({1465946468, 561043}, {tz_minuteswest=0, tz_dsttime=0}) = 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(4, 64), ...}) = 0
ioctl(1, TCGETS, {B9600 opost isig icanon echo ...}) = 0
brk(NULL)   = 0x55dbbabdf000
brk(0x55dbbac01000) = 0x55dbbac01000
write(1, "sec 1465946468\n", 15sec 1465946468
)= 15
nanosleep({1, 0}, 0x7ffd91f7c6c0)   = 0
gettimeofday({1465946469, 567377}, {tz_minuteswest=0, tz_dsttime=0}) = 0
write(1, "sec 1465946469\n", 15sec 1465946469
)= 15
nanosleep({1, 0}, 0x7ffd91f7c6c0)   = 0
gettimeofday({1465946470, 570615}, {tz_minuteswest=0, tz_dsttime=0}) = 0
write(1, "sec 1465946470\n", 15sec 1465946470
)= 15
nanosleep({1, 0}, 0x7ffd91f7c6c0)   = 0
gettimeofday({1465946471, 574084}, {tz_minuteswest=0, tz_dsttime=0}) = 0
write(1, "sec 1465946471\n", 15sec 1465946471
)= 15
nanosleep({1, 0}, 0x7ffd91f7c6c0)   = 0
gettimeofday({1465946472, 576646}, {tz_minuteswest=0, tz_dsttime=0}) = 0
write(1, "sec 1465946472\n", 15sec 1465946472
)= 15
nanosleep({1, 0}, ^Cstrace: Process 1490 detached
 
ubuntu@yakkety:~$ uname -a
Linux yakkety 4.6.0-7-generic #8-Ubuntu SMP Fri Jun 3 15:08:18 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux
ubuntu@yakkety:~$ apt-cache showpkg linux-image-4.6.0-7-generic 
Package: linux-image-4.6.0-7-generic
Versions: 
4.6.0-7.8 
(/var/lib/apt/lists/ppa.launchpad.net_canonical-kernel-team_ppa_ubuntu_dists_yakkety_main_binary-amd64_Packages)
 (/var/lib/dpkg/status)
 Description Language: 
 File: 
/var/lib/apt/lists/ppa.launchpad.net_canonical-kernel-team_ppa_ubuntu_dists_yakkety_main_binary-amd64_Packages
  MD5: eb70ad30d136e11219815e66f14ab797
 Description Language: en
 File: 
/var/lib/apt/lists/ppa.launchpad.net_canonical-kernel-team_ppa_ubuntu_dists_yakkety_main_i18n_Translation-en
  MD5: eb70ad30d136e11219815e66f14ab797


Reverse Depends: 
  linux-image-generic,linux-image-4.6.0-7-generic
  linux-image-extra-4.6.0-7-generic,linux-image-4.6.0-7-generic
  linux-image-virtual,linux-image-4.6.0-7-generic
Dependencies: 
4.6.0-7.8 - initramfs-tools (16 (null)) linux-initramfs-tool (0 (null)) kmod (0 
(null)) grub-pc (16 (null)) grub-efi-amd64 (16 (null)) grub-efi-ia32 (16 
(null)) grub (16 (null)) lilo (0 (null)) fdutils (0 (null)) linux-doc-4.6.0 (16 
(null)) linux-source-4.6.0 (0 (null)) linux-tools (0 (null)) 
linux-headers-4.6.0-7-generic (0 (null)) 
Provides: 
4.6.0-7.8 - zfs-dkms (= ) virtualbox-guest-modules (= ) spl-dkms (= ) 
redhat-cluster-modules (= ) linux-image (= ) kvm-api-4 (= ) ivtv-modules (= ) 
fuse-module (= ) 
Reverse Provides: 
ubuntu@yakkety:~$ 

Here the kernel has a 4.6.0-7 version number, not a 4.6.0-7.8 as you
mentioned. Where do I get 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/1590069


[Kernel-packages] [Bug 1591703] Re: bluetoothd crashed with SIGSEGV in __GI__IO_wsetb()

2016-06-14 Thread ernsteiswuerfel
** Information type changed from Private to Public

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

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

Title:
  bluetoothd crashed with SIGSEGV in __GI__IO_wsetb()

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Bluetooth crashinfo displayed shortly after login. This happens
  repeatedly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-powerpc-smp 4.4.8
  Uname: Linux 4.4.0-22-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  Date: Sat Jun 11 11:26:29 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-09-16 (269 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha powerpc 
(20150827)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 05ac:0215 Apple, Inc. Internal Keyboard/Trackpad (ISO)
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 003: ID 05ac:8207 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
   LANG=de_AT.UTF-8
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
  ProcKernelCmdLine: root=UUID=e7580396-741d-4923-8a8a-50db1b938df3 ro 
rootflags=subvol=@ quiet splash
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   __GI__IO_wsetb (f=f@entry=0x204b7ca0 <_IO_stdout_>, b=b@entry=0x0, 
eb=eb@entry=0x0, a=a@entry=0) at wgenops.c:105
   _IO_unbuffer_all () at genops.c:918
   _IO_cleanup () at genops.c:960
   __run_exit_handlers (status=0, listp=, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:95
   __GI_exit (status=) at exit.c:104
  Title: bluetoothd crashed with SIGSEGV in __GI__IO_wsetb()
  UpgradeStatus: Upgraded to xenial on 2016-05-08 (35 days ago)
  UserGroups:
   
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:14:51:95:FF:B4  ACL MTU: 384:8  SCO MTU: 64:8
UP RUNNING 
RX bytes:534 acl:0 sco:0 events:27 errors:0
TX bytes:612 acl:0 sco:0 commands:26 errors:0

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

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


[Kernel-packages] [Bug 1579481] Re: 16.04 -> External Monitor not working -> radeon VCE init error (-110)

2016-06-14 Thread R. Becke
Hi Chirstopher,
Actually I don't think the issue is related to the BIOS of my laptop but rather 
to the firmware of my 
"HP 2013 UltraSlim-Dockingstation". Therefore I tried the following firmware 
upgrade:
http://h20564.www2.hp.com/hpsc/swd/public/detail?swItemId=ob_147496_1#tab-history
BUT I tried in Windows 8.1 and Windows 10 and just could not get it working 
i.e. the docking station did not produce any video output on the two DVI Ports 
neither on the VGA Port and the firmware upgrade could not get installed. At 
least the DVI Port of the Laptop is working which is for now fine for me.

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

Title:
  16.04 -> External Monitor not working -> radeon VCE init error (-110)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since I've upgraded 15.10 to 16.04 my external monitor is not working 
anymore. Whether I plug it directly into the DVI port of my laptop ("HP 
EliteBook 840 G1") or whether I plug it into the DVI or VGA port of my docking 
station "HP 2013 UltraSlim-Dockingstation" I get the following error in 
"/var/log/syslog":
  ...
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.377223] radeon 
:03:00.0: VCE init error (-110).
  May  4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [   64.811603] 
[drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery reached max voltage
  May  4 19:20:18 hp-elitebook-840-g1--s0-v2 kernel: [   64.811619] 
[drm:radeon_dp_link_train [radeon]] *ERROR* clock recovery failed
  ...

  I tried as well a fresh 16.04 install but this still did not help.
  The full log related to plugging in an external monitor is:
  ...
  May  4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [   62.573716] i915 
:00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
  May  4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [   62.578032] i915 
:00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
  May  4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [   62.578106] acpi 
PNP0501:00: Still not present
  May  4 19:20:16 hp-elitebook-840-g1--s0-v2 kernel: [   62.578184] i915 
:00:02.0: BAR 6: [??? 0x flags 0x2] has bogus alignment
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.267945] [drm] 
probing gen 2 caps for device 8086:9c18 = 5323c42/0
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.267950] [drm] PCIE 
gen 2 link speeds already enabled
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.275081] [drm] PCIE 
GART of 2048M enabled (table at 0x002E8000).
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.275187] radeon 
:03:00.0: WB enabled
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.275190] radeon 
:03:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu 
addr 0x880434a83c00
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.275191] radeon 
:03:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu 
addr 0x880434a83c04
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.275192] radeon 
:03:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu 
addr 0x880434a83c08
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.275194] radeon 
:03:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu 
addr 0x880434a83c0c
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.275195] radeon 
:03:00.0: fence driver on ring 4 use gpu addr 0x4c10 and cpu 
addr 0x880434a83c10
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.276738] radeon 
:03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu 
addr 0xc90002835a18
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.377223] radeon 
:03:00.0: VCE init error (-110).
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.612628] [drm] ring 
test on 0 succeeded in 1 usecs
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.612635] [drm] ring 
test on 1 succeeded in 1 usecs
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.612640] [drm] ring 
test on 2 succeeded in 1 usecs
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.612650] [drm] ring 
test on 3 succeeded in 5 usecs
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.612658] [drm] ring 
test on 4 succeeded in 5 usecs
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.788345] [drm] ring 
test on 5 succeeded in 2 usecs
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.788352] [drm] UVD 
initialized successfully.
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.788388] [drm] ib 
test on ring 0 succeeded in 0 usecs
  May  4 19:20:17 hp-elitebook-840-g1--s0-v2 kernel: [   63.788421] [drm] ib 
test on ring 1 succeeded in 0 usecs
  May  4 19:20:17 

[Kernel-packages] [Bug 1589889] Re: Bluetooth search gets nothing on Dell XPS 15 9550

2016-06-14 Thread Cruz Fernandez
Maybe related with
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1590798 ?

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

Title:
  Bluetooth search gets nothing on Dell XPS 15 9550

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Title: Bluetooth search gets nothing on Dell XPS 15 9550

  Summary:
  Bluetooth search gets nothing on Dell XPS 15 9550

  Steps:
  1. Open Bluetooth Setting
  2. Click "+" to search nearby bluetooth devices

  Expected results: BT search could get nearby BT devices

  Actual results: Nothing shows from BT search

  Additional information:
  BT device:
  Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
  Couldn't open device, some information will be missing
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.00
    bDeviceClass  255 Vendor Specific Class
    bDeviceSubClass 1
    bDeviceProtocol 1
    bMaxPacketSize064
    idVendor   0x0a5c Broadcom Corp.
    idProduct  0x6410

  CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8x)

  GPU: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics
  530 (rev 06)

  Manufacturer: Dell

  ProductName: XPS 15 9550

  BiosVersion: 01.02.00

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

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


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

2016-06-14 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  can't write to a BTRFS disk with my powermac

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  When I try to write to my BTRFS formated external disk, I get an error 
message explaining the file system is mounted read only. Indeed, I can still 
read data in it.

  A dmesg shows the following errors:

  [  143.354977] usb 1-2: new high-speed USB device number 4 using ehci-pci
  [  143.564941] usb 1-2: New USB device found, idVendor=04e8, idProduct=61b5
  [  143.564955] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  143.564963] usb 1-2: Product: Samsung M3 Portable
  [  143.564971] usb 1-2: Manufacturer: Samsung M3 Portable
  [  143.564978] usb 1-2: SerialNumber: D93E7DFA199A
  [  143.668941] usbcore: registered new interface driver usb-storage
  [  143.694409] scsi host5: uas
  [  143.694601] usbcore: registered new interface driver uas
  [  143.696560] scsi 5:0:0:0: Direct-Access Samsung  M3 Portable  1402 
PQ: 0 ANSI: 6
  [  143.698592] sd 5:0:0:0: Attached scsi generic sg3 type 0
  [  147.091177] sd 5:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 
TB/1.82 TiB)
  [  147.091194] sd 5:0:0:0: [sdc] 4096-byte physical blocks
  [  147.092774] sd 5:0:0:0: [sdc] Write Protect is off
  [  147.092785] sd 5:0:0:0: [sdc] Mode Sense: 53 00 00 08
  [  147.093629] sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
  [  147.109068]  sdc: sdc1
  [  147.113161] sd 5:0:0:0: [sdc] Attached SCSI disk
  [  147.744379] BTRFS: device fsid bf584dbe-6bf6-4847-8b32-cb0d22bead69 devid 
1 transid 17546 /dev/sdc1
  [  148.044853] BTRFS info (device sdc1): disk space caching is enabled
  [  148.044867] BTRFS: has skinny extents
  [  181.329491] BTRFS: Transaction aborted (error -17)
  [  181.329573] [ cut here ]
  [  181.329577] WARNING: at 
/build/linux-t3xCGW/linux-4.4.0/fs/btrfs/extent-tree.c:2927
  [  181.329580] Modules linked in: uas usb_storage drbg ansi_cprng ctr ccm 
arc4 zd1211rw mac80211 cfg80211 input_leds mac_hid snd_aoa_codec_onyx snd_aoa 
snd_seq_midi snd_seq_midi_event rtc_generic snd_rawmidi snd_seq snd_seq_device 
snd_timer snd soundcore shpchp uio_pdrv_genirq uio parport_pc ppdev lp parport 
autofs4 btrfs xor raid6_pq windfarm_cpufreq_clamp windfarm_smu_sensors 
windfarm_smu_controls windfarm_pm112 windfarm_pid sil164 hid_generic nouveau 
windfarm_lm75_sensor windfarm_max6690_sensor i2c_algo_bit firewire_ohci 
windfarm_smu_sat windfarm_core firewire_core ttm crc_itu_t drm_kms_helper 
usbhid ata_generic hid drm tg3 ptp uninorth_agp pps_core
  [  181.329658] CPU: 0 PID: 1490 Comm: btrfs-transacti Not tainted 
4.4.0-24-powerpc64-smp #43-Ubuntu
  [  181.329663] task: c0007a633db0 ti: c0007d2c task.ti: 
c0007d2c
  [  181.329666] NIP: d1d99274 LR: d1d99270 CTR: 

  [  181.329670] REGS: c0007d2c3690 TRAP: 0700   Not tainted  
(4.4.0-24-powerpc64-smp)
  [  181.329672] MSR: 90029032   CR: 24f72442  
XER: 2000
  [  181.329683] SOFTE: 1 
 GPR00: d1d99270 c0007d2c3910 d1e8f2d0 
0026 
 GPR04: c0025de09ad0 c0025de0c360 0036 
02ab 
 GPR08: 0007 c10150fc 00025cdf6000 
0018 
 GPR12: 48f72444 cfdc c00f9f40 
c0007d082b80 
 GPR16:    
 
 GPR20: c0007de65800 0001  
c0007b765090 
 GPR24: c0007b784170 c0007b784160  
c0007b784000 
 GPR28: c0007de65800 c0007b765000 c0024e12bc00 
ffef 
  [  181.329801] NIP [d1d99274] .btrfs_run_delayed_refs+0x364/0x3a0 
[btrfs]
  [  181.329846] LR [d1d99270] .btrfs_run_delayed_refs+0x360/0x3a0 
[btrfs]
  [  181.329848] Call Trace:
  [  181.329894] [c0007d2c3910] [d1d99270] 
.btrfs_run_delayed_refs+0x360/0x3a0 [btrfs] (unreliable)
  [  181.329941] [c0007d2c39e0] [d1d9a5e0] 
.btrfs_write_dirty_block_groups+0x1d0/0x300 [btrfs]
  [  181.329995] [c0007d2c3ab0] [d1e4e3fc] 
.commit_cowonly_roots+0x284/0x36c [btrfs]
  [  181.330044] [c0007d2c3b90] [d1db37f8] 
.btrfs_commit_transaction+0x708/0xc40 [btrfs]
  [  181.330093] [c0007d2c3c70] [d1daf114] 
.transaction_kthread+0x2a4/0x340 [btrfs]
  [  181.330101] [c0007d2c3d30] [c00fa04c] .kthread+0x10c/0x130
  [  181.330108] [c0007d2c3e30] [c0009534] 
.ret_from_kernel_thread+0x58/0xa4
  [  

[Kernel-packages] [Bug 1584052] Re: btrfs: file write crashes with false ENOSPC during snapshot creation since kernel 4.4 - fix available

2016-06-14 Thread Oliver O.
Verified with the test script of #5. Kernel in -proposed solves the
problem.

Steps used:

1. Verified that release kernel 4.4.0-24-generic still had the problem.

2. Verified that kernel 4.4.0.25 from -proposed contains the resolution:

# apt-get install -s -t xenial-proposed 'linux-headers-4.4.0.25$'
'linux-headers-4.4.0.25-generic$' 'linux-image-4.4.0.25-generic$'
'linux-image-extra-4.4.0.25-generic$'

# reboot

# cat /proc/version
Linux version 4.4.0-25-generic (buildd@lgw01-05) (gcc version 5.3.1 20160413 
(Ubuntu 5.3.1-14ubuntu2.1) ) #44-Ubuntu SMP Fri Jun 10 18:19:48 UTC 2016

# ./test-btrfs-write-while-snapshotting.sh 
[problem did not show up on 10 consecutive runs]

Problem solved, changing tag to 'verification-done-xenial'.

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

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

Title:
  btrfs: file write crashes with false ENOSPC during snapshot creation
  since kernel 4.4 - fix available

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

Bug description:
  Kernel 4.4 introduced a btrfs bug where a process writing a file while
  a snapshot creation is underway will receive a false ENOSPC error (No
  space left on device), even while there is plenty of free space on the
  file system. On systems where snapshots are created frequently, this
  leads to frequent database crashes (here with MySQL):

  2016-05-19T21:00:01.862106Z 0 [Warning] InnoDB: Retry attempts for writing 
partial data failed.
  2016-05-19T21:00:01.862133Z 0 [ERROR] InnoDB: Write to file ./ibdata1failed 
at offset 1048576, 16384 bytes should have been written, only 0 were written. 
Operating system error number 28. Check that your OS a
  nd file system support files of this size. Check also that the disk is not 
full or a disk quota exceeded.
  2016-05-19T21:00:01.862143Z 0 [ERROR] InnoDB: Error number 28 means 'No space 
left on device'

  The problem is well known: 
http://www.spinics.net/lists/linux-btrfs/msg52672.html
  A patch is available: https://patchwork.kernel.org/patch/7967161/
  The patch has been committed to the Linux Kernel source tree on Feb 18, 2016: 
https://github.com/torvalds/linux/commits/master/fs/btrfs/file.c

  Creating snapshots for undo and backup purposes without interrupting
  database operations is a central aspect of btrfs usage. This bug
  breaks server operations and should be fixed in the xenial kernel.

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

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


[Kernel-packages] [Bug 1589889] Re: Bluetooth search gets nothing on Dell XPS 15 9550

2016-06-14 Thread Cruz Fernandez
I'm having same issue. Is the directory mentioned part of linux-firmware
? I think the directory where the file is missing is /lib/firmware/brcm/
?

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

Title:
  Bluetooth search gets nothing on Dell XPS 15 9550

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Title: Bluetooth search gets nothing on Dell XPS 15 9550

  Summary:
  Bluetooth search gets nothing on Dell XPS 15 9550

  Steps:
  1. Open Bluetooth Setting
  2. Click "+" to search nearby bluetooth devices

  Expected results: BT search could get nearby BT devices

  Actual results: Nothing shows from BT search

  Additional information:
  BT device:
  Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
  Couldn't open device, some information will be missing
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.00
    bDeviceClass  255 Vendor Specific Class
    bDeviceSubClass 1
    bDeviceProtocol 1
    bMaxPacketSize064
    idVendor   0x0a5c Broadcom Corp.
    idProduct  0x6410

  CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8x)

  GPU: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics
  530 (rev 06)

  Manufacturer: Dell

  ProductName: XPS 15 9550

  BiosVersion: 01.02.00

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

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


[Kernel-packages] [Bug 1591329] cavac (i386) - tests ran: 136, failed: 0

2016-06-14 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/cavac__3.2.0-105.146__2016-06-14_20-32-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1592566] [NEW] can't write to a BTRFS disk with my powermac

2016-06-14 Thread elvisplatini
Public bug reported:

Hi,
When I try to write to my BTRFS formated external disk, I get an error message 
explaining the file system is mounted read only. Indeed, I can still read data 
in it.

A dmesg shows the following errors:

[  143.354977] usb 1-2: new high-speed USB device number 4 using ehci-pci
[  143.564941] usb 1-2: New USB device found, idVendor=04e8, idProduct=61b5
[  143.564955] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  143.564963] usb 1-2: Product: Samsung M3 Portable
[  143.564971] usb 1-2: Manufacturer: Samsung M3 Portable
[  143.564978] usb 1-2: SerialNumber: D93E7DFA199A
[  143.668941] usbcore: registered new interface driver usb-storage
[  143.694409] scsi host5: uas
[  143.694601] usbcore: registered new interface driver uas
[  143.696560] scsi 5:0:0:0: Direct-Access Samsung  M3 Portable  1402 
PQ: 0 ANSI: 6
[  143.698592] sd 5:0:0:0: Attached scsi generic sg3 type 0
[  147.091177] sd 5:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 
TB/1.82 TiB)
[  147.091194] sd 5:0:0:0: [sdc] 4096-byte physical blocks
[  147.092774] sd 5:0:0:0: [sdc] Write Protect is off
[  147.092785] sd 5:0:0:0: [sdc] Mode Sense: 53 00 00 08
[  147.093629] sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[  147.109068]  sdc: sdc1
[  147.113161] sd 5:0:0:0: [sdc] Attached SCSI disk
[  147.744379] BTRFS: device fsid bf584dbe-6bf6-4847-8b32-cb0d22bead69 devid 1 
transid 17546 /dev/sdc1
[  148.044853] BTRFS info (device sdc1): disk space caching is enabled
[  148.044867] BTRFS: has skinny extents
[  181.329491] BTRFS: Transaction aborted (error -17)
[  181.329573] [ cut here ]
[  181.329577] WARNING: at 
/build/linux-t3xCGW/linux-4.4.0/fs/btrfs/extent-tree.c:2927
[  181.329580] Modules linked in: uas usb_storage drbg ansi_cprng ctr ccm arc4 
zd1211rw mac80211 cfg80211 input_leds mac_hid snd_aoa_codec_onyx snd_aoa 
snd_seq_midi snd_seq_midi_event rtc_generic snd_rawmidi snd_seq snd_seq_device 
snd_timer snd soundcore shpchp uio_pdrv_genirq uio parport_pc ppdev lp parport 
autofs4 btrfs xor raid6_pq windfarm_cpufreq_clamp windfarm_smu_sensors 
windfarm_smu_controls windfarm_pm112 windfarm_pid sil164 hid_generic nouveau 
windfarm_lm75_sensor windfarm_max6690_sensor i2c_algo_bit firewire_ohci 
windfarm_smu_sat windfarm_core firewire_core ttm crc_itu_t drm_kms_helper 
usbhid ata_generic hid drm tg3 ptp uninorth_agp pps_core
[  181.329658] CPU: 0 PID: 1490 Comm: btrfs-transacti Not tainted 
4.4.0-24-powerpc64-smp #43-Ubuntu
[  181.329663] task: c0007a633db0 ti: c0007d2c task.ti: 
c0007d2c
[  181.329666] NIP: d1d99274 LR: d1d99270 CTR: 
[  181.329670] REGS: c0007d2c3690 TRAP: 0700   Not tainted  
(4.4.0-24-powerpc64-smp)
[  181.329672] MSR: 90029032   CR: 24f72442  XER: 
2000
[  181.329683] SOFTE: 1 
   GPR00: d1d99270 c0007d2c3910 d1e8f2d0 
0026 
   GPR04: c0025de09ad0 c0025de0c360 0036 
02ab 
   GPR08: 0007 c10150fc 00025cdf6000 
0018 
   GPR12: 48f72444 cfdc c00f9f40 
c0007d082b80 
   GPR16:    
 
   GPR20: c0007de65800 0001  
c0007b765090 
   GPR24: c0007b784170 c0007b784160  
c0007b784000 
   GPR28: c0007de65800 c0007b765000 c0024e12bc00 
ffef 
[  181.329801] NIP [d1d99274] .btrfs_run_delayed_refs+0x364/0x3a0 
[btrfs]
[  181.329846] LR [d1d99270] .btrfs_run_delayed_refs+0x360/0x3a0 [btrfs]
[  181.329848] Call Trace:
[  181.329894] [c0007d2c3910] [d1d99270] 
.btrfs_run_delayed_refs+0x360/0x3a0 [btrfs] (unreliable)
[  181.329941] [c0007d2c39e0] [d1d9a5e0] 
.btrfs_write_dirty_block_groups+0x1d0/0x300 [btrfs]
[  181.329995] [c0007d2c3ab0] [d1e4e3fc] 
.commit_cowonly_roots+0x284/0x36c [btrfs]
[  181.330044] [c0007d2c3b90] [d1db37f8] 
.btrfs_commit_transaction+0x708/0xc40 [btrfs]
[  181.330093] [c0007d2c3c70] [d1daf114] 
.transaction_kthread+0x2a4/0x340 [btrfs]
[  181.330101] [c0007d2c3d30] [c00fa04c] .kthread+0x10c/0x130
[  181.330108] [c0007d2c3e30] [c0009534] 
.ret_from_kernel_thread+0x58/0xa4
[  181.330111] Instruction dump:
[  181.330114] 7d4048a8 7d474378 7ce049ad 40a2fff4 7c0004ac 7949f7e3 40a2001c 
3d42 
[  181.330124] 7fe4fb78 e86a8900 480be205 e8410028 <0fe0> 3d22 7fa3eb78 
e8a98908 
[  181.330134] ---[ end trace f2ee5bb68a7c169e ]---
[  181.330181] BTRFS: error (device sdc1) in btrfs_run_delayed_refs:2927: 
errno=-17 Object already exists
[  181.330187] BTRFS info (device sdc1): forced readonly
[  181.330875] BTRFS warning (device 

[Kernel-packages] [Bug 1592552] Re: Wily update to v4.2.8-ckt12 stable release

2016-06-14 Thread Kamal Mostafa
** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

** Description changed:

- 
- SRU Justification
- 
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The v4.2.8-ckt12 upstream 
stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
- 
-git://git.launchpad.net/~canonical-kernel/linux/+git/linux-
+ SRU Justification
+ 
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.2.8-ckt12 upstream 
stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
+ 
+    git://git.launchpad.net/~canonical-kernel/linux/+git/linux-
  stable-ckt
  
- TEST CASE: TBD
- 
-The following patches from the v4.2.8-ckt12 stable release shall
+ TEST CASE: TBD
+ 
+    The following patches from the v4.2.8-ckt12 stable release shall
  be applied:
+ 
+ Linux 4.2.8-ckt12
+ RDMA/cxgb3: device driver frees DMA memory with different size
+ drivers/hwspinlock: use correct radix tree API
+ uapi glibc compat: fix compilation when !__USE_MISC in glibc
+ tuntap: correctly wake up process during uninit
+ net: ehea: avoid null pointer dereference
+ batman-adv: fix skb deref after free
+ sunrpc: Update RPCBIND_MAXNETIDLEN
+ tipc: fix nametable publication field in nl compat
+ sched/preempt: Fix preempt_count manipulations
+ MIPS: ath79: fix regression in PCI window initialization
+ netlink: Fix dump skb leak/double free
+ x86/PCI: Mark Broadwell-EP Home Agent 1 as having non-compliant BARs
+ blk-mq: fix undefined behaviour in order_to_size()
+ i40e: fix an uninitialized variable bug
+ IB/IWPM: Fix a potential skb leak
+ IB/srp: Print "ib_srp: " prefix once
+ MIPS: BMIPS: Adjust mips-hpt-frequency for BCM7435
+ MIPS: Fix BC1{EQ,NE}Z return offset calculation
+ MIPS: math-emu: Fix BC1{EQ,NE}Z emulation
+ MIPS: BMIPS: Pretty print BMIPS5200 processor name
+ MIPS: BMIPS: local_r4k___flush_cache_all needs to blast S-cache
+ MIPS: BMIPS: Clear MIPS_CACHE_ALIASES earlier
+ MIPS: BMIPS: BMIPS5000 has I cache filing from D cache
+ powerpc/sstep: Fix sstep.c compile on powerpcspe
+ perf tools: Fix perf regs mask generation
+ s390/vmem: fix identity mapping
+ ata: sata_dwc_460ex: remove incorrect locking
+ NFS: Fix an LOCK/OPEN race when unlinking an open file
+ MIPS: BMIPS: Fix PRID_IMP_BMIPS5000 masking for BMIPS5200
+ clk: qcom: msm8916: Fix crypto clock flags
+ ACPI / sysfs: fix error code in get_status()
+ cpufreq: Fix GOV_LIMITS handling for the userspace governor
+ tty: vt, return error when con_startup fails
+ metag: Fix atomic_*_return inline asm constraints
+ driver-core: use 'dev' argument in dev_dbg_ratelimited stub
+ char: Drop bogus dependency of DEVPORT on !M68K
+ taskstats: fix nl parsing in accounting/getdelays.c
+ cxl: Fix DAR check & use REGION_ID instead of opencoding
+ ARM: debug: remove extraneous DEBUG_HI3716_UART option
+ alpha/PCI: Call iomem_is_exclusive() for IORESOURCE_MEM, but not IORESOURCE_IO
+ PCI: Supply CPU physical address (not bus address) to iomem_is_exclusive()
+ EDAC: Increment correct counter in edac_inc_ue_error()
+ perf test: Ignore kcore files in the "vmlinux matches kallsyms" test
+ usb: gadget: f_fs: Fix EFAULT generation for async read operations
+ ipv6, token: allow for clearing the current device token
+ cx23885: uninitialized variable in cx23885_av_work_handler()
+ am437x-vpfe: fix an uninitialized variable bug
+ am437x-vfpe: fix typo in vpfe_get_app_input_index
+ mfd: lp8788-irq: Uninitialized variable in irq handler
+ security: drop the unused hook skb_owned_by
+ ARM: OMAP2+: hwmod: fix _idle() hwmod state sanity check sequence
+ power: ipaq-micro-battery: freeing the wrong variable
+ iommu/vt-d: Improve fault handler error messages
+ iommu/vt-d: Ratelimit fault handler
+ iio: buffer: add missing descriptions in iio_buffer_access_funcs
+ serial: doc: Un-document non-existing uart_write_console()
+ ARM: dts: kirkwood: add kirkwood-ds112.dtb to Makefile
+ regmap: cache: Fix typo in cache_bypass parameter description
+ hpfs: implement the show_options method
+ affs: fix remount failure when there are no options changed
+ hpfs: fix remount failure when there are no options changed
+ MIPS: lib: Mark intrinsics notrace
+ Input: pwm-beeper - fix - scheduling while atomic
+ Input: xpad - prevent spurious input from wired Xbox 360 controllers
+ dell-rbtn: Ignore ACPI 

Re: [Kernel-packages] [Bug 1592541] Re: trusty kernel with virtio-blk oops

2016-06-14 Thread Ryan Harper
Having posted, I see that this is actually a utopic kernel that oopsed
(3.16.0-71-generic)

However, the oops stack is still possible on trusty, the blk-merge code in
3.13 doesn't include the fix
that appears in the vivid kernel.

On Tue, Jun 14, 2016 at 2:56 PM, Ryan Harper <1592...@bugs.launchpad.net>
wrote:

> Here's the qemu launch command used, in case that's useful.
>
>
>  qemu-system-x86_64 -enable-kvm -device
> virtio-scsi-pci,id=virtio-scsi-xkvm -device virtio-net-pci,netdev=net00
> -netdev type=user,id=net00 -m 1024 -serial
> file:/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/logs/install-serial.log
> -nographic -drive
> file=/tmp/launch.Cnc0wx/boot.img,if=none,cache=unsafe,format=qcow2,id=boot,index=0
> -device virtio-blk,drive=boot -drive
> file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/install_disk.img,if=none,cache=unsafe,format=raw,id=drv2,index=2
> -device
> virtio-blk,drive=drv2,serial=dev2,logical_block_size=512,physical_block_size=512,min_io_size=512
> -drive
> file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_0.img,if=none,cache=unsafe,format=raw,id=drv3,index=3
> -device
> virtio-blk,drive=drv3,serial=dev3,logical_block_size=512,physical_block_size=512,min_io_size=512
> -drive
> file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_1.img,if=none,cache=unsafe,format=raw,id=drv4,index=4
> -device
> virtio-blk,drive=drv4,serial=dev4,logical_block_size=512,physical_block_size=512,min_io_size=512
> -drive
> file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_2.img,if=none,cache=unsafe,format=raw,id=drv5,index=5
> -device
> virtio-blk,drive=drv5,serial=dev5,logical_block_size=512,physical_block_size=512,min_io_size=512
> -drive
> file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_3.img,if=none,cache=unsafe,format=raw,id=drv6,index=6
> -device
> virtio-blk,drive=drv6,serial=dev6,logical_block_size=512,physical_block_size=512,min_io_size=512
> -kernel /srv/images/trusty/amd64/20160606/utopic/generic/boot-kernel
> -initrd /srv/images/trusty/amd64/20160606/utopic/generic/boot-initrd
> -append "root=/dev/vda ds=nocloud-net;seedfrom=http://10.100.0.103:40646/
> console=ttyS0 "
> kvm pid=6128. my pid=6123
> QEMU 2.0.0 monitor - type 'help' for more information
> (qemu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1592541
>
> Title:
>   trusty kernel with virtio-blk oops
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592541/+subscriptions
>

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

Title:
  trusty kernel with virtio-blk oops

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The following oops was found in a Trusty Cloud-image when doing
  storage operations with software raid, lvm and various filesystems.

  [   85.327298] general protection fault:  [#1] SMP 
  [   85.327806] Modules linked in: bcache btrfs jfs xfs libcrc32c iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 
raid0 multipath linear cirrus syscopyarea sysfillrect sysimgblt psmouse 
virtio_scsi ttm drm_kms_helper drm pata_acpi floppy
  [   85.328008] CPU: 0 PID: 6 Comm: kworker/u2:0 Not tainted 3.16.0-71-generic 
#92~14.04.1-Ubuntu
  [   85.328008] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [   85.328008] Workqueue: writeback bdi_writeback_workfn (flush-251:0)
  [   85.328008] task: 88003c2732f0 ti: 88003c2a task.ti: 
88003c2a
  [   85.328008] RIP: 0010:[]  [] 
__blk_bios_map_sg+0x1be/0x3d0
  [   85.328008] RSP: 0018:88003c2a38d8  EFLAGS: 00010206
  [   85.328008] RAX: 3355167b09fe31e4 RBX: 0c00 RCX: 

  [   85.328008] RDX: 3355167b09fe31e5 RSI: eabd2a00 RDI: 

  [   85.328008] RBP: 88003c2a3958 R08: 880028d86520 R09: 
0080
  [   85.328008] R10:  R11: 2ed79000 R12: 

  [   85.328008] R13: 0c00 R14:  R15: 
88003c2a3968
  [   85.328008] FS:  () GS:88003e20() 
knlGS:
  [   85.328008] CS:  0010 DS:  ES:  CR0: 8005003b
  [   85.328008] CR2: 025b5000 CR3: 28d8a000 CR4: 
06f0
  [   85.328008] Stack:
  [   85.328008]  88002313e958 881dc4e0 

[Kernel-packages] [Bug 1591329] dagmar (i386) - tests ran: 136, failed: 0

2016-06-14 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/dagmar__3.2.0-105.146__2016-06-14_20-06-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1592552] [NEW] Wily update to v4.2.8-ckt12 stable release

2016-06-14 Thread Kamal Mostafa
Public bug reported:


SRU Justification

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

   git://git.launchpad.net/~canonical-kernel/linux/+git/linux-
stable-ckt

TEST CASE: TBD

   The following patches from the v4.2.8-ckt12 stable release shall
be applied:

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Wily update to v4.2.8-ckt12 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  New

Bug description:
  
  SRU Justification

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

 git://git.launchpad.net/~canonical-kernel/linux/+git/linux-
  stable-ckt

  TEST CASE: TBD

 The following patches from the v4.2.8-ckt12 stable release
  shall be applied:

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

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


[Kernel-packages] [Bug 1591329] cavac (amd64) - tests ran: 136, failed: 0

2016-06-14 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/cavac__3.2.0-105.146__2016-06-14_19-28-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1592429] Re: trusty kernel crash in OOM killer related to cgroups

2016-06-14 Thread Kamal Mostafa
Moritz, here is a test kernel with the three needed oom_kill patches*
applied.  Please confirm that it resolves the problem:

http://people.canonical.com/~kamal/lp1592429/

*[mainline]
4d4048b oom_kill: add rcu_read_lock() into find_lock_task_mm()
ad96244 oom_kill: has_intersects_mems_allowed() needs rcu_read_lock()
1da4db0 oom_kill: change oom_kill.c to use for_each_thread()

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

Title:
  trusty kernel crash in OOM killer related to cgroups

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

Bug description:
  The trusty kernel can crash if the OOM killer kills processes which
  have reached a memory limit imposed by cgroups. More details can be
  found in this blog post:

  https://community.nitrous.io/posts/stability-and-a-linux-oom-killer-
  bug

  The upstream patch series which ultimately landed in 3.14 is available
  at:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=4d4048be8a93769350efa31d2482a038b7de73d0=range=9853a407b97d8d066b5a865173a4859a3e69fd8a...4d4048be8a93769350efa31d2482a038b7de73d0

  One of those four (0c740d0afc3bff0a097ad03a1c8df92757516f5c) is
  already part of the trusty kernel.

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

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


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

2016-06-14 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/onibi__3.2.0-105.146__2016-06-14_19-15-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1592429] Re: trusty kernel crash in OOM killer related to cgroups

2016-06-14 Thread Kamal Mostafa
** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  trusty kernel crash in OOM killer related to cgroups

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

Bug description:
  The trusty kernel can crash if the OOM killer kills processes which
  have reached a memory limit imposed by cgroups. More details can be
  found in this blog post:

  https://community.nitrous.io/posts/stability-and-a-linux-oom-killer-
  bug

  The upstream patch series which ultimately landed in 3.14 is available
  at:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?id=4d4048be8a93769350efa31d2482a038b7de73d0=range=9853a407b97d8d066b5a865173a4859a3e69fd8a...4d4048be8a93769350efa31d2482a038b7de73d0

  One of those four (0c740d0afc3bff0a097ad03a1c8df92757516f5c) is
  already part of the trusty kernel.

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

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


[Kernel-packages] [Bug 1591329] onza (amd64) - tests ran: 136, failed: 0

2016-06-14 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/onza__3.2.0-105.146__2016-06-14_19-01-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


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

2016-06-14 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1592541

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

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

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

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

** Tags added: utopic

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

Title:
  trusty kernel with virtio-blk oops

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The following oops was found in a Trusty Cloud-image when doing
  storage operations with software raid, lvm and various filesystems.

  [   85.327298] general protection fault:  [#1] SMP 
  [   85.327806] Modules linked in: bcache btrfs jfs xfs libcrc32c iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 
raid0 multipath linear cirrus syscopyarea sysfillrect sysimgblt psmouse 
virtio_scsi ttm drm_kms_helper drm pata_acpi floppy
  [   85.328008] CPU: 0 PID: 6 Comm: kworker/u2:0 Not tainted 3.16.0-71-generic 
#92~14.04.1-Ubuntu
  [   85.328008] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [   85.328008] Workqueue: writeback bdi_writeback_workfn (flush-251:0)
  [   85.328008] task: 88003c2732f0 ti: 88003c2a task.ti: 
88003c2a
  [   85.328008] RIP: 0010:[]  [] 
__blk_bios_map_sg+0x1be/0x3d0
  [   85.328008] RSP: 0018:88003c2a38d8  EFLAGS: 00010206
  [   85.328008] RAX: 3355167b09fe31e4 RBX: 0c00 RCX: 

  [   85.328008] RDX: 3355167b09fe31e5 RSI: eabd2a00 RDI: 

  [   85.328008] RBP: 88003c2a3958 R08: 880028d86520 R09: 
0080
  [   85.328008] R10:  R11: 2ed79000 R12: 

  [   85.328008] R13: 0c00 R14:  R15: 
88003c2a3968
  [   85.328008] FS:  () GS:88003e20() 
knlGS:
  [   85.328008] CS:  0010 DS:  ES:  CR0: 8005003b
  [   85.328008] CR2: 025b5000 CR3: 28d8a000 CR4: 
06f0
  [   85.328008] Stack:
  [   85.328008]  88002313e958 881dc4e0 880037370f80 
0100
  [   85.328008]  880028d86520 8880  
eabd2a00
  [   85.328008]  0c00 eabb5e00 1000 
881dc340
  [   85.328008] Call Trace:
  [   85.328008]  [] blk_rq_map_sg+0x35/0x170
  [   85.328008]  [] virtio_queue_rq+0xa0/0x240
  [   85.328008]  [] __blk_mq_run_hw_queue+0x1c7/0x320
  [   85.328008]  [] blk_mq_run_hw_queue+0x65/0x80
  [   85.328008]  [] blk_mq_insert_requests+0xcf/0x150
  [   85.328008]  [] blk_mq_flush_plug_list+0x129/0x140
  [   85.328008]  [] blk_flush_plug_list+0xd1/0x220
  [   85.328008]  [] blk_finish_plug+0x14/0x40
  [   85.328008]  [] generic_writepages+0x4d/0x60
  [   85.328008]  [] do_writepages+0x1e/0x40
  [   85.328008]  [] __writeback_single_inode+0x40/0x2a0
  [   85.328008]  [] writeback_sb_inodes+0x26a/0x440
  [   85.328008]  [] __writeback_inodes_wb+0x9f/0xd0
  [   85.328008]  [] wb_writeback+0x283/0x320
  [   85.328008]  [] bdi_writeback_workfn+0x1e9/0x4a0
  [   85.328008]  [] process_one_work+0x178/0x470
  [   85.328008]  [] worker_thread+0x121/0x570
  [   85.328008]  [] ? rescuer_thread+0x380/0x380
  [   85.328008]  [] kthread+0xd2/0xf0
  [   85.328008]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [   85.328008]  [] ret_from_fork+0x58/0x90
  [   85.328008]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [   85.328008] Code: 3f 44 89 4c 24 28 48 89 4c 24 30 e8 8d 99 03 00 8b 7c 24 
44 48 8b 74 24 38 4c 8b 44 24 20 44 8b 4c 24 28 48 8b 4c 24 30 49 89 07 <48> 8b 
10 83 e2 03 40 f6 c6 03 0f 85 a0 01 00 00 48 09 f2 89 78 
  [   85.328008] RIP  [] __blk_bios_map_sg+0x1be/0x3d0
  [   85.328008]  RSP 
  [   85.355829] ---[ end trace 12bf400b01eb42cf ]---
  [   85.356327] BUG: unable to handle kernel paging request at ffd8
  [   85.356926] IP: [] kthread_data+0x10/0x20
  [   85.357393] PGD 1c16067 PUD 1c18067 PMD 0 
  [   85.357778] Oops:  [#2] SMP 
  [   85.358067] Modules linked in: bcache btrfs jfs xfs libcrc32c iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 
raid0 multipath linear cirrus syscopyarea sysfillrect sysimgblt psmouse 
virtio_scsi ttm drm_kms_helper drm pata_acpi floppy
  [   85.360215] CPU: 0 PID: 6 Comm: kworker/u2:0 Tainted: G  D   
3.16.0-71-generic #92~14.04.1-Ubuntu
  [   85.360215] Hardware name: 

[Kernel-packages] [Bug 1592541] Re: trusty kernel with virtio-blk oops

2016-06-14 Thread Ryan Harper
Here's the qemu launch command used, in case that's useful.


 qemu-system-x86_64 -enable-kvm -device virtio-scsi-pci,id=virtio-scsi-xkvm 
-device virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -m 1024 -serial 
file:/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/logs/install-serial.log
 -nographic -drive 
file=/tmp/launch.Cnc0wx/boot.img,if=none,cache=unsafe,format=qcow2,id=boot,index=0
 -device virtio-blk,drive=boot -drive 
file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/install_disk.img,if=none,cache=unsafe,format=raw,id=drv2,index=2
 -device 
virtio-blk,drive=drv2,serial=dev2,logical_block_size=512,physical_block_size=512,min_io_size=512
 -drive 
file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_0.img,if=none,cache=unsafe,format=raw,id=drv3,index=3
 -device 
virtio-blk,drive=drv3,serial=dev3,logical_block_size=512,physical_block_size=512,min_io_size=51
 2 -drive 
file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_1.img,if=none,cache=unsafe,format=raw,id=drv4,index=4
 -device 
virtio-blk,drive=drv4,serial=dev4,logical_block_size=512,physical_block_size=512,min_io_size=512
 -drive 
file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_2.img,if=none,cache=unsafe,format=raw,id=drv5,index=5
 -device 
virtio-blk,drive=drv5,serial=dev5,logical_block_size=512,physical_block_size=512,min_io_size=512
 -drive 
file=/var/lib/jenkins/slaves/venonat/workspace/curtin-vmtest-venonat-devel/output/TrustyHWEUTestRaid5Bcache/disks/extra_disk_3.img,if=none,cache=unsafe,format=raw,id=drv6,index=6
 -device 
virtio-blk,drive=drv6,serial=dev6,logical_block_size=512,physical_block_size=512,min_io_size=512
 -kernel /srv/images/trusty/amd64/20160606/utopic/generic/boot-kernel -initrd 
/srv/images/trusty/amd64/20160606/utopic/gene
 ric/boot-initrd -append "root=/dev/vda 
ds=nocloud-net;seedfrom=http://10.100.0.103:40646/ console=ttyS0 "
kvm pid=6128. my pid=6123
QEMU 2.0.0 monitor - type 'help' for more information
(qemu)

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

Title:
  trusty kernel with virtio-blk oops

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The following oops was found in a Trusty Cloud-image when doing
  storage operations with software raid, lvm and various filesystems.

  [   85.327298] general protection fault:  [#1] SMP 
  [   85.327806] Modules linked in: bcache btrfs jfs xfs libcrc32c iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 
raid0 multipath linear cirrus syscopyarea sysfillrect sysimgblt psmouse 
virtio_scsi ttm drm_kms_helper drm pata_acpi floppy
  [   85.328008] CPU: 0 PID: 6 Comm: kworker/u2:0 Not tainted 3.16.0-71-generic 
#92~14.04.1-Ubuntu
  [   85.328008] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
  [   85.328008] Workqueue: writeback bdi_writeback_workfn (flush-251:0)
  [   85.328008] task: 88003c2732f0 ti: 88003c2a task.ti: 
88003c2a
  [   85.328008] RIP: 0010:[]  [] 
__blk_bios_map_sg+0x1be/0x3d0
  [   85.328008] RSP: 0018:88003c2a38d8  EFLAGS: 00010206
  [   85.328008] RAX: 3355167b09fe31e4 RBX: 0c00 RCX: 

  [   85.328008] RDX: 3355167b09fe31e5 RSI: eabd2a00 RDI: 

  [   85.328008] RBP: 88003c2a3958 R08: 880028d86520 R09: 
0080
  [   85.328008] R10:  R11: 2ed79000 R12: 

  [   85.328008] R13: 0c00 R14:  R15: 
88003c2a3968
  [   85.328008] FS:  () GS:88003e20() 
knlGS:
  [   85.328008] CS:  0010 DS:  ES:  CR0: 8005003b
  [   85.328008] CR2: 025b5000 CR3: 28d8a000 CR4: 
06f0
  [   85.328008] Stack:
  [   85.328008]  88002313e958 881dc4e0 880037370f80 
0100
  [   85.328008]  880028d86520 8880  
eabd2a00
  [   85.328008]  0c00 eabb5e00 1000 
881dc340
  [   85.328008] Call Trace:
  [   85.328008]  [] blk_rq_map_sg+0x35/0x170
  [   85.328008]  [] virtio_queue_rq+0xa0/0x240
  [   85.328008]  [] __blk_mq_run_hw_queue+0x1c7/0x320
  [   85.328008]  [] blk_mq_run_hw_queue+0x65/0x80
  [   85.328008]  [] blk_mq_insert_requests+0xcf/0x150
  [   85.328008]  [] blk_mq_flush_plug_list+0x129/0x140
  [   85.328008]  [] blk_flush_plug_list+0xd1/0x220
  [   85.328008]  [] blk_finish_plug+0x14/0x40
  [   85.328008]  [] 

[Kernel-packages] [Bug 1591329] dagmar (amd64) - tests ran: 136, failed: 0

2016-06-14 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/dagmar__3.2.0-105.146__2016-06-14_19-11-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1592541] [NEW] trusty kernel with virtio-blk oops

2016-06-14 Thread Ryan Harper
Public bug reported:

The following oops was found in a Trusty Cloud-image when doing storage
operations with software raid, lvm and various filesystems.

[   85.327298] general protection fault:  [#1] SMP 
[   85.327806] Modules linked in: bcache btrfs jfs xfs libcrc32c iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 
raid0 multipath linear cirrus syscopyarea sysfillrect sysimgblt psmouse 
virtio_scsi ttm drm_kms_helper drm pata_acpi floppy
[   85.328008] CPU: 0 PID: 6 Comm: kworker/u2:0 Not tainted 3.16.0-71-generic 
#92~14.04.1-Ubuntu
[   85.328008] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
[   85.328008] Workqueue: writeback bdi_writeback_workfn (flush-251:0)
[   85.328008] task: 88003c2732f0 ti: 88003c2a task.ti: 
88003c2a
[   85.328008] RIP: 0010:[]  [] 
__blk_bios_map_sg+0x1be/0x3d0
[   85.328008] RSP: 0018:88003c2a38d8  EFLAGS: 00010206
[   85.328008] RAX: 3355167b09fe31e4 RBX: 0c00 RCX: 
[   85.328008] RDX: 3355167b09fe31e5 RSI: eabd2a00 RDI: 
[   85.328008] RBP: 88003c2a3958 R08: 880028d86520 R09: 0080
[   85.328008] R10:  R11: 2ed79000 R12: 
[   85.328008] R13: 0c00 R14:  R15: 88003c2a3968
[   85.328008] FS:  () GS:88003e20() 
knlGS:
[   85.328008] CS:  0010 DS:  ES:  CR0: 8005003b
[   85.328008] CR2: 025b5000 CR3: 28d8a000 CR4: 06f0
[   85.328008] Stack:
[   85.328008]  88002313e958 881dc4e0 880037370f80 
0100
[   85.328008]  880028d86520 8880  
eabd2a00
[   85.328008]  0c00 eabb5e00 1000 
881dc340
[   85.328008] Call Trace:
[   85.328008]  [] blk_rq_map_sg+0x35/0x170
[   85.328008]  [] virtio_queue_rq+0xa0/0x240
[   85.328008]  [] __blk_mq_run_hw_queue+0x1c7/0x320
[   85.328008]  [] blk_mq_run_hw_queue+0x65/0x80
[   85.328008]  [] blk_mq_insert_requests+0xcf/0x150
[   85.328008]  [] blk_mq_flush_plug_list+0x129/0x140
[   85.328008]  [] blk_flush_plug_list+0xd1/0x220
[   85.328008]  [] blk_finish_plug+0x14/0x40
[   85.328008]  [] generic_writepages+0x4d/0x60
[   85.328008]  [] do_writepages+0x1e/0x40
[   85.328008]  [] __writeback_single_inode+0x40/0x2a0
[   85.328008]  [] writeback_sb_inodes+0x26a/0x440
[   85.328008]  [] __writeback_inodes_wb+0x9f/0xd0
[   85.328008]  [] wb_writeback+0x283/0x320
[   85.328008]  [] bdi_writeback_workfn+0x1e9/0x4a0
[   85.328008]  [] process_one_work+0x178/0x470
[   85.328008]  [] worker_thread+0x121/0x570
[   85.328008]  [] ? rescuer_thread+0x380/0x380
[   85.328008]  [] kthread+0xd2/0xf0
[   85.328008]  [] ? kthread_create_on_node+0x1c0/0x1c0
[   85.328008]  [] ret_from_fork+0x58/0x90
[   85.328008]  [] ? kthread_create_on_node+0x1c0/0x1c0
[   85.328008] Code: 3f 44 89 4c 24 28 48 89 4c 24 30 e8 8d 99 03 00 8b 7c 24 
44 48 8b 74 24 38 4c 8b 44 24 20 44 8b 4c 24 28 48 8b 4c 24 30 49 89 07 <48> 8b 
10 83 e2 03 40 f6 c6 03 0f 85 a0 01 00 00 48 09 f2 89 78 
[   85.328008] RIP  [] __blk_bios_map_sg+0x1be/0x3d0
[   85.328008]  RSP 
[   85.355829] ---[ end trace 12bf400b01eb42cf ]---
[   85.356327] BUG: unable to handle kernel paging request at ffd8
[   85.356926] IP: [] kthread_data+0x10/0x20
[   85.357393] PGD 1c16067 PUD 1c18067 PMD 0 
[   85.357778] Oops:  [#2] SMP 
[   85.358067] Modules linked in: bcache btrfs jfs xfs libcrc32c iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 
raid0 multipath linear cirrus syscopyarea sysfillrect sysimgblt psmouse 
virtio_scsi ttm drm_kms_helper drm pata_acpi floppy
[   85.360215] CPU: 0 PID: 6 Comm: kworker/u2:0 Tainted: G  D   
3.16.0-71-generic #92~14.04.1-Ubuntu
[   85.360215] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Bochs 01/01/2011
[   85.360215] task: 88003c2732f0 ti: 88003c2a task.ti: 
88003c2a
[   85.360215] RIP: 0010:[]  [] 
kthread_data+0x10/0x20
[   85.360215] RSP: 0018:88003c2a3690  EFLAGS: 00010002
[   85.360215] RAX:  RBX:  RCX: 000f
[   85.360215] RDX:  RSI:  RDI: 88003c2732f0
[   85.360215] RBP: 88003c2a3690 R08:  R09: 00018027001c
[   85.360215] R10: 813621da R11: eadcb540 R12: 88003e2130c0
[   85.360215] R13:  R14:  R15: 88003c2732f0
[   85.360215] FS:  () GS:88003e20() 
knlGS:
[   85.360215] CS:  0010 DS:  ES:  CR0: 8005003b
[   85.360215] CR2: 0028 CR3: 3f36 CR4: 06f0
[  

[Kernel-packages] [Bug 1591329] phact (i386) - tests ran: 136, failed: 0

2016-06-14 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/phact__3.2.0-105.146__2016-06-14_18-59-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1586650] Re: Ubuntu 16.04 touchy WiFi Internet

2016-06-14 Thread dozycat
I have the same problem.
In windows xp the wireless works at 150 mbps, but in xubuntu 16.04 it works 
most of the time at 1 mbps, some times at 39 mbps.
Before in lubuntu 12.04 it worked perfect.
I could do report apport report...

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

Title:
  Ubuntu 16.04 touchy WiFi Internet

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I installed Ubuntu 16.04 I had to reconfigure our modem and
  router setup from bridge mode to DHCP mode. As a result, I lost all
  ability on my computer to connect to WiFi.

  However, the other eight connected devices (ex. iPad, PlayStation)
  have Internet connection.

  After power-cycling our router and modem I'm now able to connect but I
  get 2 Mbps download speed, and web pages load up slowly.

  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nicholas   1993 F pulseaudio
   /dev/snd/controlC0:  nicholas   1993 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=65e816b7-679f-4d88-9cef-c4d5eeb89f23
  InstallationDate: Installed on 2016-05-30 (7 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic 
root=UUID=6b080b23-fe79-4a22-9dec-bd3d029dda95 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-87-generic N/A
   linux-backports-modules-3.13.0-87-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-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A78LT-M-LE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd07/23/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78LT-M-LE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1588449] Re: NVMe max_segments queue parameter gets set to 1

2016-06-14 Thread bugproxy
--- Comment From heit...@br.ibm.com 2016-06-14 15:19 EDT---
(In reply to comment #7)
> This bug is awaiting verification that the kernel in -proposed solves the
> problem. Please test the kernel and update this bug with the results. If the
> problem is solved, change the tag 'verification-needed-xenial' to
> 'verification-done-xenial'.
>
> If verification is not done by 5 working days from today, this fix will be
> dropped from the source code, and this bug will be closed.
>
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed. Thank you!

Tested on 4.4.0-25-generic, patches seem to be included:

root@everest-lp13:~/halves# ./queue.sh nvme0n1
/sys/block/nvme0n1/queue/add_random = 0
/sys/block/nvme0n1/queue/discard_granularity = 4096
/sys/block/nvme0n1/queue/discard_max_bytes = 2199023255040
/sys/block/nvme0n1/queue/discard_max_hw_bytes = 4294966784
/sys/block/nvme0n1/queue/discard_zeroes_data = 0
/sys/block/nvme0n1/queue/hw_sector_size = 4096
/sys/block/nvme0n1/queue/io_poll = 0
/sys/block/nvme0n1/queue/iostats = 1
/sys/block/nvme0n1/queue/logical_block_size = 4096
/sys/block/nvme0n1/queue/max_hw_sectors_kb = 2147483647
/sys/block/nvme0n1/queue/max_integrity_segments = 0
/sys/block/nvme0n1/queue/max_sectors_kb = 1280
/sys/block/nvme0n1/queue/max_segments = 65535
/sys/block/nvme0n1/queue/max_segment_size = 65536
/sys/block/nvme0n1/queue/minimum_io_size = 4096
/sys/block/nvme0n1/queue/nomerges = 2
/sys/block/nvme0n1/queue/nr_requests = 1023
/sys/block/nvme0n1/queue/optimal_io_size = 0
/sys/block/nvme0n1/queue/physical_block_size = 4096
/sys/block/nvme0n1/queue/read_ahead_kb = 128
/sys/block/nvme0n1/queue/rotational = 0
/sys/block/nvme0n1/queue/rq_affinity = 1
/sys/block/nvme0n1/queue/scheduler = none
/sys/block/nvme0n1/queue/write_same_max_bytes = 0

root@everest-lp13:~/halves# uname -r
4.4.0-25-generic

Moving to verified. Thanks!

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

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

Title:
  NVMe max_segments queue parameter gets set to 1

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

Bug description:
  == Comment: #0 - Heitor Ricardo Alves de Siqueira - 2016-06-02 10:41:18 ==
  There are some upstream patches missing from the 16.04 nvme driver, and this 
limits adapter performance. We need to include these so that NVMe devices are 
correctly set up.

  I would like to ask Canonical to cherry pick the following patches for the 
16.04 kernel:
  * da35825d9a09 ("nvme: set queue limits for the admin queue")
  * 45686b6198bd ("nvme: fix max_segments integer truncation")
  * f21018427cb0 ("block: fix blk_rq_get_max_sectors for driver private 
requests")
   
  ---uname output---
  Linux ubuntu 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:35 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Steps to Reproduce---
  Boot the system with an NVMe adapter connected, and verify the queue 
parameters:

  root@ubuntu:~# ./queue.sh nvme0n1
  /sys/block/nvme0n1/queue/add_random = 0
  /sys/block/nvme0n1/queue/discard_granularity = 4096
  /sys/block/nvme0n1/queue/discard_max_bytes = 2199023255040
  /sys/block/nvme0n1/queue/discard_max_hw_bytes = 4294966784
  /sys/block/nvme0n1/queue/discard_zeroes_data = 0
  /sys/block/nvme0n1/queue/hw_sector_size = 4096
  /sys/block/nvme0n1/queue/io_poll = 0
  /sys/block/nvme0n1/queue/iostats = 1
  /sys/block/nvme0n1/queue/logical_block_size = 4096
  /sys/block/nvme0n1/queue/max_hw_sectors_kb = 2147483647
  /sys/block/nvme0n1/queue/max_integrity_segments = 0
  /sys/block/nvme0n1/queue/max_sectors_kb = 1280
  /sys/block/nvme0n1/queue/max_segments = 1<-
  /sys/block/nvme0n1/queue/max_segment_size = 65536
  /sys/block/nvme0n1/queue/minimum_io_size = 4096
  /sys/block/nvme0n1/queue/nomerges = 2
  /sys/block/nvme0n1/queue/nr_requests = 1023
  /sys/block/nvme0n1/queue/optimal_io_size = 0
  /sys/block/nvme0n1/queue/physical_block_size = 4096
  /sys/block/nvme0n1/queue/read_ahead_kb = 128
  /sys/block/nvme0n1/queue/rotational = 0
  /sys/block/nvme0n1/queue/rq_affinity = 1
  /sys/block/nvme0n1/queue/scheduler = none
  /sys/block/nvme0n1/queue/write_same_max_bytes = 0

  We should have max_segments set to 65535 by default.

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

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


[Kernel-packages] [Bug 1592531] [NEW] Cannot compile module tda10071

2016-06-14 Thread Tim Ritberg
Public bug reported:

Xubuntu 16.10, Kernel source 4.4.0.24.25

Can't compile tda10071 as a module:

  Building modules, stage 2.
Kernel: arch/x86/boot/bzImage is ready  (#2)
  MODPOST 408 modules
ERROR: "__devm_regmap_init_i2c" [drivers/media/dvb-frontends/tda10071.ko] 
undefined!
scripts/Makefile.modpost:91: recipe for target '__modpost' failed
make[1]: *** [__modpost] Error 1
Makefile:1118: recipe for target 'modules' failed
make: *** [modules] Error 2

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1592531

Title:
  Cannot compile module tda10071

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 16.10, Kernel source 4.4.0.24.25

  Can't compile tda10071 as a module:

Building modules, stage 2.
  Kernel: arch/x86/boot/bzImage is ready  (#2)
MODPOST 408 modules
  ERROR: "__devm_regmap_init_i2c" [drivers/media/dvb-frontends/tda10071.ko] 
undefined!
  scripts/Makefile.modpost:91: recipe for target '__modpost' failed
  make[1]: *** [__modpost] Error 1
  Makefile:1118: recipe for target 'modules' failed
  make: *** [modules] Error 2

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

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


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

2016-06-14 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1592531

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

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

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

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

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

Title:
  Cannot compile module tda10071

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 16.10, Kernel source 4.4.0.24.25

  Can't compile tda10071 as a module:

Building modules, stage 2.
  Kernel: arch/x86/boot/bzImage is ready  (#2)
MODPOST 408 modules
  ERROR: "__devm_regmap_init_i2c" [drivers/media/dvb-frontends/tda10071.ko] 
undefined!
  scripts/Makefile.modpost:91: recipe for target '__modpost' failed
  make[1]: *** [__modpost] Error 1
  Makefile:1118: recipe for target 'modules' failed
  make: *** [modules] Error 2

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

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


[Kernel-packages] [Bug 1586875] Re: Support for Qualcomm Atheros AR928X WiFi chipset

2016-06-14 Thread dozycat
*** This bug is a duplicate of bug 1586650 ***
https://bugs.launchpad.net/bugs/1586650

I have the same problem, xubuntu 16.04. the wireless works in windows xp with 
speed of 150 mbps, however in ubuntu  the wireless jumps from 39 mbps to 1 mbps 
( most of the time 1 mbps). But I can connet to internet.
Before I had lubuntu 12.04 and it worked perfect.

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

Title:
  Support for Qualcomm Atheros AR928X WiFi chipset

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  A number of other Ubuntu users and myself have encountered difficulty
  when upgrading to Ubuntu 16.04 LTS due to our WiFi chipset not being
  supported. When I inquired about it on the Ubuntu Forums, I was
  informed that this chipset was last known to work on Ubuntu 14.04.3,
  and no longer in Ubuntu 14.04.4.

  I had bought this network adapter about a year ago from a Linux-
  friendly retailer specifically because it said it would work
  harmoniously with Ubuntu. But because it is not supported in 16.04, I
  am left without Internet access on my desktop, which I require for
  work and for pleasure.

  Unfortunately, connecting to my router with an Ethernet cord is not an
  option, as the distance is too great and awkward. In the meantime, I
  will have to revert to Ubuntu 14.04.3 to hopefully get Internet on my
  computer. I hope this will be resolved soon. I'd really like to
  continue using the latest Ubuntu versions.

  My Ubuntu Forums post:
  http://ubuntuforums.org/showthread.php?t=2326224=13496747#post13496747

  A similar post:
  http://ubuntuforums.org/showthread.php?t=2323816

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

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


[Kernel-packages] [Bug 1591329] cavac (i386) - tests ran: 21, failed: 2

2016-06-14 Thread Brad Figg
tests ran:  21, failed: 2;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/cavac__3.2.0-105.146__2016-06-14_17-36-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1591329] dagmar (i386) - tests ran: 21, failed: 2

2016-06-14 Thread Brad Figg
tests ran:  21, failed: 2;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/dagmar__3.2.0-105.146__2016-06-14_17-19-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1591329] onibi (amd64) - tests ran: 136, failed: 0

2016-06-14 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/onibi__3.2.0-105.146__2016-06-14_18-16-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1591329] phact (amd64) - tests ran: 136, failed: 0

2016-06-14 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/phact__3.2.0-105.146__2016-06-14_18-14-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1591329] onza (i386) - tests ran: 21, failed: 2

2016-06-14 Thread Brad Figg
tests ran:  21, failed: 2;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/onza__3.2.0-105.146__2016-06-14_17-15-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1591329] alkaid (i386) - tests ran: 136, failed: 0

2016-06-14 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/alkaid__3.2.0-105.146__2016-06-14_17-59-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1589704] Re: workaround cavium thunderx silicon erratum 23144

2016-06-14 Thread dann frazier
I rebuilt d-i against the kernel in proposed and booted it a couple of
times. I have not reproduced this issue, so marking it verified.

~ # uname -a
Linux cvm3 4.4.0-25-generic #44-Ubuntu SMP Fri Jun 10 18:15:04 UTC 2016 aarch64 
GNU/Linux
~ # dmesg | grep -i soft
[0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-di 
root=UUID=bc611283-1f38-4993-a2b9-883922c7ed1f ro earlycon=pl011,0x87e02400 
hardlockup_all_cpu_backtrace=1 softlockup_all_cpu_backtrace=1 
earlycon=pl011,0x87e02400 apt-setup/proposed=true
[0.00] software IO TLB [mem 0xfbfed000-0xfffed000] (64MB) mapped at 
[8000fb1ed000-8000ff1ecfff]
[0.229859] CPU features: detected feature: Software prefetching using PRFM
[  174.913338] xor: measuring software checksum speed

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

Title:
  workaround cavium thunderx silicon erratum 23144

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  This impacts 2 socket Cavium ThunderX systems using pass-1.1 silicon, and can 
result in IO hangs.

  [Test Case]
  $ dmesg | grep "ITS command queue timeout"

  [Regression Risk]
  The workaround is in gicv3 specific code, and only activated when the hw 
revision in the IIDR matches ThunderX pass 1.x silicon, so risk to other 
platforms is minimal.

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

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


[Kernel-packages] [Bug 1574814] Re: ThunderX: soft lockup in cursor_timer_handler()

2016-06-14 Thread dann frazier
I rebuilt d-i against the kernel in proposed and booted it a couple of
times. I have not reproduced this issue, so marking it verified.

~ # uname -a
Linux cvm3 4.4.0-25-generic #44-Ubuntu SMP Fri Jun 10 18:15:04 UTC 2016 aarch64 
GNU/Linux
~ # dmesg | grep -i soft
[ 0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-di 
root=UUID=bc611283-1f38-4993-a2b9-883922c7ed1f ro earlycon=pl011,0x87e02400 
hardlockup_all_cpu_backtrace=1 softlockup_all_cpu_backtrace=1 
earlycon=pl011,0x87e02400 apt-setup/proposed=true
[ 0.00] software IO TLB [mem 0xfbfed000-0xfffed000] (64MB) mapped at 
[8000fb1ed000-8000ff1ecfff]
[ 0.229859] CPU features: detected feature: Software prefetching using PRFM
[ 174.913338] xor: measuring software checksum speed

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

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

Title:
  ThunderX: soft lockup in cursor_timer_handler()

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via 
virtual media:

http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso

  During boot I observed the following lockup on the serial console:

  [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
[swapper/14:0]
  [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
  [ 84.922749]
  [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic 
#37-Ubuntu
  [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
  [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
801f6c9e8000
  [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
  [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
  [ 84.922778] pc : [] lr : [] pstate: 
00400145
  [ 84.922781] sp : 801f6c9ebc20
  [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
  [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
  [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
  [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
  [ 84.922802] x21: 0100 x20: 8000f94398d8
  [ 84.922807] x19: 8000f9439800 x18: c76a5358
  [ 84.922811] x17: 97bbd2a8 x16: 802a5040
  [ 84.922816] x15: 3e4cf1e0 x14: 0008
  [ 84.922820] x13:  x12: 003d0900
  [ 84.922824] x11: 003d0900 x10: 8090f200
  [ 84.922829] x9 : 3d09 x8 : 000e
  [ 84.922833] x7 : 801f7b3c5008 x6 : 
  [ 84.922837] x5 :  x4 : 0001
  [ 84.922842] x3 :  x2 : 801f6c899e05
  [ 84.922846] x1 : 801f667d99e0 x0 : 
  [ 84.922850]
  [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.342677] random: nonblocking pool is initialized

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

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


[Kernel-packages] [Bug 1589704] Re: workaround cavium thunderx silicon erratum 23144

2016-06-14 Thread dann frazier
Oops, comment #3 was posted against the wrong bug. This one still
requires verification.

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

Title:
  workaround cavium thunderx silicon erratum 23144

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  This impacts 2 socket Cavium ThunderX systems using pass-1.1 silicon, and can 
result in IO hangs.

  [Test Case]
  $ dmesg | grep "ITS command queue timeout"

  [Regression Risk]
  The workaround is in gicv3 specific code, and only activated when the hw 
revision in the IIDR matches ThunderX pass 1.x silicon, so risk to other 
platforms is minimal.

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

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


[Kernel-packages] [Bug 1591631] Re: Atheros AR928X Wireless Network Adapter has poor range

2016-06-14 Thread Jim Tarrant
I upgraded the bios to V1.09 but the problem still remains.

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

Title:
  Atheros AR928X Wireless Network Adapter has poor range

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Atheros AR928X Wireless Network Adapter will only connect to my
  WiFi base station if it's very close to it.  When connected, if I move
  about 5 metres away, the connection drops.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-38-generic 4.2.0-38.45~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10
  Uname: Linux 4.2.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jun 12 08:26:48 2016
  InstallationDate: Installed on 2016-06-01 (10 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jim2165 F pulseaudio
   /dev/snd/controlC1:  jim2165 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-06-01 (11 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Acer Aspire 5542
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-38-generic 
root=UUID=7d2bd334-80d7-4869-8ca2-849d7a1dcd3c ro quiet splash 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
  Tags:  trusty
  Uname: Linux 4.2.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/11/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.03
  dmi.board.name: JV50TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.03:bd08/11/2009:svnAcer:pnAspire5542:pvr0100:rvnAcer:rnJV50TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 5542
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1591329] onibi (i386) - tests ran: 21, failed: 2

2016-06-14 Thread Brad Figg
tests ran:  21, failed: 2;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/onibi__3.2.0-105.146__2016-06-14_16-34-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1591329] phact (i386) - tests ran: 21, failed: 2

2016-06-14 Thread Brad Figg
tests ran:  21, failed: 2;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/phact__3.2.0-105.146__2016-06-14_16-37-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1587316] Re: STC840.20:Alpine:alp7fp1:Ubuntu 16.04, BlueFin (SAN) EEH 6 times during boot then disabled SRC BA188002:b0314a_1612.840

2016-06-14 Thread 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/1587316

Title:
  STC840.20:Alpine:alp7fp1:Ubuntu 16.04, BlueFin (SAN) EEH 6 times
  during boot then disabled SRC BA188002:b0314a_1612.840

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

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-03-21 15:55:09 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-03-21 
15:55:11 ==
   State: Open by: mlfield on 21 March 2016 14:45:01 

  ==Automatic entries==
  Contact: LittleField, Michael *CONTRACTOR*
  Backup: Thirukumaran V T (thirukuma...@in.ibm.com), Deepti Umarani 
(deeptiumar...@in.ibm.com), Brian M. Carpenter(c...@us.ibm.com)

  = sys_capture v5.24 === 2016-03-21_14-25-41 ===

  |
  ||
  |System Hardware Information:
  |  NODE /Sys-0/Node-0, U78C7.001.1AQH383-P2
  | FSP  /Sys-0/Node-0/FSP-0, FSP-2 DD 1.0, U78C7.001.1AQH383-P1-C5
  |PSI  /Sys-0/Node-0/FSP-0/PSI-0
  |PSI  /Sys-0/Node-0/FSP-0/PSI-1
  | MEMBUF /Sys-0/Node-0/Membuf-12, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C11
  | MEMBUF /Sys-0/Node-0/Membuf-13, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C10
  | MEMBUF /Sys-0/Node-0/Membuf-14, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C12
  | MEMBUF /Sys-0/Node-0/Membuf-15, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C13
  | MEMBUF /Sys-0/Node-0/Membuf-20, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C23
  | MEMBUF /Sys-0/Node-0/Membuf-21, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C22
  | MEMBUF /Sys-0/Node-0/Membuf-22, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C24
  | MEMBUF /Sys-0/Node-0/Membuf-23, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C25
  | MEMBUF /Sys-0/Node-0/Membuf-28, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C19
  | MEMBUF /Sys-0/Node-0/Membuf-29, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C18
  | MEMBUF /Sys-0/Node-0/Membuf-30, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C20
  | MEMBUF /Sys-0/Node-0/Membuf-31, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C21
  | MEMBUF /Sys-0/Node-0/Membuf-36, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C31
  | MEMBUF /Sys-0/Node-0/Membuf-37, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C30
  | MEMBUF /Sys-0/Node-0/Membuf-38, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C32
  | MEMBUF /Sys-0/Node-0/Membuf-39, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C33
  | MEMBUF /Sys-0/Node-0/Membuf-4, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C15
  | MEMBUF /Sys-0/Node-0/Membuf-44, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C27
  | MEMBUF /Sys-0/Node-0/Membuf-45, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C26
  | MEMBUF /Sys-0/Node-0/Membuf-46, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C28
  | MEMBUF /Sys-0/Node-0/Membuf-47, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C29
  | MEMBUF /Sys-0/Node-0/Membuf-5, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C14
  | MEMBUF /Sys-0/Node-0/Membuf-52, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C39
  | MEMBUF /Sys-0/Node-0/Membuf-53, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C38
  | MEMBUF /Sys-0/Node-0/Membuf-54, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C40
  | MEMBUF /Sys-0/Node-0/Membuf-55, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C41
  | MEMBUF /Sys-0/Node-0/Membuf-6, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C16
  | MEMBUF /Sys-0/Node-0/Membuf-60, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C35
  | MEMBUF /Sys-0/Node-0/Membuf-61, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C34
  | MEMBUF /Sys-0/Node-0/Membuf-62, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C36
  | MEMBUF /Sys-0/Node-0/Membuf-63, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C37
  | MEMBUF /Sys-0/Node-0/Membuf-7, CENTAUR EC 2.0, 
U78C7.001.1AQH383-P2-C17
  | PROC /Sys-0/Node-0/Proc-0, P8/Murano DD 2.1, U78C7.001.1AQH383-P2-C2
  |CORE /Sys-0/Node-0/Proc-0/EX-12/Core-0
  |CORE /Sys-0/Node-0/Proc-0/EX-13/Core-0
  |CORE /Sys-0/Node-0/Proc-0/EX-14/Core-0
  |CORE /Sys-0/Node-0/Proc-0/EX-4/Core-0
  |PCI  /Sys-0/Node-0/Proc-0/PCI-0
  |PCI  /Sys-0/Node-0/Proc-0/PCI-1
  |PCI  /Sys-0/Node-0/Proc-0/PCI-2
  |PSI  /Sys-0/Node-0/Proc-0/PSI-0
  | PROC /Sys-0/Node-0/Proc-1, P8/Murano DD 2.1, U78C7.001.1AQH383-P2-C2
  |CORE /Sys-0/Node-0/Proc-1/EX-13/Core-0
  |CORE /Sys-0/Node-0/Proc-1/EX-14/Core-0
  |CORE /Sys-0/Node-0/Proc-1/EX-4/Core-0
  |CORE /Sys-0/Node-0/Proc-1/EX-5/Core-0
  |PCI  /Sys-0/Node-0/Proc-1/PCI-0
  |PCI  

[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards

2016-06-14 Thread Kamal Mostafa
** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => In Progress

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

** Changed in: linux (Ubuntu Wily)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

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

Bug description:
  I have a K520 Logitech keyboard and sometimes something starts to keep 
pressing key 5.
  It mostly happens when I leave the computer alone for some time, but 
sometimes also just during regular usage.

  It seems that this is a Linux specific issue as no one is complaining
  about this issue under Windows, but a couple of people are complaining
  for different versions of Ubuntu.

  It is always 5 and WladyXX3740 claims on the Logitech forum that:
  "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably 
kernel related."

  Here is where most of the people are complaining:
  
https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639

  I discovered that this is related to my Logitech keyboard by running this 
command:
  xinput test-xi2 --root

  Here is the device list:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech K520   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech M310/M310t id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]

  And some extract from the output when this happens:
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags:
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 12 (PropertyEvent)
   property: 308 'Synaptics Off'
   changed: modified
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 

[Kernel-packages] [Bug 1592501] [NEW] "error while doing dist-upgrade from command line" package linux-image-extra-3.19.0-61-generic 3.19.0-61.69~14.04.1 failed to install/upgrade: subprocess installe

2016-06-14 Thread Ron Larson
Public bug reported:

error while trying to complete dist-upgrade via command line

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.19.0-61-generic 3.19.0-61.69~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19
Uname: Linux 3.19.0-59-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Tue Jun 14 13:48:13 2016
DpkgHistoryLog:
 
DpkgTerminalLog:
 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-12-10 (186 days ago)
InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.6
 apt  1.0.1ubuntu2.14
SourcePackage: linux-lts-vivid
Title: package linux-image-extra-3.19.0-61-generic 3.19.0-61.69~14.04.1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  "error while doing dist-upgrade from command line" package linux-
  image-extra-3.19.0-61-generic 3.19.0-61.69~14.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

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

Bug description:
  error while trying to complete dist-upgrade via command line

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.19.0-61-generic 3.19.0-61.69~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Tue Jun 14 13:48:13 2016
  DpkgHistoryLog:
   
  DpkgTerminalLog:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-12-10 (186 days ago)
  InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.14
  SourcePackage: linux-lts-vivid
  Title: package linux-image-extra-3.19.0-61-generic 3.19.0-61.69~14.04.1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1591329] alkaid (amd64) - tests ran: 136, failed: 0

2016-06-14 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/alkaid__3.2.0-105.146__2016-06-14_17-12-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards

2016-06-14 Thread Kamal Mostafa
Summary of test kernel results: All users of the test kernel have
reported that it does appear to eliminate the 5 problem.

I will get the fix patch ([mainline] 50220de HID: core: prevent out-of-
bound readings) into the pipeline for all affected Ubuntu kernels, and a
note will be posted here once those kernels become available.

Thanks all, for the testing help!

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

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  I have a K520 Logitech keyboard and sometimes something starts to keep 
pressing key 5.
  It mostly happens when I leave the computer alone for some time, but 
sometimes also just during regular usage.

  It seems that this is a Linux specific issue as no one is complaining
  about this issue under Windows, but a couple of people are complaining
  for different versions of Ubuntu.

  It is always 5 and WladyXX3740 claims on the Logitech forum that:
  "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably 
kernel related."

  Here is where most of the people are complaining:
  
https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639

  I discovered that this is related to my Logitech keyboard by running this 
command:
  xinput test-xi2 --root

  Here is the device list:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech K520   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech M310/M310t id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]

  And some extract from the output when this happens:
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags:
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 12 (PropertyEvent)
   property: 308 'Synaptics Off'
   changed: modified
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 

[Kernel-packages] [Bug 1591329] cavac (amd64) - tests ran: 21, failed: 1

2016-06-14 Thread Brad Figg
tests ran:  21, failed: 1;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/cavac__3.2.0-105.146__2016-06-14_15-42-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1591329] dagmar (amd64) - tests ran: 21, failed: 1

2016-06-14 Thread Brad Figg
tests ran:  21, failed: 1;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/dagmar__3.2.0-105.146__2016-06-14_15-32-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1591329] onza (amd64) - tests ran: 21, failed: 1

2016-06-14 Thread Brad Figg
tests ran:  21, failed: 1;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/onza__3.2.0-105.146__2016-06-14_15-30-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1572624] Re: Backport patch to abort syscalls in active transactions

2016-06-14 Thread Kamal Mostafa
** 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/1572624

Title:
  Backport patch to abort syscalls in active transactions

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

Bug description:
  == Comment: #0 - Tulio Magno Quites Machado Filho - 2016-02-23 12:47:09 ==
  ---Problem Description---
  This is happening on Ubuntu 14.04.3.
  User is creating stack structure using C++ transactional memory extension:

  int Pop(int)
  {
  int ret = 0;
  __transaction_atomic
  {
  if(!stack_.empty())
  {
  ret = stack_.top();
  stack_.pop();
  } else
  ret = -1;
  }
  return ret;
  }

  While evaluating if(!stack_.empty()), this code calls a libitm function (GCC 
code), which calls malloc (glibc code) which ends up calling futex (a syscall).
  A syscall inside a transaction is forbidden by the kernel, but there is 
nothing the user can do to avoid this syscall.

  This will hang the user application inside the malloc(), which would
  be waiting for the futex to return.

  Ubuntu 14.04 provides glibc 2.19, which is too old to know about HTM.
  And this is probably happening with other libraries as well.

  Backporting commit b4b56f9e would solve this issue.

  ---uname output---
  Linux 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 16:06:09 UTC 2015 ppc64le 
ppc64le ppc64le GNU/Linux
   
  ---Steps to Reproduce---
   Start a transaction, make a syscall.
   
  == Comment: #1 - Wei Guo - 2016-02-24 02:33:03 ==
  I already verfied that kernel with patch b4b56f9e (on Ubuntu14.04) will work.

  == Comment: #2 - Wei Guo - 2016-02-26 04:20:37 ==
  Backport patch for commit b4b56f9e is attached. The patch is based on tag 
Ubuntu-lts-3.19.0-25.26_14.04.1.

  Tested based on Ubuntu 14.04.4 LTS ( 3.19.0-25-generic).

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

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


[Kernel-packages] [Bug 1577024] Re: Kernel 4.2.X and 4.4.X - Fix USB3.0 link power management (LPM) claim/release logic in USBFS

2016-06-14 Thread Matthew Giassa
Tested successfully. Tags updated as requested.

Thank you.


Matthew Giassa, MASc, BASc, EIT
Security and Embedded Systems Specialist
linkedin: https://ca.linkedin.com/in/giassa
e-mail:   matt...@giassa.net
website:  www.giassa.net

>  Original Message 
> Subject: [Bug 1577024] Re: Kernel 4.2.X and 4.4.X - Fix USB3.0 link
> power management (LPM) claim/release logic in USBFS
> From: Kamal Mostafa 
> Date: Tue, June 14, 2016 7:21 am
> To: matt...@giassa.net
> 
> 
> This bug is awaiting verification that the kernel in -proposed solves
> the problem. Please test the kernel and update this bug with the
> results. If the problem is solved, change the tag 'verification-needed-
> xenial' to 'verification-done-xenial'.
> 
> If verification is not done by 5 working days from today, this fix will
> be dropped from the source code, and this bug will be closed.
> 
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
> to enable and use -proposed. Thank you!
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1577024
> 
> Title:
>   Kernel 4.2.X and 4.4.X - Fix USB3.0 link power management (LPM)
>   claim/release logic in USBFS
> 
> Status in linux package in Ubuntu:
>   Triaged
> Status in linux source package in Vivid:
>   Fix Committed
> Status in linux source package in Wily:
>   Fix Committed
> Status in linux source package in Xenial:
>   Fix Committed
> 
> Bug description:
>   I am currently carrying out kernel testing and debugging with Alan Stern on 
> the mainline kernel. Alan has proposed a patch to resolve a bug in USBFS that 
> causes USB machine vision cameras to fail on kernels that contain the 
> following patch:
>   commit e951f84074b84a3f5aecbffd01da74576e0068d5
>   Author: Lu Baolu 
>   Date:   Tue Jun 16 09:08:26 2015 +0800
>   usb: core: lpm: set lpm_capable for root hub device
>   commit 2d2a316765d956bc5cb6bb367b2ec52ca59ab8e9 upstream.
> 
>   There is an issue in this patch that impacts software that rapidly
>   issues claim/release calls in USBFS, and all of our customers that use
>   Ubuntu 14.04.4 (kernel 4.2.x) and Ubuntu 16.04 (kernel 4.4.x) are
>   unable to communicate with their machine vision cameras using our
>   software stack.
> 
>   The patch for the mainline kernel is being tested, and is currently posted, 
> along with a history of this issue, at:
>   https://bugzilla.kernel.org/show_bug.cgi?id=115961
> 
>   Right now, all of our customers have to either use an older kernel, or
>   manually patch their own kernel with the fix provided by Alan if they
>   are required to use a newer kernel. I am raising this bug so that,
>   once the patch is submitted to the the mainline/linus series, it can
>   be included in the next "monthly" kernel update made available to the
>   general public, and so our customers can just run a normal "vanilla"
>   system without having to rely on manually patching their kernel every
>   time they need to update.
> 
>   I can be contacted at:
>   matt...@giassa.net
>   matthew.gia...@ptgrey.com
> 
>   Thank you.
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.13.0-55-generic 3.13.0-55.94
>   ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
>   Uname: Linux 3.13.0-55-generic i686
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.14.1-0ubuntu3.19
>   Architecture: i386
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  owner  4035 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Sat Apr 30 10:36:15 2016
>   EcryptfsInUse: Yes
>   HibernationDevice: RESUME=UUID=0287e25d-68d6-4390-aced-c682b8e13b60
>   InstallationDate: Installed on 2013-09-23 (949 days ago)
>   InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
> (20130820.1)
>   IwConfig:
>lono wireless extensions.
>
>cscotun0  no wireless extensions.
>
>eth0  no wireless extensions.
>   MachineType: Hewlett-Packard HP xw4600 Workstation
>   ProcFB:
>
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic 
> root=UUID=292845c9-c333-4592-aa06-bc01f45d3ee6 ro quiet splash
>   RelatedPackageVersions:
>linux-restricted-modules-3.13.0-55-generic N/A
>linux-backports-modules-3.13.0-55-generic  N/A
>linux-firmware 1.127.19
>   RfKill:
>
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to trusty on 2014-07-30 (639 days ago)
>   dmi.bios.date: 07/09/2012
>   dmi.bios.vendor: Hewlett-Packard
>   dmi.bios.version: 786F3 v01.34
>   dmi.board.asset.tag: CAC94101JZ
>   dmi.board.name: 0AA0h
>   dmi.board.vendor: Hewlett-Packard
>   dmi.chassis.asset.tag: CAC94101JZ
>   dmi.chassis.type: 6
>   dmi.chassis.vendor: Hewlett-Packard
>   dmi.modalias: 
> 

[Kernel-packages] [Bug 1592481] [NEW] VMX kernel crypto module exhibits poor performance in Ubuntu 16.04

2016-06-14 Thread bugproxy
Public bug reported:

---Problem Description---
Pre-sales customer with loaner P8 observes slow performance of VMX-accelerated 
kernel crypto, multiple times slower then Haswell.
 
---uname output---
Linux crimini9 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:30:22 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = unknown 
 
---Steps to Reproduce---
 Run cryptsetup benchmark with the VMX crypto module modprobed.
 
Original customer cryptsetup benchmark results on Ubuntu 16.04:
 
Intel i5 core 2500k overclocked at 4.5 GHz w/ 4 cores:
aes-xts   256b  1884,2 MiB/s  1952,0 MiB/s
aes-cbc  256b   509,1 MiB/s  1724,2 MiB/s
 
Results for xeon e5-2680 at 2.80 Ghz:
 aes-cbc   256b   392.6 MiB/s  2062.0 MiB/s
 aes-xts   256b  3853.0 MiB/s  4793.0 MiB/s
 
Results from intel i7 3770 at 3.40 GHz:
aes-xts?? 256b??7787.0 MiB/s??7962.0 MiB/s
aes-cbc?? 256b?? 662.0 MiB/s??3779.0 MiB/s
 
Power 8 at 4.15Ghz and vmx-crypto loaded (s822L, 16c, powervm)
aes-xts   256b   410.7 MiB/s   413.9 MiB/s
aes-cbc   256b   300.6 MiB/s   358.7 MiB/s

Mirroring to Canonical for their awareness as IBM purses a fix for
inclusion in a 16.04 SRU.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-142541 severity-critical 
targetmilestone-inin16041

** Tags added: architecture-ppc64le bugnameltc-142541 severity-critical
targetmilestone-inin16041

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

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

Title:
  VMX kernel crypto module exhibits poor performance in Ubuntu 16.04

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Pre-sales customer with loaner P8 observes slow performance of 
VMX-accelerated kernel crypto, multiple times slower then Haswell.
   
  ---uname output---
  Linux crimini9 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:30:22 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = unknown 
   
  ---Steps to Reproduce---
   Run cryptsetup benchmark with the VMX crypto module modprobed.
   
  Original customer cryptsetup benchmark results on Ubuntu 16.04:
   
  Intel i5 core 2500k overclocked at 4.5 GHz w/ 4 cores:
  aes-xts   256b  1884,2 MiB/s  1952,0 MiB/s
  aes-cbc  256b   509,1 MiB/s  1724,2 MiB/s
   
  Results for xeon e5-2680 at 2.80 Ghz:
   aes-cbc   256b   392.6 MiB/s  2062.0 MiB/s
   aes-xts   256b  3853.0 MiB/s  4793.0 MiB/s
   
  Results from intel i7 3770 at 3.40 GHz:
  aes-xts?? 256b??7787.0 MiB/s??7962.0 MiB/s
  aes-cbc?? 256b?? 662.0 MiB/s??3779.0 MiB/s
   
  Power 8 at 4.15Ghz and vmx-crypto loaded (s822L, 16c, powervm)
  aes-xts   256b   410.7 MiB/s   413.9 MiB/s
  aes-cbc   256b   300.6 MiB/s   358.7 MiB/s

  Mirroring to Canonical for their awareness as IBM purses a fix for
  inclusion in a 16.04 SRU.

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

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


[Kernel-packages] [Bug 1584827] Re: s390/mm: fix asce_bits handling with dynamic pagetable levels

2016-06-14 Thread bugproxy
--- Comment From geral...@de.ibm.com 2016-06-14 12:30 EDT---
I verified that the kernel in -proposed (4.4.0-25.44) fixes the problem.

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

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

Title:
  s390/mm: fix asce_bits handling with dynamic pagetable levels

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #0 - Hendrik Brueckner  - 2016-05-23 
09:17:08 ==
  Please backport the following linux stable commit ID:

  linux-stable: https://git.kernel.org/cgit/linux/kernel/git/stable
  /linux-
  stable.git/commit/?h=linux-4.4.y=ce1bc448bac01edfccdc26d8318cfd39aa09e6e0

  
  s390/mm: fix asce_bits handling with dynamic pagetable levels
  commit 723cacbd9dc79582e562c123a0bacf8bfc69e72a upstream.

  There is a race with multi-threaded applications between context switch and
  pagetable upgrade. In switch_mm() a new user_asce is built from mm->pgd and
  mm->context.asce_bits, w/o holding any locks. A concurrent mmap with a
  pagetable upgrade on another thread in crst_table_upgrade() could already
  have set new asce_bits, but not yet the new mm->pgd. This would result in a
  corrupt user_asce in switch_mm(), and eventually in a kernel panic from a
  translation exception.

  Fix this by storing the complete asce instead of just the asce_bits, which
  can then be read atomically from switch_mm(), so that it either sees the
  old value or the new value, but no mixture. Both cases are OK. Having the
  old value would result in a page fault on access to the higher level memory,
  but the fault handler would see the new mm->pgd, if it was a valid access
  after the mmap on the other thread has completed. So as worst-case scenario
  we would have a page fault loop for the racing thread until the next time
  slice.

  Also remove dead code and simplify the upgrade/downgrade path, there are no
  upgrades from 2 levels, and only downgrades from 3 levels for compat tasks.
  There are also no concurrent upgrades, because the mmap_sem is held with
  down_write() in do_mmap, so the flush and table checks during upgrade can
  be removed.

  Reported-by: Michael Munday 
  Reviewed-by: Martin Schwidefsky 
  Signed-off-by: Gerald Schaefer 
  Signed-off-by: Martin Schwidefsky 
  Signed-off-by: Greg Kroah-Hartman 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1584827/+subscriptions

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


[Kernel-packages] [Bug 1591329] onibi (amd64) - tests ran: 21, failed: 1

2016-06-14 Thread Brad Figg
tests ran:  21, failed: 1;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/onibi__3.2.0-105.146__2016-06-14_14-47-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1591329] phact (amd64) - tests ran: 21, failed: 1

2016-06-14 Thread Brad Figg
tests ran:  21, failed: 1;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/phact__3.2.0-105.146__2016-06-14_15-00-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1592481] [NEW] VMX kernel crypto module exhibits poor performance in Ubuntu 16.04

2016-06-14 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

---Problem Description---
Pre-sales customer with loaner P8 observes slow performance of VMX-accelerated 
kernel crypto, multiple times slower then Haswell.
 
---uname output---
Linux crimini9 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:30:22 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = unknown 
 
---Steps to Reproduce---
 Run cryptsetup benchmark with the VMX crypto module modprobed.
 
Original customer cryptsetup benchmark results on Ubuntu 16.04:
 
Intel i5 core 2500k overclocked at 4.5 GHz w/ 4 cores:
aes-xts   256b  1884,2 MiB/s  1952,0 MiB/s
aes-cbc  256b   509,1 MiB/s  1724,2 MiB/s
 
Results for xeon e5-2680 at 2.80 Ghz:
 aes-cbc   256b   392.6 MiB/s  2062.0 MiB/s
 aes-xts   256b  3853.0 MiB/s  4793.0 MiB/s
 
Results from intel i7 3770 at 3.40 GHz:
aes-xts?? 256b??7787.0 MiB/s??7962.0 MiB/s
aes-cbc?? 256b?? 662.0 MiB/s??3779.0 MiB/s
 
Power 8 at 4.15Ghz and vmx-crypto loaded (s822L, 16c, powervm)
aes-xts   256b   410.7 MiB/s   413.9 MiB/s
aes-cbc   256b   300.6 MiB/s   358.7 MiB/s

Mirroring to Canonical for their awareness as IBM purses a fix for
inclusion in a 16.04 SRU.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-142541 severity-critical 
targetmilestone-inin16041
-- 
VMX kernel crypto module exhibits poor performance in Ubuntu 16.04
https://bugs.launchpad.net/bugs/1592481
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1584828] Re: s390/pci: fix use after free in dma_init

2016-06-14 Thread bugproxy
--- Comment From geral...@de.ibm.com 2016-06-14 12:31 EDT---
I verified that the kernel in -proposed (4.4.0-25.44) fixes the problem.

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

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

Title:
  s390/pci: fix use after free in dma_init

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #0 - Hendrik Brueckner  - 2016-05-23 
09:09:00 ==
  Please backport upstream Linux commit ID:

  commit dba599091c191d209b1499511a524ad9657c0e5a
  Author: Sebastian Ott 
  Date:   Fri Apr 15 09:41:35 2016 +0200

  s390/pci: fix use after free in dma_init
  
  After a failure during registration of the dma_table (because of the
  function being in error state) we free its memory but don't reset the
  associated pointer to zero.
  
  When we then receive a notification from firmware (about the function
  being in error state) we'll try to walk and free the dma_table again.
  
  Fix this by resetting the dma_table pointer. In addition to that make
  sure that we free the iommu_bitmap when appropriate.
  
  Signed-off-by: Sebastian Ott 
  Reviewed-by: Gerald Schaefer 
  Signed-off-by: Martin Schwidefsky 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1584828/+subscriptions

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


[Kernel-packages] [Bug 1591329] alkaid (amd64) - tests ran: 21, failed: 1

2016-06-14 Thread Brad Figg
tests ran:  21, failed: 1;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/alkaid__3.2.0-105.146__2016-06-14_14-55-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1583357] Re: [Hyper-V] Rebase Hyper-V to 4.6 kernel

2016-06-14 Thread Chris Valean
Thanks Joe!

I've tested your lp1583357 kernel with KVP and the results are looking good.
For the original 16.04 kernel and the rebase one to 4.6 the only issue open 
we're tracking is with kdump, but we have another ticket in which that is 
handled.

Otherwise the results for the 4.6 rebase kernel are good and the changes should 
be merged.
Thank you!

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

Title:
  [Hyper-V] Rebase Hyper-V to 4.6 kernel

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

Bug description:
  Please rebase Hyper-V support to the final v4.6 upstream kernel.

  The following files comprise Hyper-V support in the upstream kernel:
  arch/x86/kernel/cpu/mshyperv.c
  arch/x86/include/asm/mshyperv.h
  arch/x86/include/uapi/asm/hyperv.h
  include/linux/hyperv.h
  drivers/hv/channel.c
  drivers/hv/channel_mgmt.c
  drivers/hv/connection.c
  drivers/hv/hv_balloon.c
  drivers/hv/hv.c
  drivers/hv/hv_fcopy.c
  drivers/hv/hv_kvp.c
  drivers/hv/hv_snapshot.c
  drivers/hv/hv_util.c
  drivers/hv/hv_utils_transport.c
  drivers/hv/hv_utils_transport.h
  drivers/hv/hyperv_vmbus.h
  drivers/hv/ring_buffer.c
  drivers/hv/vmbus_drv.c
  tools/hv/hv_fcopy_daemon.c
  tools/hv/hv_get_dhcp_info.sh
  tools/hv/hv_get_dns_info.sh
  tools/hv/hv_kvp_daemon.c
  tools/hv/hv_set_ifconfig.sh
  tools/hv/hv_vss_daemon.c
  tools/hv/lsvmbus
  drivers/input/serio/hyperv-keyboard.c
  drivers/net/hyperv/hyperv_net.h
  drivers/net/hyperv/netvsc.c
  drivers/net/hyperv/netvsc_drv.c
  drivers/net/hyperv/rndis_filter.c
  drivers/scsi/storvsc_drv.c
  drivers/hid/hid-hyperv.c
  drivers/pci/host/pci-hyperv.c
  drivers/video/fbdev/hyperv_fb.c

  While I know a number of post-4.4 commits are already committed, I am
  including all of the commits from 4.4 to 4.6 for reference:

  mshyperv.c : commit 1e2ae9ec072f3b7887f456426bc2cf23b80f661a : 
x86/hyperv: Avoid reporting bogus NMI status for Gen2 instances
  mshyperv.c : commit 1b74dde7c47c19a73ea3e9fac95ac27b5d3d50c5 : x86/cpu: 
Convert printk(KERN_ ...) to pr_(...)
  hyperv.h : commit 45870a441361d1c05a5f767c4ece2f6e30e0da9c : Drivers: hv: 
ring_buffer: remove stray smp_read_barrier_depends()
  hyperv.h : commit e8d6ca023efce3bd80050dcd9e708ee3cf8babd4 : Drivers: hv: 
vmbus: define the new offer type for Hyper-V socket (hvsock)
  hyperv.h : commit 5c23a1a5c60b0f472cfa61cd7d8279f8aaeb5b64 : Drivers: hv: 
vmbus: define a new VMBus message type for hvsock
  hyperv.h : commit 499e8401a515d04daa986b995da710d2b9737764 : Drivers: hv: 
vmbus: add a per-channel rescind callback
  hyperv.h : commit 3c75354d043ad546148d6992e40033ecaefc5ea5 : Drivers: hv: 
vmbus: add a helper function to set a channel's pending send size
  hyperv.h : commit 8981da320a11217589aa3c50f9e891bcdef07ece : Drivers: hv: 
vmbus: add a hvsock flag in struct hv_driver
  hyperv.h : commit b9830d120cbe155863399f25eaef6aa8353e767f : Drivers: hv: 
util: Pass the channel information during the init call
  channel.c : commit 63d55b2aeb5e4faa170316fee73c3c47ea9268c7 : Drivers: 
hv: vmbus: serialize process_chn_event() and vmbus_close_internal()
  channel.c : commit 5c23a1a5c60b0f472cfa61cd7d8279f8aaeb5b64 : Drivers: 
hv: vmbus: define a new VMBus message type for hvsock
  channel.c : commit fe760e4d64fe5c17c39e86c410d41f6587ee88bc : Drivers: 
hv: vmbus: Give control over how the ring access is serialized
  channel.c : commit 8599846d73997cdbccf63f23394d871cfad1e5e6 : Drivers: 
hv: vmbus: Fix a Host signaling bug
  channel_mgmt.c : commit fe760e4d64fe5c17c39e86c410d41f6587ee88bc : 
Drivers: hv: vmbus: Give control over how the ring access is serialized
  channel_mgmt.c : commit 79fd8e706637a5c7c41f9498fe0fbfb437abfdc8 : 
Drivers: hv: vmbus: avoid infinite loop in init_vp_index()
  channel_mgmt.c : commit 75ff3a8a9168df750b5bd0589e897a6c0517a9f1 : 
Drivers: hv: vmbus: avoid wait_for_completion() on crash
  channel_mgmt.c : commit 5c23a1a5c60b0f472cfa61cd7d8279f8aaeb5b64 : 
Drivers: hv: vmbus: define a new VMBus message type for hvsock
  connection.c : commit d6f591e339d23f434efda11917da511870891472 : Drivers: 
hv: vmbus: channge vmbus_connection.channel_lock to mutex
  connection.c : commit 75ff3a8a9168df750b5bd0589e897a6c0517a9f1 : Drivers: 
hv: vmbus: avoid wait_for_completion() on crash
  connection.c : commit 1b807e1011af46a595ba46c75ad5e20ad7177af7 : Drivers: 
hv: vmbus: Cleanup vmbus_set_event()
  hv.c : commit a108393dbf764efb2405f21ca759806c65b8bc16 : drivers:hv: 
Export the API to invoke a hypercall on Hyper-V
  hv.c : commit c35b82ef0294ae5052120615f5cfcef17c5a6bf7 : drivers/hv: 
correct tsc page sequence invalid value
  hv.c : commit 9220e39b5c900c67ddcb517d52fe52d90fb5e3c8 : Drivers: hv: 
vmbus: fix build warning
  hv.c : commit 

[Kernel-packages] [Bug 1592042] Re: Unable to start guests with memballoon default.

2016-06-14 Thread ChristianEhrhardt
It is a kernel patch, so trying to fix the package assigning that was
done.

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

** No longer affects: libvirt (Ubuntu)

** Project changed: libvirt => 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/1592042

Title:
  Unable to start guests with memballoon default.

Status in linux:
  New
Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Frank R. Lefevre  - 2016-06-13 08:49:43 
==
  ---Problem Description---
  Please include the upstream fix for virtio_balloon: fix PFN format for 
virtio-1.
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=87c9403b0d1de4676b0bd273eea68fcf6de68e68
   
  Contact Information = lefe...@us.ibm.com, mi...@us.ibm.com 
   
  ---uname output---
  root@zs93k1g112005:~# uname -a Linux zs93k1g112005 4.4.0-22-generic 
#40-Ubuntu SMP Thu May 12 22:02:55 UTC 2016 s390x s390x s390x GNU/Linux
   
  Machine Type = 2964-701 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   Include memballoon statement in xml file, guest fails to boot.
   
  *Additional Instructions for lefe...@us.ibm.com, mi...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occurring on.

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

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


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

2016-06-14 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  btrfs related kernel threads blocked and not making progress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  I'm seeing messages like this in dmesg:

  [ 2400.951071] INFO: task btrfs-cleaner:325 blocked for more than 120 seconds.
  [ 2400.958293]   Not tainted 4.4.0-24-generic #43-Ubuntu
  [ 2400.963918] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2400.972037] btrfs-cleaner   D 880071f77ce8 0   325  2 
0x
  [ 2400.972049]  880071f77ce8 8800045ac020 88007a110c80 
88007d4b1900
  [ 2400.972062]  880071f78000 88007e31b9f0 88007e31b800 
88007e31b9f0
  [ 2400.972073]  0001 880071f77d00 81821b15 
880079a97950
  [ 2400.972088] Call Trace:
  [ 2400.972103]  [] schedule+0x35/0x80
  [ 2400.972163]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [ 2400.972174]  [] ? wake_atomic_t_function+0x60/0x60
  [ 2400.972225]  [] start_transaction+0x2cb/0x4c0 [btrfs]
  [ 2400.972276]  [] btrfs_start_transaction+0x18/0x20 [btrfs]
  [ 2400.972324]  [] btrfs_drop_snapshot+0x54f/0x830 [btrfs]
  [ 2400.972334]  [] ? __schedule+0x3b6/0xa30
  [ 2400.972385]  [] 
btrfs_clean_one_deleted_snapshot+0xb2/0x100 [btrfs]
  [ 2400.972435]  [] cleaner_kthread+0xcf/0x220 [btrfs]
  [ 2400.972484]  [] ? check_leaf+0x360/0x360 [btrfs]
  [ 2400.972493]  [] kthread+0xd8/0xf0
  [ 2400.972501]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [ 2400.972509]  [] ret_from_fork+0x3f/0x70
  [ 2400.972517]  [] ? kthread_create_on_node+0x1e0/0x1e0

  Also, Sometimes btrfs quota rescan will stop making progress on this
  system and never recover until a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.24.25
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-24-generic.
  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/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue Jun 14 08:40:00 2016
  EcryptfsInUse: Yes
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: NETGEAR ReadyNAS 314
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 psbdrmfb
  ProcKernelCmdLine: ro rootflags=subvol=ubuntu console=tty0 
console=ttyS0,115200n8 root=/dev/md127
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-02 (12 days ago)
  dmi.bios.date: 11/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  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: NETGEAR
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/05/2013:svnNETGEAR:pnReadyNAS314:pvr11/05/2013ReadyNAS-314V1.0:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnNETGEAR:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: ReadyNAS 314
  dmi.product.version: 11/05/2013 ReadyNAS-314 V1.0
  dmi.sys.vendor: NETGEAR

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

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


[Kernel-packages] [Bug 1592442] [NEW] Ubuntu 16.04 Xenial hard crashing on ACER E3-11-P0D8

2016-06-14 Thread Saif Taifur Anwar
Public bug reported:

About a month ago I installed the latest Ubuntu 16.04 Xenial on my ACER
E3-11-P0D8 laptop. Since then, it randomly freeze up while I work. It
generally takes 10-20 mins to do that.

Out of frustration, I started to change the kernel. It seems that every
>4.0 kernel is freezing up my system. Now i am stable at 3.19.8 from
here: http://kernel.ubuntu.com/~kernel-ppa/mainline/

Please note: When using old kernel ( 3.19.8 ) i have no crash. But when
i use the latest one, it freeze up and i can not use anything ( no
kernel panic, no terminal, nothing, keyboard mouse doesn't work ).

The freeze happens very randomly. It can take 5 mins or hours after
working. And it takes me to switch off the laptop and start it again.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-24-generic 4.4.0-24.43
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  saif   1431 F pulseaudio
Date: Tue Jun 14 20:39:57 2016
HibernationDevice: RESUME=UUID=f2e69a50-3159-4db7-be6b-10bc5072fc65
InstallationDate: Installed on 2016-05-14 (31 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b48a Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E3-112
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=665e2c47-366b-4bc0-9142-8ae6796d1b72 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:
 linux-restricted-modules-4.4.0-24-generic N/A
 linux-backports-modules-4.4.0-24-generic  N/A
 linux-firmware1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: R2
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.10:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E3-112
dmi.product.version: V1.10
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug xenial

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

Title:
  Ubuntu 16.04 Xenial hard crashing on ACER E3-11-P0D8

Status in linux package in Ubuntu:
  New

Bug description:
  About a month ago I installed the latest Ubuntu 16.04 Xenial on my
  ACER E3-11-P0D8 laptop. Since then, it randomly freeze up while I
  work. It generally takes 10-20 mins to do that.

  Out of frustration, I started to change the kernel. It seems that
  every >4.0 kernel is freezing up my system. Now i am stable at 3.19.8
  from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/

  Please note: When using old kernel ( 3.19.8 ) i have no crash. But
  when i use the latest one, it freeze up and i can not use anything (
  no kernel panic, no terminal, nothing, keyboard mouse doesn't work ).

  The freeze happens very randomly. It can take 5 mins or hours after
  working. And it takes me to switch off the laptop and start it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-24-generic 4.4.0-24.43
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  saif   1431 F pulseaudio
  Date: Tue Jun 14 20:39:57 2016
  HibernationDevice: RESUME=UUID=f2e69a50-3159-4db7-be6b-10bc5072fc65
  InstallationDate: Installed on 2016-05-14 (31 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b48a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E3-112
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=665e2c47-366b-4bc0-9142-8ae6796d1b72 ro quiet 

[Kernel-packages] [Bug 1592443] [NEW] [Ubuntu 16.10] CAPI flash (cxlflash) driver and CXL kernel services to support driver event notification

2016-06-14 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

This adds an afu_driver_ops structure with deliver_event callback. An
AFU driver such as cxlflash can fill this out and associate it with a
context to enable passing custom AFU specific events to userspace.

This also adds a new kernel API function cxl_context_pending_events(),
that the AFU driver can use to notify the cxl driver that new specific
events are ready to be delivered, and wake up anyone waiting on the
context wait queue.

The current count of AFU driver specific events is stored in the field
afu_driver_events of the context structure.

The cxl driver will check the afu_driver_events count during poll,
select, read, etc. calls to check if an AFU driver specific event is
pending, and will call deliver_event() to deliver that event. This way,
the cxl driver takes care of all the usual locking semantics around
these calls and handles all the generic cxl events, so that the AFU
driver only needs to worry about it's own events.

This is a kernel feature for Ubuntu 16.10

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-133692 severity-medium 
targetmilestone-inin1610
-- 
[Ubuntu 16.10] CAPI flash (cxlflash) driver and CXL kernel services to support 
driver event notification
https://bugs.launchpad.net/bugs/1592443
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1592461] [NEW] btrfs related kernel threads blocked and not making progress

2016-06-14 Thread Lawrence D'Anna
Public bug reported:


I'm seeing messages like this in dmesg:

[ 2400.951071] INFO: task btrfs-cleaner:325 blocked for more than 120 seconds.
[ 2400.958293]   Not tainted 4.4.0-24-generic #43-Ubuntu
[ 2400.963918] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 2400.972037] btrfs-cleaner   D 880071f77ce8 0   325  2 0x
[ 2400.972049]  880071f77ce8 8800045ac020 88007a110c80 
88007d4b1900
[ 2400.972062]  880071f78000 88007e31b9f0 88007e31b800 
88007e31b9f0
[ 2400.972073]  0001 880071f77d00 81821b15 
880079a97950
[ 2400.972088] Call Trace:
[ 2400.972103]  [] schedule+0x35/0x80
[ 2400.972163]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
[ 2400.972174]  [] ? wake_atomic_t_function+0x60/0x60
[ 2400.972225]  [] start_transaction+0x2cb/0x4c0 [btrfs]
[ 2400.972276]  [] btrfs_start_transaction+0x18/0x20 [btrfs]
[ 2400.972324]  [] btrfs_drop_snapshot+0x54f/0x830 [btrfs]
[ 2400.972334]  [] ? __schedule+0x3b6/0xa30
[ 2400.972385]  [] 
btrfs_clean_one_deleted_snapshot+0xb2/0x100 [btrfs]
[ 2400.972435]  [] cleaner_kthread+0xcf/0x220 [btrfs]
[ 2400.972484]  [] ? check_leaf+0x360/0x360 [btrfs]
[ 2400.972493]  [] kthread+0xd8/0xf0
[ 2400.972501]  [] ? kthread_create_on_node+0x1e0/0x1e0
[ 2400.972509]  [] ret_from_fork+0x3f/0x70
[ 2400.972517]  [] ? kthread_create_on_node+0x1e0/0x1e0

Also, Sometimes btrfs quota rescan will stop making progress on this
system and never recover until a reboot.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.24.25
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-24-generic.
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/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Tue Jun 14 08:40:00 2016
EcryptfsInUse: Yes
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: NETGEAR ReadyNAS 314
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 psbdrmfb
ProcKernelCmdLine: ro rootflags=subvol=ubuntu console=tty0 
console=ttyS0,115200n8 root=/dev/md127
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-24-generic N/A
 linux-backports-modules-4.4.0-24-generic  N/A
 linux-firmware1.157
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-06-02 (12 days ago)
dmi.bios.date: 11/05/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
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: NETGEAR
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/05/2013:svnNETGEAR:pnReadyNAS314:pvr11/05/2013ReadyNAS-314V1.0:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnNETGEAR:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: ReadyNAS 314
dmi.product.version: 11/05/2013 ReadyNAS-314 V1.0
dmi.sys.vendor: NETGEAR

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


** Tags: amd64 apport-bug xenial

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

Title:
  btrfs related kernel threads blocked and not making progress

Status in linux package in Ubuntu:
  New

Bug description:
  
  I'm seeing messages like this in dmesg:

  [ 2400.951071] INFO: task btrfs-cleaner:325 blocked for more than 120 seconds.
  [ 2400.958293]   Not tainted 4.4.0-24-generic #43-Ubuntu
  [ 2400.963918] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2400.972037] btrfs-cleaner   D 880071f77ce8 0   325  2 
0x
  [ 2400.972049]  880071f77ce8 8800045ac020 88007a110c80 
88007d4b1900
  [ 2400.972062]  880071f78000 88007e31b9f0 88007e31b800 
88007e31b9f0
  [ 2400.972073]  0001 880071f77d00 81821b15 
880079a97950
  [ 2400.972088] Call Trace:
  [ 2400.972103]  [] schedule+0x35/0x80
  [ 2400.972163]  [] wait_current_trans.isra.21+0xd3/0x120 
[btrfs]
  [ 2400.972174]  [] ? wake_atomic_t_function+0x60/0x60
  [ 2400.972225]  [] start_transaction+0x2cb/0x4c0 [btrfs]
  [ 2400.972276]  

[Kernel-packages] [Bug 1581132] Re: [Xenial] net: updates to ethtool and virtio_net for speed/duplex support

2016-06-14 Thread Andy Gospodarek
Confirmed that link speed/duplex/etc could set set with ethtool on
proposed kernel 4.4.0-25-generic.

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

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

Title:
  [Xenial] net: updates to ethtool and virtio_net for speed/duplex
  support

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

Bug description:
  Post 4.4, several changes landed upsteam to allow users to set interface
  speed for virtio_net backed devices.  This feature is extremely useful
  for those doing large-scale networking simulations where Ubuntu-based
  VMs are used to simulate hosts.  Not only does it allow hosts to report
  the same speed in simulations for monitoring tools, but it is required
  to simulate 802.3ad bonding where link-speed is reported to the peer
  device.  Without proper speed setting there are cases where establishing
  LACP adjacency is not possible.  

  After this patch setting the link speed and duplex now works just as one would
  expect.  I'm running the kernel that contains this patch for these commands:

  $ sudo ethtool -s enp0s8 speed 10 duplex full 
  $ sudo ethtool enp0s8
  Settings for enp0s8:
Supported ports: [ ]
Supported link modes:   Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Advertised link modes:  Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 10Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Link detected: yes

  I've already submitted patches to the kernel-team mailing list.  Those
  patches can be found in this thread: https://lists.ubuntu.com/archives
  /kernel-team/2016-May/077286.html

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

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

2016-06-14 Thread John Mazzie
This version is working as well.

-- 
You 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 1591329] cavac (i386) - tests ran: 1, failed: 0

2016-06-14 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/cavac__3.2.0-105.146__2016-06-14_14-35-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1531768] Re: [arm64] lockups when idle if tickless (nohz=on) is used

2016-06-14 Thread Martin Pitt
Oh noes! I'm still getting "task * blocked for more than 120 seconds"
hangs even with nohz=off :-( Is there another option which I could try?

** Changed in: auto-package-testing
   Status: Fix Released => 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/1531768

Title:
  [arm64] lockups when idle if tickless (nohz=on) is used

Status in Auto Package Testing:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1531768/+subscriptions

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


[Kernel-packages] [Bug 1591329] dagmar (i386) - tests ran: 1, failed: 0

2016-06-14 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/dagmar__3.2.0-105.146__2016-06-14_14-34-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1580355] Re: promote *_diag modules from linux-image-extra to linux-image

2016-06-14 Thread Tycho Andersen
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  promote *_diag modules from linux-image-extra to linux-image

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Hi,

  For checkpoint restore support via CRIU, we need to use the following
  modules:

  udp_diag
  tcp_diag
  inet_diag
  netlink_diag
  af_packet_diag
  unix_diag

  some of which aren't included in linux-image, requiring users to
  install linux-image-extra. It would be handy if these were in the main
  kernel package.

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

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


[Kernel-packages] [Bug 1585311] Re: [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

2016-06-14 Thread Chris Valean
Verified the lsvmbus tool functionality using the proposed kernel
4.4.0-25, marking this as done.

Thank you!

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

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

Title:
  [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Similar to the Hyper-V daemons that are in cloud-tools, please place
  the python script "lsvmbus" from the Linux kernel source tree in
  tools/hv in /usr/sbin

  This script will show the devices on the Hyper-V vmbus.

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

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


[Kernel-packages] [Bug 1581169] Re: kernel panic (General protection fault) on module hpsa (lockup_detected)

2016-06-14 Thread Eric Desrochers
** Tags removed: verification-needed-wily
** Tags added: verification-done-wily

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

Title:
  kernel panic (General protection fault) on module hpsa
  (lockup_detected)

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

Bug description:
  it has been brought to my attention the following:

  Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu

  When running an sosreport on HP DL380 gen8 machines running this
  kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes
  hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning
  block devices. These are machines with an onboard p420i and
  daughtercard p420 RAID controller, with each drive in a single raid0
  configuration. (unideal, but the machines do not boot when the card is
  in HBA mode).

  This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using
  sosreport.

  The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable
  solution - I have yet to see a prior issue in which the p420 would
  lock up on this version. One issue wit h this is HP 99% of the time
  will require an sosreport when we raise any hardware issues. I can no
  longer produce that on kernel 4.2 machines because they kernel panic.

  I can reproduce this consistently with several other machines in our
  environment. - please let me know if you would like more info.

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

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


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

2016-06-14 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  Ubuntu 16.04 Xenial hard crashing on ACER E3-11-P0D8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  About a month ago I installed the latest Ubuntu 16.04 Xenial on my
  ACER E3-11-P0D8 laptop. Since then, it randomly freeze up while I
  work. It generally takes 10-20 mins to do that.

  Out of frustration, I started to change the kernel. It seems that
  every >4.0 kernel is freezing up my system. Now i am stable at 3.19.8
  from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/

  Please note: When using old kernel ( 3.19.8 ) i have no crash. But
  when i use the latest one, it freeze up and i can not use anything (
  no kernel panic, no terminal, nothing, keyboard mouse doesn't work ).

  The freeze happens very randomly. It can take 5 mins or hours after
  working. And it takes me to switch off the laptop and start it again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-24-generic 4.4.0-24.43
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  saif   1431 F pulseaudio
  Date: Tue Jun 14 20:39:57 2016
  HibernationDevice: RESUME=UUID=f2e69a50-3159-4db7-be6b-10bc5072fc65
  InstallationDate: Installed on 2016-05-14 (31 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b48a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E3-112
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic.efi.signed 
root=UUID=665e2c47-366b-4bc0-9142-8ae6796d1b72 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:
   linux-restricted-modules-4.4.0-24-generic N/A
   linux-backports-modules-4.4.0-24-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: R2
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.10:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E3-112
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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


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

2016-06-14 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/onza__3.2.0-105.146__2016-06-14_14-40-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1592443] [NEW] [Ubuntu 16.10] CAPI flash (cxlflash) driver and CXL kernel services to support driver event notification

2016-06-14 Thread bugproxy
Public bug reported:

This adds an afu_driver_ops structure with deliver_event callback. An
AFU driver such as cxlflash can fill this out and associate it with a
context to enable passing custom AFU specific events to userspace.

This also adds a new kernel API function cxl_context_pending_events(),
that the AFU driver can use to notify the cxl driver that new specific
events are ready to be delivered, and wake up anyone waiting on the
context wait queue.

The current count of AFU driver specific events is stored in the field
afu_driver_events of the context structure.

The cxl driver will check the afu_driver_events count during poll,
select, read, etc. calls to check if an AFU driver specific event is
pending, and will call deliver_event() to deliver that event. This way,
the cxl driver takes care of all the usual locking semantics around
these calls and handles all the generic cxl events, so that the AFU
driver only needs to worry about it's own events.

This is a kernel feature for Ubuntu 16.10

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-133692 severity-medium 
targetmilestone-inin1610

** Tags added: architecture-ppc64le bugnameltc-133692 severity-medium
targetmilestone-inin1610

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

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

Title:
  [Ubuntu 16.10] CAPI flash (cxlflash) driver and CXL kernel services to
  support driver event notification

Status in linux package in Ubuntu:
  New

Bug description:
  This adds an afu_driver_ops structure with deliver_event callback. An
  AFU driver such as cxlflash can fill this out and associate it with a
  context to enable passing custom AFU specific events to userspace.

  This also adds a new kernel API function cxl_context_pending_events(),
  that the AFU driver can use to notify the cxl driver that new specific
  events are ready to be delivered, and wake up anyone waiting on the
  context wait queue.

  The current count of AFU driver specific events is stored in the field
  afu_driver_events of the context structure.

  The cxl driver will check the afu_driver_events count during poll,
  select, read, etc. calls to check if an AFU driver specific event is
  pending, and will call deliver_event() to deliver that event. This
  way, the cxl driver takes care of all the usual locking semantics
  around these calls and handles all the generic cxl events, so that the
  AFU driver only needs to worry about it's own events.

  This is a kernel feature for Ubuntu 16.10

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

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


[Kernel-packages] [Bug 1584890] Re: debian.master/.../getabis bogus warnings "inconsistant compiler versions" and "not a git repository"

2016-06-14 Thread Kamal Mostafa
** Tags removed: verification-needed-precise verification-needed-trusty 
verification-needed-vivid verification-needed-wily verification-needed-xenial
** Tags added: verification-done-precise verification-done-trusty 
verification-done-vivid verification-done-wily verification-done-xenial

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

Title:
  debian.master/.../getabis bogus warnings "inconsistant compiler
  versions" and "not a git repository"

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 Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  The debian.master/scripts/misc/getabis script always emits these false
  warnings/errors under normal use:

  WARNING: inconsistant compiler versions detected
  ... because the compiler version check code is wrong.

  fatal: Not a git repository (or any of the parent directories): .git
  ... because the script is normally run on a remote host via 
maint-startnewrelease.

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

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


[Kernel-packages] [Bug 1585311] Re: [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

2016-06-14 Thread Kamal Mostafa
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Similar to the Hyper-V daemons that are in cloud-tools, please place
  the python script "lsvmbus" from the Linux kernel source tree in
  tools/hv in /usr/sbin

  This script will show the devices on the Hyper-V vmbus.

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

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


[Kernel-packages] [Bug 1587091] Re: Extended statistics from balloon for proper memory management

2016-06-14 Thread Kamal Mostafa
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  Extended statistics from balloon for proper memory management

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-lts-utopic package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  There is QEMU/KVM and a Linux OS running inside the guest. 
  Inside the Linux guest a balloon consumes memory in accordance with 
  commands performed on the host side in QEMU and reports some statistics 
through memstat structure.
  For the Linux guest reported “free” value doesn’t describe the guest memory 
pressure at all.
  The provided patch set in Linux kernel extends the stat with available field.

  The problem is addressed in mainstream Linux with the following
  patchset:

  commit
  5057dcd0f1aaad57e07e728ba20a99e205c6b9de
  Author: Igor Redko 
  Date: Thu Mar 17 15:09:34 2016 -0700
  virtio_balloon: export 'available' memory to balloon statistics

  Add a new field, VIRTIO_BALLOON_S_AVAIL, to virtio_balloon memory
  statistics protocol, corresponding to 'Available' in /proc/meminfo.

  It indicates to the hypervisor how big the balloon can be inflated
  without pushing the guest system to swap.

  Signed-off-by: Igor Redko 
  Signed-off-by: Denis V. Lunev 
  Reviewed-by: Roman Kagan 
  Cc: Michael S. Tsirkin 
  Signed-off-by: Andrew Morton 
  Signed-off-by: Linus Torvalds 

  
  commit d02bd27bd33dd7e8d22594cd568b81be0cb584cd
  Author: Igor Redko 
  Date: Thu Mar 17 15:09:34 2016 -0700
  mm/page_alloc.c: calculate 'available' memory in a separate function

  Add a new field, VIRTIO_BALLOON_S_AVAIL, to virtio_balloon memory
  statistics protocol, corresponding to 'Available' in /proc/meminfo.

  It indicates to the hypervisor how big the balloon can be inflated
  without pushing the guest system to swap.  This metric would be very
  useful in VM orchestration software to improve memory management of
  different VMs under overcommit.

  This patch (of 2):

  Factor out calculation of the available memory counter into a separate
  exportable function, in order to be able to use it in other parts of the
  kernel.

  In particular, it appears a relevant metric to report to the hypervisor
  via virtio-balloon statistics interface (in a followup patch).

  Signed-off-by: Igor Redko 
  Signed-off-by: Denis V. Lunev 
  Reviewed-by: Roman Kagan 
  Cc: Michael S. Tsirkin 
  Signed-off-by: Andrew Morton 
  Signed-off-by: Linus Torvalds 

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

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


[Kernel-packages] [Bug 1584890] Re: debian.master/.../getabis bogus warnings "inconsistant compiler versions" and "not a git repository"

2016-06-14 Thread Kamal Mostafa
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-precise

** Tags added: verification-needed-trusty

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

Title:
  debian.master/.../getabis bogus warnings "inconsistant compiler
  versions" and "not a git repository"

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 Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  The debian.master/scripts/misc/getabis script always emits these false
  warnings/errors under normal use:

  WARNING: inconsistant compiler versions detected
  ... because the compiler version check code is wrong.

  fatal: Not a git repository (or any of the parent directories): .git
  ... because the script is normally run on a remote host via 
maint-startnewrelease.

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

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


[Kernel-packages] [Bug 1591329] alkaid (i386) - tests ran: 1, failed: 0

2016-06-14 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.2.0-105.146/alkaid__3.2.0-105.146__2016-06-14_14-08-00/results-index.html

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

Title:
  linux: 3.2.0-105.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-105.146 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: Promoted to proposed
  proposed-announcement-sent: true

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

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


[Kernel-packages] [Bug 1582991] Re: conflicting modules in udebs - arc4.ko

2016-06-14 Thread Kamal Mostafa
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  conflicting modules in udebs - arc4.ko

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  cryptop/arc4.ko appears to be in both nic-moudles and crypto-modules.

  Unpacking nic-modules-4.4.0-22-generic-di (4.4.0-22.40) ...
  dpkg: warning: overriding problem because --force enabled:
  dpkg: warning: trying to overwrite 
'/lib/modules/4.4.0-22-generic/kernel/crypto/arc4.ko', which is also in package 
crypto-modules-4.4.0-22-generic-di 4.4.0-22.40

  Not a problem per se, as d-i build just forces through this, but still
  ugly.

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

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


[Kernel-packages] [Bug 1584827] Re: s390/mm: fix asce_bits handling with dynamic pagetable levels

2016-06-14 Thread Kamal Mostafa
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  s390/mm: fix asce_bits handling with dynamic pagetable levels

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #0 - Hendrik Brueckner  - 2016-05-23 
09:17:08 ==
  Please backport the following linux stable commit ID:

  linux-stable: https://git.kernel.org/cgit/linux/kernel/git/stable
  /linux-
  stable.git/commit/?h=linux-4.4.y=ce1bc448bac01edfccdc26d8318cfd39aa09e6e0

  
  s390/mm: fix asce_bits handling with dynamic pagetable levels
  commit 723cacbd9dc79582e562c123a0bacf8bfc69e72a upstream.

  There is a race with multi-threaded applications between context switch and
  pagetable upgrade. In switch_mm() a new user_asce is built from mm->pgd and
  mm->context.asce_bits, w/o holding any locks. A concurrent mmap with a
  pagetable upgrade on another thread in crst_table_upgrade() could already
  have set new asce_bits, but not yet the new mm->pgd. This would result in a
  corrupt user_asce in switch_mm(), and eventually in a kernel panic from a
  translation exception.

  Fix this by storing the complete asce instead of just the asce_bits, which
  can then be read atomically from switch_mm(), so that it either sees the
  old value or the new value, but no mixture. Both cases are OK. Having the
  old value would result in a page fault on access to the higher level memory,
  but the fault handler would see the new mm->pgd, if it was a valid access
  after the mmap on the other thread has completed. So as worst-case scenario
  we would have a page fault loop for the racing thread until the next time
  slice.

  Also remove dead code and simplify the upgrade/downgrade path, there are no
  upgrades from 2 levels, and only downgrades from 3 levels for compat tasks.
  There are also no concurrent upgrades, because the mmap_sem is held with
  down_write() in do_mmap, so the flush and table checks during upgrade can
  be removed.

  Reported-by: Michael Munday 
  Reviewed-by: Martin Schwidefsky 
  Signed-off-by: Gerald Schaefer 
  Signed-off-by: Martin Schwidefsky 
  Signed-off-by: Greg Kroah-Hartman 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1584827/+subscriptions

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


  1   2   3   >