[Kernel-packages] [Bug 1675390] Re: touchpad stops responding erratically

[Amnon Yekutieli]

Since upgrade to KUBUNTU 17.04 trouble vitually gone

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

Title:
  touchpad stops responding erratically

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware: Dell XPW 13 2016 model no. 9360
  Touchpad  DLL075B:01 06CB:76AF Touchpad  
  OS KUBUNTU 

  Description:

  - The tochpad works ok for a while, then after some time it stops responding 
to finger input. 
  - There seems to be a correlation bwetween the touchpad failure and a running 
a heavy program, like LIBREOFFICE. 
  - Plugging in an extenral mouse is a solution (of sorts). 
  - After a while the touchapd resumea normal activity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xinput 1.6.2-1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Mar 23 14:28:24 2017
  InstallationDate: Installed on 2016-12-09 (104 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: xinput
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1690999] [NEW] linux: 4.11.0-3.8 -proposed tracker

[Seth Forshee]

Public bug reported:

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

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

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

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

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

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

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

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

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

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

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

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


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

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

** Tags added: block-proposed

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

** Tags added: artful

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

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

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

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

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

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

Title:
  linux: 4.11.0-3.8 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow 

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Wifi drops out RTL8821AE

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Have tried downloading and compiling driver, have tried
  /etc/modprobe.d/rtl8821ae.conf with combinations of options rtl8821ae
  fwlps swlps being Y, N, 1, and 0. None of the combinations works.

  WiFi comes up, lasts a few seconds - maybe up to a few minutes, then
  disconnects.

  Restarting the network manager service usually restores the connection
  for a few minutes, sometimes a reboot is required.

  Running a VPN over the wireless adapter causes the dropout to occur
  quicker.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-75-generic 4.4.0-75.96
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  1758 F pulseaudio
   /dev/snd/controlC1:  steve  1758 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 16 11:51:44 2017
  HibernationDevice: RESUME=UUID=395e6c11-8c59-45e8-85eb-2917c9588d7b
  InstallationDate: Installed on 2017-01-09 (126 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. P552LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic 
root=UUID=bedc4f01-09c8-407a-b5b9-5b2da87846f7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P552LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: P552LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP552LA.204:bd08/11/2015:svnASUSTeKCOMPUTERINC.:pnP552LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP552LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: P552LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1662316] Re: Asus GL553VE laptop keyboard backlight uncontrollable and Fn keys not working

[Kai-Heng Feng]

Please try 4.12-rc1 mainline kernel:

commit af22a610bc38508d5ea760507d31be6b6983dfa8
Author: Carlo Caione 
Date:   Thu Apr 6 12:18:17 2017 +0200

HID: asus: support backlight on USB keyboards

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

Title:
  Asus GL553VE laptop keyboard backlight uncontrollable and Fn keys not
  working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  There are problems with Asus GL553VE laptop Fn buttons and keyboard backlight
  1) Keyboard backlight uncontrollable
  2) Most FN keys don't work

  There is no way to control keyboard backlight at all (already tried
  all possible ways found in internet)

  Missing /sys/class/leds/asus::kbd_backlight (asus-nb-wmi modprobed)

  try all possible variants with acpi_osi and acpi_backlight from forum
  - no effect.

  Install kernel 4.9 and even 4.10 latest RC - no effect (only got
  control over airplane led).

  Keyboard backlight is always on or always off (last state from windows)
  Fn keys not working:
  F1(Zz Suspend) F2(Airplane) F3(Kb brightness down) F4(Kb brightness up)  
F5(Brightness down) F6(Brightness up) F7(Screen dim) F9(Touchpad disable)
  Workjng: Sound Mute + - (F10 F11 F12)

  Monitor backlight working fine by using menu slider.

  Tested on open and proprietary drivers from latest ppas

  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  Suggestion: asus-nb-wmi kernel module unable to detect hardware

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cabalbl4   1713 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Feb  6 23:18:11 2017
  HibernationDevice: RESUME=UUID=6ab6365a-c88a-4e64-a529-83b6a9a70e4e
  InstallationDate: Installed on 2017-02-05 (1 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 0bda:57f5 Realtek Semiconductor Corp.
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=18b6e8b1-63c2-4fb9-bdbb-5f9ffcc2d4cf ro quiet splash acpi_osi=Linux 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VE.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL553VE.208:bd11/08/2016:svnASUSTeKCOMPUTERINC.:pnGL553VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1672200] Re: Kernel error on i915 gpu driver

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel error on i915 gpu driver

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

Bug description:
  The following error (warning?) shows up in dmesg during every boot:

  [3.244312] [ cut here ]
  [3.244397] WARNING: CPU: 0 PID: 170 at 
/build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/i915/intel_fbdev.c:406 
intel_fb_initial_config+0x2d4/0x5f0 [i915]()
  [3.244410] WARN_ON(!encoder->crtc)
  [3.244413] Modules linked in:
  [3.244419]  i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt fb_sys_fops b44 drm ahci ssb psmouse pata_acpi libahci mii wmi fjes 
video
  [3.244451] CPU: 0 PID: 170 Comm: kworker/u4:6 Not tainted 
4.4.0-66-generic #87-Ubuntu
  [3.244462] Hardware name: Hewlett-Packard HP Compaq nx7400 
(RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006
  [3.244477] Workqueue: events_unbound async_run_entry_fn
  [3.244484]  c1adf967 ebf0fd93 0286 f5da5d04 c13ac15f f5da5d44 
f8d3b99c f5da5d34
  [3.244499]  c1070457 f8d46600 f5da5d64 00aa f8d3b99c 0196 
f8ceb9a4 f8ceb9a4
  [3.244514]   0001 0001 f5da5d50 c10704ce 0009 
f5da5d44 f8d46600
  [3.244530] Call Trace:
  [3.244541]  [] dump_stack+0x58/0x79
  [3.244550]  [] warn_slowpath_common+0x87/0xc0
  [3.244615]  [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244678]  [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244687]  [] warn_slowpath_fmt+0x3e/0x60
  [3.244750]  [] intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244759]  [] ? idr_alloc+0xa4/0x120
  [3.244823]  [] ? intel_crtc_fb_gamma_get+0x40/0x40 [i915]
  [3.244847]  [] drm_setup_crtcs+0x21f/0xa90 [drm_kms_helper]
  [3.244866]  [] ? 
drm_helper_probe_single_connector_modes_merge_bits+0x1e3/0x480 [drm_kms_helper]
  [3.244879]  [] ? schedule+0x2d/0x80
  [3.244898]  [] drm_fb_helper_initial_config+0xbc/0x400 
[drm_kms_helper]
  [3.244911]  [] ? put_prev_entity+0x33/0xcc0
  [3.244919]  [] ? pick_next_task_fair+0x501/0x520
  [3.244982]  [] intel_fbdev_initial_config+0x19/0x20 [i915]
  [3.244991]  [] async_run_entry_fn+0x4e/0x170
  [3.245000]  [] process_one_work+0x121/0x3f0
  [3.245009]  [] worker_thread+0x37/0x490
  [3.245017]  [] ? process_one_work+0x3f0/0x3f0
  [3.245025]  [] kthread+0xa6/0xc0
  [3.245034]  [] ret_from_kernel_thread+0x21/0x38
  [3.245042]  [] ? kthread_create_on_node+0x170/0x170
  [3.245049] ---[ end trace 0bd04c67fb0cdbfa ]---
  [3.251264] fbcon: inteldrmfb (fb0) is primary device
  [3.251911] [ cut here ]
  [3.251933] WARNING: CPU: 0 PID: 170 at 
/build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/drm_atomic_helper.c:723 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]()
  [3.251945] Modules linked in: i915 i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops b44 drm ahci ssb psmouse 
pata_acpi libahci mii wmi fjes video
  [3.251949] CPU: 0 PID: 170 Comm: kworker/u4:6 Tainted: GW   
4.4.0-66-generic #87-Ubuntu
  [3.251950] Hardware name: Hewlett-Packard HP Compaq nx7400 
(RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006
  [3.251956] Workqueue: events_unbound async_run_entry_fn
  [3.251962]  c1adf967 ebf0fd93 0286 f5da5b3c c13ac15f  
f85c51f0 f5da5b6c
  [3.251966]  c1070457 c19d054c  00aa f85c51f0 02d3 
f85bb98a f85bb98a
  [3.251970]  f67f8800  f07fc400 f5da5b7c c1070562 0009 
 f5da5ba4
  [3.251971] Call Trace:
  [3.251977]  [] dump_stack+0x58/0x79
  [3.251981]  [] warn_slowpath_common+0x87/0xc0
  [3.251994]  [] ? 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252007]  [] ? 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252010]  [] warn_slowpath_null+0x22/0x30
  [3.252023]  [] 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252023]  [] ? intel_pre_plane_update+0xd8/0x130 [i915]
  [3.252023]  [] intel_atomic_commit+0x52a/0x6a0 [i915]
  [3.252023]  [] ? drm_atomic_check_only+0x1ae/0x600 [drm]
  [3.252023]  [] ? drm_modeset_lock+0x49/0xd0 [drm]
  [3.252023]  [] ? drm_atomic_set_crtc_for_connector+0x5c/0xe0 
[drm]
  [3.252023]  [] drm_atomic_commit+0x32/0x60 [drm]
  [3.252023]  [] restore_fbdev_mode+0x253/0x290 [drm_kms_helper]
  [3.252023]  [] ? drm_modeset_lock_all_ctx+0x94/0xb0 [drm]
  [3.252023]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x27/0x70 

[Kernel-packages] [Bug 1672200] Re: Kernel error on i915 gpu driver

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel error on i915 gpu driver

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

Bug description:
  The following error (warning?) shows up in dmesg during every boot:

  [3.244312] [ cut here ]
  [3.244397] WARNING: CPU: 0 PID: 170 at 
/build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/i915/intel_fbdev.c:406 
intel_fb_initial_config+0x2d4/0x5f0 [i915]()
  [3.244410] WARN_ON(!encoder->crtc)
  [3.244413] Modules linked in:
  [3.244419]  i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt fb_sys_fops b44 drm ahci ssb psmouse pata_acpi libahci mii wmi fjes 
video
  [3.244451] CPU: 0 PID: 170 Comm: kworker/u4:6 Not tainted 
4.4.0-66-generic #87-Ubuntu
  [3.244462] Hardware name: Hewlett-Packard HP Compaq nx7400 
(RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006
  [3.244477] Workqueue: events_unbound async_run_entry_fn
  [3.244484]  c1adf967 ebf0fd93 0286 f5da5d04 c13ac15f f5da5d44 
f8d3b99c f5da5d34
  [3.244499]  c1070457 f8d46600 f5da5d64 00aa f8d3b99c 0196 
f8ceb9a4 f8ceb9a4
  [3.244514]   0001 0001 f5da5d50 c10704ce 0009 
f5da5d44 f8d46600
  [3.244530] Call Trace:
  [3.244541]  [] dump_stack+0x58/0x79
  [3.244550]  [] warn_slowpath_common+0x87/0xc0
  [3.244615]  [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244678]  [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244687]  [] warn_slowpath_fmt+0x3e/0x60
  [3.244750]  [] intel_fb_initial_config+0x2d4/0x5f0 [i915]
  [3.244759]  [] ? idr_alloc+0xa4/0x120
  [3.244823]  [] ? intel_crtc_fb_gamma_get+0x40/0x40 [i915]
  [3.244847]  [] drm_setup_crtcs+0x21f/0xa90 [drm_kms_helper]
  [3.244866]  [] ? 
drm_helper_probe_single_connector_modes_merge_bits+0x1e3/0x480 [drm_kms_helper]
  [3.244879]  [] ? schedule+0x2d/0x80
  [3.244898]  [] drm_fb_helper_initial_config+0xbc/0x400 
[drm_kms_helper]
  [3.244911]  [] ? put_prev_entity+0x33/0xcc0
  [3.244919]  [] ? pick_next_task_fair+0x501/0x520
  [3.244982]  [] intel_fbdev_initial_config+0x19/0x20 [i915]
  [3.244991]  [] async_run_entry_fn+0x4e/0x170
  [3.245000]  [] process_one_work+0x121/0x3f0
  [3.245009]  [] worker_thread+0x37/0x490
  [3.245017]  [] ? process_one_work+0x3f0/0x3f0
  [3.245025]  [] kthread+0xa6/0xc0
  [3.245034]  [] ret_from_kernel_thread+0x21/0x38
  [3.245042]  [] ? kthread_create_on_node+0x170/0x170
  [3.245049] ---[ end trace 0bd04c67fb0cdbfa ]---
  [3.251264] fbcon: inteldrmfb (fb0) is primary device
  [3.251911] [ cut here ]
  [3.251933] WARNING: CPU: 0 PID: 170 at 
/build/linux-Nasqxe/linux-4.4.0/drivers/gpu/drm/drm_atomic_helper.c:723 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]()
  [3.251945] Modules linked in: i915 i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops b44 drm ahci ssb psmouse 
pata_acpi libahci mii wmi fjes video
  [3.251949] CPU: 0 PID: 170 Comm: kworker/u4:6 Tainted: GW   
4.4.0-66-generic #87-Ubuntu
  [3.251950] Hardware name: Hewlett-Packard HP Compaq nx7400 
(RB525UT#ABA)/30A2, BIOS 68YGU Ver. F.07 07/28/2006
  [3.251956] Workqueue: events_unbound async_run_entry_fn
  [3.251962]  c1adf967 ebf0fd93 0286 f5da5b3c c13ac15f  
f85c51f0 f5da5b6c
  [3.251966]  c1070457 c19d054c  00aa f85c51f0 02d3 
f85bb98a f85bb98a
  [3.251970]  f67f8800  f07fc400 f5da5b7c c1070562 0009 
 f5da5ba4
  [3.251971] Call Trace:
  [3.251977]  [] dump_stack+0x58/0x79
  [3.251981]  [] warn_slowpath_common+0x87/0xc0
  [3.251994]  [] ? 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252007]  [] ? 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252010]  [] warn_slowpath_null+0x22/0x30
  [3.252023]  [] 
drm_atomic_helper_update_legacy_modeset_state+0x26a/0x280 [drm_kms_helper]
  [3.252023]  [] ? intel_pre_plane_update+0xd8/0x130 [i915]
  [3.252023]  [] intel_atomic_commit+0x52a/0x6a0 [i915]
  [3.252023]  [] ? drm_atomic_check_only+0x1ae/0x600 [drm]
  [3.252023]  [] ? drm_modeset_lock+0x49/0xd0 [drm]
  [3.252023]  [] ? drm_atomic_set_crtc_for_connector+0x5c/0xe0 
[drm]
  [3.252023]  [] drm_atomic_commit+0x32/0x60 [drm]
  [3.252023]  [] restore_fbdev_mode+0x253/0x290 [drm_kms_helper]
  [3.252023]  [] ? drm_modeset_lock_all_ctx+0x94/0xb0 [drm]
  [3.252023]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x27/0x70 [drm_kms_helper]
  [   

[Kernel-packages] [Bug 1644295] Re: Freeze after suspend

[Launchpad Bug Tracker]

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

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

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

Title:
  Freeze after suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello there,

  I came back from here and start the computer, which was suspended. I
  filled my password, enter into my account and then froze, I could not
  do anything neither the keyboard nor the mouse, was totally frozen.

  I waited a few minutes, there was no change and then I tried enforced
  restart by Alt + Print Screen + B.

  Very rarely I have exactly this problem, but I never knew exactly what
  you might needed as log files and information, so I proceed further to
  the next time. This time I decided to cooperate.

  I don't know what exactly should I provide, except /var/log/kern.log , so I 
attached it. Here is a note: I looked at this log file and would like to point 
that everything started right here:
  Nov 23 18:09:28 PC kernel: [43931.580063] PM: Syncing filesystems ... done.

  It seems I started my PC at 18:09:28 .

  I'll be glad if you helped to discover where the problem comes from.

  My distribution is Ubuntu MATE 16.10, up-to-date.

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

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

[Kernel-packages] [Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

[Kai-Heng Feng]

If this still happens on latest mainline kernel, you need to raise the
issue to linux-usb mailing list.

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

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

Title:
  Call Trace disabling IRQ 17, affects USB mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [  477.964736] Call Trace:
  [  477.964738][] dump_stack+0x63/0x90
  [  477.964750]  [] __report_bad_irq+0x33/0xc0
  [  477.964753]  [] note_interrupt+0x247/0x290
  [  477.964756]  [] handle_irq_event_percpu+0x167/0x1d0
  [  477.964758]  [] handle_irq_event+0x3e/0x60
  [  477.964761]  [] handle_fasteoi_irq+0x96/0x150
  [  477.964765]  [] handle_irq+0x1a/0x30
  [  477.964769]  [] do_IRQ+0x4b/0xd0
  [  477.964772]  [] common_interrupt+0x82/0x82
  [  477.964773][] ? mwait_idle+0x76/0x180
  [  477.964780]  [] arch_cpu_idle+0xf/0x20
  [  477.964784]  [] default_idle_call+0x2a/0x40
  [  477.964786]  [] cpu_startup_entry+0x2f1/0x350
  [  477.964790]  [] start_secondary+0x154/0x190
  [  477.964792] handlers:
  [  477.964796] [] usb_hcd_irq
  [  477.964798] [] usb_hcd_irq
  [  477.964802] [] ata_bmdma_interrupt
  [  477.964804] Disabling IRQ #17

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  js13126 F pulseaudio
  Date: Mon Aug  8 09:47:58 2016
  HibernationDevice: RESUME=UUID=62dbd34f-d371-4ae5-8687-e061a2ff9ec0
  InstallationDate: Installed on 2016-04-24 (105 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=1ac1bc6f-01e2-4f75-8a7c-3c2586ae7d6a ro
  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-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0572.2009.0715.2346
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-209
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0572.2009.0715.2346:bd07/15/2009:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-209:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested

[Kai-Heng Feng]

See if removing "pcie_aspm=force" helps.

Why do you need "i8042.nopnp" and "atkbd.reset"? Most Dell laptop should
work out of the box, those kernel parameters are not required.

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

Title:
  iwlwifi queue stuck, Microcode SW error detected,  "ieee80211 phy0:
  Hardware restart was requested

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently (maybe since updating to linux-image-4.4.0-34-generic:amd64
  (4.4.0-34.53), i've not used this notebook to much lately), my wifi
  connection is unstable, often hangs and therefore spread a lot of bad
  karma to all networking applications. My log shows entries of the
  following pattern

  Aug 22 20:12:56 nb-voer kernel: [ 1792.518944] iwlwifi :02:00.0: Queue 2 
stuck for 1 ms.
  Aug 22 20:12:56 nb-voer kernel: [ 1792.518962] iwlwifi :02:00.0: Current 
SW read_ptr 86 write_ptr 124
  Aug 22 20:12:56 nb-voer kernel: [ 1792.518999] iwl data: : 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00  
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519024] iwlwifi :02:00.0: FH 
TRBs(0) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519037] iwlwifi :02:00.0: FH 
TRBs(1) = 0x80102065
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519050] iwlwifi :02:00.0: FH 
TRBs(2) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519062] iwlwifi :02:00.0: FH 
TRBs(3) = 0x8031
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519075] iwlwifi :02:00.0: FH 
TRBs(4) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519088] iwlwifi :02:00.0: FH 
TRBs(5) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519100] iwlwifi :02:00.0: FH 
TRBs(6) = 0x
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519113] iwlwifi :02:00.0: FH 
TRBs(7) = 0x00709052
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519163] iwlwifi :02:00.0: Q 0 is 
active and mapped to fifo 3 ra_tid 0x [2,2]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519213] iwlwifi :02:00.0: Q 1 is 
active and mapped to fifo 2 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519265] iwlwifi :02:00.0: Q 2 is 
active and mapped to fifo 1 ra_tid 0x [86,124]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519326] iwlwifi :02:00.0: Q 3 is 
active and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519376] iwlwifi :02:00.0: Q 4 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519426] iwlwifi :02:00.0: Q 5 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519476] iwlwifi :02:00.0: Q 6 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519526] iwlwifi :02:00.0: Q 7 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519576] iwlwifi :02:00.0: Q 8 is 
active and mapped to fifo 3 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519626] iwlwifi :02:00.0: Q 9 is 
active and mapped to fifo 7 ra_tid 0x [83,83]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519676] iwlwifi :02:00.0: Q 10 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519726] iwlwifi :02:00.0: Q 11 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519776] iwlwifi :02:00.0: Q 12 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519826] iwlwifi :02:00.0: Q 13 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519876] iwlwifi :02:00.0: Q 14 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519925] iwlwifi :02:00.0: Q 15 is 
active and mapped to fifo 5 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.519975] iwlwifi :02:00.0: Q 16 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520025] iwlwifi :02:00.0: Q 17 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520075] iwlwifi :02:00.0: Q 18 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520125] iwlwifi :02:00.0: Q 19 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520175] iwlwifi :02:00.0: Q 20 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520225] iwlwifi :02:00.0: Q 21 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520275] iwlwifi :02:00.0: Q 22 is 
inactive and mapped to fifo 0 ra_tid 0x [0,0]
  Aug 22 20:12:56 nb-voer kernel: [ 1792.520324] iwlwifi :02:00.0: Q 23 is 
inactive 

[Kernel-packages] [Bug 1690984] [NEW] Wifi drops out RTL8821AE

[Steve]

Public bug reported:

Have tried downloading and compiling driver, have tried
/etc/modprobe.d/rtl8821ae.conf with combinations of options rtl8821ae
fwlps swlps being Y, N, 1, and 0. None of the combinations works.

WiFi comes up, lasts a few seconds - maybe up to a few minutes, then
disconnects.

Restarting the network manager service usually restores the connection
for a few minutes, sometimes a reboot is required.

Running a VPN over the wireless adapter causes the dropout to occur
quicker.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-75-generic 4.4.0-75.96
ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
Uname: Linux 4.4.0-75-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  steve  1758 F pulseaudio
 /dev/snd/controlC1:  steve  1758 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 16 11:51:44 2017
HibernationDevice: RESUME=UUID=395e6c11-8c59-45e8-85eb-2917c9588d7b
InstallationDate: Installed on 2017-01-09 (126 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: ASUSTeK COMPUTER INC. P552LA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic 
root=UUID=bedc4f01-09c8-407a-b5b9-5b2da87846f7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-75-generic N/A
 linux-backports-modules-4.4.0-75-generic  N/A
 linux-firmware1.157.8
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P552LA.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: P552LA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP552LA.204:bd08/11/2015:svnASUSTeKCOMPUTERINC.:pnP552LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP552LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: P552LA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  Wifi drops out RTL8821AE

Status in linux package in Ubuntu:
  New

Bug description:
  Have tried downloading and compiling driver, have tried
  /etc/modprobe.d/rtl8821ae.conf with combinations of options rtl8821ae
  fwlps swlps being Y, N, 1, and 0. None of the combinations works.

  WiFi comes up, lasts a few seconds - maybe up to a few minutes, then
  disconnects.

  Restarting the network manager service usually restores the connection
  for a few minutes, sometimes a reboot is required.

  Running a VPN over the wireless adapter causes the dropout to occur
  quicker.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-75-generic 4.4.0-75.96
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  1758 F pulseaudio
   /dev/snd/controlC1:  steve  1758 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 16 11:51:44 2017
  HibernationDevice: RESUME=UUID=395e6c11-8c59-45e8-85eb-2917c9588d7b
  InstallationDate: Installed on 2017-01-09 (126 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. P552LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic 
root=UUID=bedc4f01-09c8-407a-b5b9-5b2da87846f7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P552LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: P552LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP552LA.204:bd08/11/2015:svnASUSTeKCOMPUTERINC.:pnP552LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP552LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: P552LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1690321] Re: Fix CVE-2017-7294

[Po-Hsu Lin]

** Changed in: linux (Ubuntu Precise)
   Status: Incomplete => In Progress

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

Title:
  Fix CVE-2017-7294

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Precise:
  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 Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Tracking bug for fixing CVE-2017-7294

  Affected file: drivers/gpu/drm/vmwgfx/vmwgfx_surface.c
  Fix: e7e11f99564222d82f0ce84bd521e57d78a6b678

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

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

[Kernel-packages] [Bug 1690980] [NEW] No pop-up window to warn users that system should not reboot or shutdown while installing security updates

[ethan.hsieh]

Public bug reported:

Title: No pop-up window to warn users that system should not reboot or
shutdown while installing security updates

Summary:
No pop-up window to warn users that system should not reboot or shutdown while 
installing security updates

Steps:
1. trigger unattended-upgrades
2. reboot or shutdown system while installing packages

Expected results: There is a pop-up window to warn users that system
should not reboot or shutdown

Actual results: There is no pop-up window to warn users

Additional information:
$ apt-cache policy unattended-upgrades
unattended-upgrades:
  Installed: 0.90
  Candidate: 0.90ubuntu0.5
$ lsb_release -rd
Description:Ubuntu 16.04 LTS

** Affects: unattended-upgrades
 Importance: Undecided
 Status: New

** Also affects: unattended-upgrades
   Importance: Undecided
   Status: New

** No longer affects: bluez (Ubuntu)

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

Title:
  No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

Status in unattended-upgrades:
  New

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1690980/+subscriptions

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[Kai-Heng Feng]

I can confirm above two new incident. I still encountered this issue
after 3 days on a Precision 5510.

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1690956] Re: linux: 4.8.0-53.56 -proposed tracker

[Brad Figg]

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

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1690957
  derivatives: 1690958
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Tuesday, 16. May 2017 01:01 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1690957
  derivatives: 1690958
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Tuesday, 16. May 2017 01:01 UTC
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.8.0-53.56 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1690957
  derivatives: 1690958
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Tuesday, 16. May 2017 01:01 UTC

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux-hwe (Ubuntu Yakkety)
   Status: Confirmed => Fix Committed

** Changed in: linux-hwe-edge (Ubuntu Yakkety)
   Status: Confirmed => Fix Committed

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10
  in XENIAL LTS

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux-hwe source package in Yakkety:
  Fix Committed
Status in linux-hwe-edge source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1690956] Re: linux: 4.8.0-53.56 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.8.0-53.56 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  linux: 4.8.0-53.56 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1690957
  derivatives: 1690958

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

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

[Kernel-packages] [Bug 1662316] Re: Asus GL553VE laptop keyboard backlight uncontrollable and Fn keys not working

[shivang patel]

Same as above, I am facing same problems and in addition another problem
is battery dry in very fast.

My System : Asus FX553VD laptop(intel i7-7700HQ, nvidia-1050)

Linux shivangpatel 4.10.11-041011-generic #201704180310 SMP Tue Apr 18
07:12:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

 
Keyboard backlight is always on.

Fn keys not working:
F1(Zz Suspend) F2(Airplane) F3(Kb brightness down) F4(Kb brightness up) 
F5(Brightness down) F6(Brightness up) F7(Screen dim) F9(Touchpad disable)

Fn keys working:
Sound Mute + - (F10 F11 F12)

Monitor backlight working fine by using menu slider(in setting).

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

Title:
  Asus GL553VE laptop keyboard backlight uncontrollable and Fn keys not
  working

Status in linux package in Ubuntu:
  Triaged

Bug description:
  There are problems with Asus GL553VE laptop Fn buttons and keyboard backlight
  1) Keyboard backlight uncontrollable
  2) Most FN keys don't work

  There is no way to control keyboard backlight at all (already tried
  all possible ways found in internet)

  Missing /sys/class/leds/asus::kbd_backlight (asus-nb-wmi modprobed)

  try all possible variants with acpi_osi and acpi_backlight from forum
  - no effect.

  Install kernel 4.9 and even 4.10 latest RC - no effect (only got
  control over airplane led).

  Keyboard backlight is always on or always off (last state from windows)
  Fn keys not working:
  F1(Zz Suspend) F2(Airplane) F3(Kb brightness down) F4(Kb brightness up)  
F5(Brightness down) F6(Brightness up) F7(Screen dim) F9(Touchpad disable)
  Workjng: Sound Mute + - (F10 F11 F12)

  Monitor backlight working fine by using menu slider.

  Tested on open and proprietary drivers from latest ppas

  lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  Suggestion: asus-nb-wmi kernel module unable to detect hardware

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-62-generic 4.4.0-62.83
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cabalbl4   1713 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Feb  6 23:18:11 2017
  HibernationDevice: RESUME=UUID=6ab6365a-c88a-4e64-a529-83b6a9a70e4e
  InstallationDate: Installed on 2017-02-05 (1 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 0bda:57f5 Realtek Semiconductor Corp.
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=18b6e8b1-63c2-4fb9-bdbb-5f9ffcc2d4cf ro quiet splash acpi_osi=Linux 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VE.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL553VE.208:bd11/08/2016:svnASUSTeKCOMPUTERINC.:pnGL553VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1690956] [NEW] linux: -proposed tracker

[Thadeu Lima de Souza Cascardo]

Public bug reported:

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

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

backports: 1690957
derivatives: 1690958

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

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

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

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

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


** Tags: block-proposed-yakkety kernel-release-tracking-bug 
kernel-sru-cycle-2017.04.25-2 kernel-sru-master-kernel yakkety

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

** Tags added: block-proposed-yakkety

** Tags added: yakkety

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

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

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

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

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

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

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

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

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

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

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: 

[Kernel-packages] [Bug 1577057] Re: zfs initrd script fails when rootdelay boot option is set

[Richard Laager]

This has presumably regressed in 17.04 as they replaced the initrd code
(somewhat by accident). I'm going to review all this stuff and get some
fixes in soon, so it should be re-fixed by the next LTS.

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

Title:
  zfs initrd script fails when rootdelay boot option is set

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  It looks like that, when booting off zfs (zfs holds /boot) with the
  rootdelay boot option set, the boot process fails in the initrd fase,
  asking to manually import the pool using zpool import -f -R / -N. I
  only had one system with that parameter set, which I seldom reboot.

  I did not find an upstream reference of this bug or behavior.

  The error is caused by the fact the pool is already imported: "zpool
  status" executed on the initramfs prompt will correctly list the pool
  and all devices online. To continue, one has to export the pool, re-
  import it and exit the initramfs prompt after which regular booting
  continues. Not exporting and reimporting it leaves the pool readonly
  leading to boot errors further down the road (systemd units failing).

  I noticed zfs_autoimport_disable is set to 1 in the initramfs
  environment, so looking at /usr/share/initramfs-tools/scripts/zfs this
  section might be the issue (zpool import succeeding, but $ZFS_HEALTH
  never returning with the correct status (I'm not a programmer but
  perhaps ZFS_HEALTH is a local variable in the zfs_test_import
  function)):

   delay=${ROOTDELAY:-0}

   if [ "$delay" -gt 0 ]
   then
    # Try to import the pool read-only.  If it does not import with
    # the ONLINE status, wait and try again.  The pool could be
    # DEGRADED because a drive is really missing, or it might just
    # be slow to be detected.
    zfs_test_import
    retry_nr=0
    while [ "$retry_nr" -lt "$delay" ] && [ "$ZFS_HEALTH" != "ONLINE" ]
    do
     [ "$quiet" != "y" ] && log_begin_msg "Retrying ZFS read-only import"
     /bin/sleep 1
     zfs_test_import
     retry_nr=$(( $retry_nr + 1 ))
     [ "$quiet" != "y" ] && log_end_msg
    done
    unset retry_nr
    unset ZFS_HEALTH
   fi
   unset delay

  
  Edit: to be clear: I removed the rootdelay parameter, regenerated the initrd, 
and was able to boot successfully afterwards.

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

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

[Kernel-packages] [Bug 1577057] Re: zfs initrd script fails when rootdelay boot option is set

[dreamcat4]

Hi. Just to say thanks for fixing this. However the bug has occured for
me very recently on 16.04 LTS. Both 16.04.1 (4.4 kernel) and 16.04.2
(4.8 kernel).

So at this time this was not fixed for 16.04. Which aligns with the 'no
fix target' here for '16.04' in the bug description. Anyhow regardless
of that it is still a great help, and has solved my issue, just to
simply remove the 'rootdelay=' parameter from boot flags. Many thanks.

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

Title:
  zfs initrd script fails when rootdelay boot option is set

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  It looks like that, when booting off zfs (zfs holds /boot) with the
  rootdelay boot option set, the boot process fails in the initrd fase,
  asking to manually import the pool using zpool import -f -R / -N. I
  only had one system with that parameter set, which I seldom reboot.

  I did not find an upstream reference of this bug or behavior.

  The error is caused by the fact the pool is already imported: "zpool
  status" executed on the initramfs prompt will correctly list the pool
  and all devices online. To continue, one has to export the pool, re-
  import it and exit the initramfs prompt after which regular booting
  continues. Not exporting and reimporting it leaves the pool readonly
  leading to boot errors further down the road (systemd units failing).

  I noticed zfs_autoimport_disable is set to 1 in the initramfs
  environment, so looking at /usr/share/initramfs-tools/scripts/zfs this
  section might be the issue (zpool import succeeding, but $ZFS_HEALTH
  never returning with the correct status (I'm not a programmer but
  perhaps ZFS_HEALTH is a local variable in the zfs_test_import
  function)):

   delay=${ROOTDELAY:-0}

   if [ "$delay" -gt 0 ]
   then
    # Try to import the pool read-only.  If it does not import with
    # the ONLINE status, wait and try again.  The pool could be
    # DEGRADED because a drive is really missing, or it might just
    # be slow to be detected.
    zfs_test_import
    retry_nr=0
    while [ "$retry_nr" -lt "$delay" ] && [ "$ZFS_HEALTH" != "ONLINE" ]
    do
     [ "$quiet" != "y" ] && log_begin_msg "Retrying ZFS read-only import"
     /bin/sleep 1
     zfs_test_import
     retry_nr=$(( $retry_nr + 1 ))
     [ "$quiet" != "y" ] && log_end_msg
    done
    unset retry_nr
    unset ZFS_HEALTH
   fi
   unset delay

  
  Edit: to be clear: I removed the rootdelay parameter, regenerated the initrd, 
and was able to boot successfully afterwards.

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Woody]

I'd return my board if I could, but I can't (had to wait 2+weeks for
other parts to arrive before I started build).

Anyone have a good kernel compilation guide (or even just paste their
commands I would be grateful for) so that I can build up-to-date
official kernels with AMD_PINCTRL disabled? I tried various guides
carefully, all failed. The problem always appears to be that this
debian/ directory does not exist in my kernel source code folder.

Thanks,

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Joseph Salisbury]

Sorry for the delay.

I built the next test kernel, up to the following commit:
834a61d455ff8069552f44140b2c1de85e6bc84d

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1686636/834a61d455ff8069552f44140b2c1de85e6bc84d

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  outgoing tcp connections sometimes fail to be established

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

Bug description:
  I spend the better part of a day debugging this.

  Symptom: Outgoing connections (ssh, tcp to port 80, to port 8080) fail
  to establish about 25% of my attempts.

  I then switched the kernel from 
  linux-image-4.10.0-20-generic (zesty)
  back to
  linux-image-4.8.0-49-generic (yakkety)

  and those problems were gone. I have no iptables rules on my system.
  I'm using an e1000e over gigabit wired network.

  Attached is a tcpdump of a connection attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.8.0-49.52-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hildeb 3286 F pulseaudio
   /dev/snd/controlC1:  hildeb 3286 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Thu Apr 27 10:42:04 2017
  HibernationDevice: RESUME=UUID=d5037585-3853-4049-a410-b17d0c104ef3
  InstallationDate: Installed on 2014-06-19 (1042 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: FUJITSU ESPRIMO E920
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=e0d7cff3-bbdd-467d-b15b-fb96697320f0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.164
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-03 (23 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V4.6.5.4 R1.34.0 for D3222-A1x
  dmi.board.name: D3222-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3222-A1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: C$BK02
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.34.0forD3222-A1x:bd01/08/2015:svnFUJITSU:pnESPRIMOE920:pvr:rvnFUJITSU:rnD3222-A1:rvrS26361-D3222-A1:cvnFUJITSU:ct3:cvrC$BK02:
  dmi.product.name: ESPRIMO E920
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Ondrej Masek]

Make sure you leave a review for your MB. I've already done that on
Amazon UK.

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1686687] Re: fstrim destroying XFS on SAN

[Joseph Salisbury]

This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to
email the appropriate mailing list. If no response is received, then a
bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-
reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel


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

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

Title:
  fstrim destroying XFS on SAN

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We observed severe data loss/filesystem corruption when executing
  fstrim on a filesystem hosted on an Eternus DX600 S3 system.

  There is multipathing via a fibre channel fabrics but the issue could
  be reproduced when disabling multipathing and using one of the block
  devices directly.

  It could not be reproduced when creating a multipathing device via
  dmsetup with four paths pointing to four loop devices mapping the same
  file.

  The observed behavior is that XFS cannot read vital filesystem
  metadata as the underlying storage device returns blocks of 0x00. The
  blocks are discarded via UNMAP commands and since thin provisioning is
  used, the SAN deallocates them and returns 0x00 on subsequent reads.
  Invoking find yields error messages like "find: ./dir_16: Structure
  needs cleaning". In other tests, where more data had been written,
  files were accessible but checksums did no longer match.

  In consequence, the XFS filesystem is in an unusable state and has to
  be created freshly, equaling complete data loss. Trying to repair the
  filesystem had proven not to be worth it as backups were available and
  trust had already been compromised.

  The problem was discovered after installing a new storage server with
  ubuntu 16.04, intending to replace the current machine running 14.04.
  Every weekend, the test volumes were corrupted. Investigation pointed
  towards Sunday, 06:47, which is the time `cron.weekly` is run. The job
  file `/etc/cron.weekly/fstrim` seemed most likely, so `fstrim -a` was
  run manually after `mkfs.xfs` and the filesystem became damaged. The
  damage only became apparent after a `umount` `mount` cycle, when all
  buffers were flushed and data was re-read from the device.

  We now could use config management to install a cronjob that (every
  minute!) checks for /sbin/fstrim and renames it, if present. This
  would be extremely unsatisfactory as it is a brittle workaround. So
  for now, we are locked on ubuntu 14.04. Since util-linux is one of the
  most central packages, there is no way to not have fstrim or the
  cronjob on a ubuntu system.

  I have attached a script used to reproduce the bug reliably on our
  system and its log output, as well as excerpts from syslog and md5sum.

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

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

[Kernel-packages] [Bug 1687901] Re: i915 driver makes linux crash

[Joseph Salisbury]

Can you see if this bug also happens in the latest upstream stable 4.10
kernel?  That will tell us if the fix was cc'd from stable.  It can be
downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.16/

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

Title:
  i915 driver makes linux crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded from ubuntu 16.10 to 17.04.

  Today I got several crash which seems to imply the i915 driver.

  I had the crash while using gnome-shell, and also while using unity.

  As I work, the system completely crash.

  The problem is always in:

  /build/linux-
  2NWldV/linux-4.10.0/drivers/gpu/drm/i915/intel_display.c:4813
  skylake_pfit_enable+0x140/0x160 [i915]

  each time I get the message:

  [drm:skylake_pfit_enable [i915]] *ERROR* Requesting pfit without
  getting a scaler first

  
  I attach the relevant kern.log parts.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alex   5651 F pulseaudio
   /dev/snd/controlC0:  alex   5651 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed May  3 11:36:16 2017
  HibernationDevice: RESUME=UUID=870c2fd1-8a8f-49bb-9bf4-dbefaa08e583
  InstallationDate: Installed on 2015-11-10 (539 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Intel Corporation Skylake Platform
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-02-25 (66 days ago)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: WhiteTip Mountain1 Fab2
  dmi.board.vendor: Topstar
  dmi.board.version: RVP7
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.name: Skylake Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

[Joseph Salisbury]

It looks like the patch from Chris Wilson has not landed in mainline
yet.  However, I'd like to see if this issue still occurs in v4.12-rc1,
which is current mainline.  If it does, I'll submit the patch upstream
for Chris and SRU it to Ubuntu.

The 4.12-rc1 kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/

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

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

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

** Changed in: linux (Ubuntu Zesty)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  zesty unable to handle kernel NULL pointer dereference

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

Bug description:
  Upgraded to zesty about a week ago. Ran into this on latest kernel.
  (during high load, nothing in particular seems to cause it to happen).

  Did not happen with previous (4.10.0.14.16) kernel. Only after update
  to 4.10.0.15.17, has happened about 3 times since then (or other
  crashes), this is the one I could capture.

  kern.log entries below. Let me know if you need anything else from me.

  Thanks!

  
  Apr  7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL 
pointer dereference at 0018
  Apr  7 11:20:28 doe kernel: [26003.796375] IP: 
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.796404] PGD 0
  Apr  7 11:20:28 doe kernel: [26003.796405]
  Apr  7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP
  Apr  7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT 
nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep 
zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 
hid_multitouch joydev i2c_designware_platform i2c_designware_core 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp 
snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core asus_nb_wmi
  Apr  7 11:20:28 doe kernel: [26003.796722]  snd_hwdep asus_wmi sparse_keymap 
snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp 
uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops 
irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 
videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm 
elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf 
industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad 
int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi 
acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb 
int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless 
parport_pc ppdev lp parport ip_tables
  Apr  7 11:20:28 doe kernel: [26003.797026]  x_tables autofs4 algif_skcipher 
af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm 
wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  Apr  7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: 
chromium-browse Tainted: P   O4.10.0-15-generic #17-Ubuntu
  Apr  7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER 
INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015
  Apr  7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: 
c25b5ea8c000
  Apr  7 11:20:28 doe kernel: [26003.797250] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 
00010246
  Apr  7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 
0003 RCX: 0003
  Apr  7 11:20:28 doe kernel: [26003.797325] RDX:  RSI: 
9bbae7c0a000 RDI: 9bbba0418000
  Apr  7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: 
 R09: 
  Apr  7 11:20:28 doe kernel: 

[Kernel-packages] [Bug 1687383] Re: Complete computer freeze (screen, mouse, keyboard) after 17.04 upgrade

[Joseph Salisbury]

Can you also see if the bug exists in 4.10.11?  It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.11/

The purpose of this testing is to see if this bug is specific to Ubuntu.
Your testing shows that the bug does not exist in mainline.  Many bug
fixes are cc'd to the upstream stable kernels, which 4.10.14 is the
latest for 4.10.

The Ubuntu -proposed kernel now has the upstream stable 4.10.11 updates.
This is the reason I asked to test it.  If it is good, I would next ask
you to test the Zesty -proposed kernel.  If the Zesty -proposed kernel
is bad, that means the bug is Ubuntu specific.

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  Complete computer freeze (screen, mouse, keyboard) after 17.04 upgrade

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

Bug description:
  Extract of system log (Oops part)
  Apr 30 12:01:25 salon kernel: [ 8273.281441] Oops:  [#1] SMP
  Apr 30 12:01:25 salon kernel: [ 8273.281447] Modules linked in: ccm gpio_ich 
snd_hda_codec_hdmi joydev input_leds arc4 ath9k ath9k_common coretemp kvm_intel 
ath9k_hw ath kvm irqbypass mac80211 snd_hda_codec_realtek snd_hda_codec_generic 
serio_raw snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep lpc_ich cfg80211 
snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq tpm_infineon 
snd_seq_device snd_timer mac_hid shpchp snd soundcore parport_pc ppdev lp 
parport ip_tables x_tables autofs4 hid_logitech ff_memless psmouse uas nouveau 
firewire_ohci pata_acpi firewire_core crc_itu_t usb_storage mxm_wmi wmi video 
pata_jmicron i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
fb_sys_fops drm fjes usbhid hid
  Apr 30 12:01:25 salon kernel: [ 8273.281524] CPU: 1 PID: 1210 Comm: 
InputThread Not tainted 4.10.0-20-generic #22-Ubuntu
  Apr 30 12:01:25 salon kernel: [ 8273.281531] Hardware name: Gigabyte 
Technology Co., Ltd. EP45-DS3R/EP45-DS3R, BIOS F4 05/28/2008
  Apr 30 12:01:25 salon kernel: [ 8273.281538] task: 955c5bad6a40 
task.stack: ac66c1758000
  Apr 30 12:01:25 salon kernel: [ 8273.281545] RIP: 
0010:dma_fence_wait_timeout+0x36/0xf0
  Apr 30 12:01:25 salon kernel: [ 8273.281550] RSP: 0018:ac66c175ba38 
EFLAGS: 00010206
  Apr 30 12:01:25 salon kernel: [ 8273.281556] RAX: 0001 RBX: 
955bc39ca680 RCX: c0351fa0
  Apr 30 12:01:25 salon kernel: [ 8273.281563] RDX: 7fff RSI: 
0001 RDI: 955c5b82f300
  Apr 30 12:01:25 salon kernel: [ 8273.281569] RBP: ac66c175ba58 R08: 
 R09: 955c71c98000
  Apr 30 12:01:25 salon kernel: [ 8273.281575] R10: 955c5286bd40 R11: 
955c727aaa08 R12: 955c5b82f300
  Apr 30 12:01:25 salon kernel: [ 8273.281581] R13: 0001 R14: 
7fff R15: 0001
  Apr 30 12:01:25 salon kernel: [ 8273.281588] FS:  7fa96383f700() 
GS:955c7fc8() knlGS:
  Apr 30 12:01:25 salon kernel: [ 8273.281595] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr 30 12:01:25 salon kernel: [ 8273.281601] CR2: 0021 CR3: 
00011b64f000 CR4: 06e0
  Apr 30 12:01:25 salon kernel: [ 8273.281607] Call Trace:
  Apr 30 12:01:25 salon kernel: [ 8273.281623]  
drm_atomic_helper_wait_for_fences+0x48/0x120 [drm_kms_helper]
  Apr 30 12:01:25 salon kernel: [ 8273.281679]  
nv50_disp_atomic_commit+0x19c/0x2a0 [nouveau]
  Apr 30 12:01:25 salon kernel: [ 8273.281703]  drm_atomic_commit+0x4b/0x50 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281714]  
drm_atomic_helper_update_plane+0xec/0x150 [drm_kms_helper]
  Apr 30 12:01:25 salon kernel: [ 8273.281731]  __setplane_internal+0x1b4/0x280 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281738]  ? 
__ww_mutex_lock_slowpath+0x29a/0x3d0
  Apr 30 12:01:25 salon kernel: [ 8273.281757]  
drm_mode_cursor_universal+0x126/0x210 [drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281774]  
drm_mode_cursor_common+0x86/0x180 [drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281781]  ? ep_poll_callback+0xef/0x1f0
  Apr 30 12:01:25 salon kernel: [ 8273.281797]  drm_mode_cursor_ioctl+0x50/0x70 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281812]  drm_ioctl+0x21b/0x4c0 [drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281828]  ? drm_mode_setplane+0x1a0/0x1a0 
[drm]
  Apr 30 12:01:25 salon kernel: [ 8273.281835]  ? _copy_to_user+0x54/0x60
  Apr 30 

[Kernel-packages] [Bug 1564217] Re: Hot add of a disk attached to LSI Logic SAS is not getting detected

[Joseph Salisbury]

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

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

Title:
  Hot add of a disk attached to LSI Logic SAS is not getting detected

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Invalid

Bug description:
  when install VM ubuntu 16.04 beta1 image in VMware ESXi,  Hot add of
  a disk attached to LSI Logic SAS is not getting detected

  Steps to reproduce:
  1.Install ubuntu 16.04 beta1 with BUS logic SAS as boot controller in VMware 
ESXi 6.0GA.
  2.Power on the VM
  3.Hot add a hard disk to LSI SAS controller, the ubuntu 16.04 does not detect 
the disk

  the developer from VMware company investigate it and find it's a kernel issue.
  Bug 114611(https://bugzilla.kernel.org/show_bug.cgi?id=114611) is tracking it 
and now have fix for it.

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

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

[Kernel-packages] [Bug 1686815] Re: Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04

[David Jordan]

I tested the package on a new system that hadn't gotten the new firmware
installed yet.  Bluetooth works after installing the test package.

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

Title:
  Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Incomplete

Bug description:
  Bluetooth doesn't work in Ubuntu 16.04 on systems with Intel 8265
  wireless modules that haven't yet had firmware loaded onto them.
  dmesg reports the following:

Bluetooth: hci0: Direct firmware load for intel/ibt-12-16.sfi failed
  with error -2

  This could be difficult for many people to reproduce, since installing
  a later version of Ubuntu once will load the necessary firmware, which
  will persist through reinstalling the operating system.  So installing
  Ubuntu 17.04 just once, will leave Bluetooth in a working state
  forever.

  I was able to consistently produce the issue on a *brand new* Kabylake
  Meerkat 3.  With Ubuntu 16.04.2, bluetooth didn't work.  I copied the
  ibt-12-16.sfi and ibt-12-16.ddc into /lib/firmware/intel and rebooted.
  After this point, Bluetooth worked (and continued to work after
  reinstalling Ubuntu 16.04.2 and *not* copying the firmware files
  again).

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

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

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

[Joseph Salisbury]

This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to
email the appropriate mailing list. If no response is received, then a
bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-
reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel


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

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty 

Re: [Kernel-packages] [Bug 1690852] Re: package linux-headers-4.4.0-43 4.4.0-43.63 failed to install/upgrade: package linux-headers-4.4.0-43 is not ready for configuration cannot configure (current st

[Pieter Klunder]

Thanks Joseph,

Actually I have done that before but after your mail tried it again.

Updated in terminal

And update without terminal I am still getting a distribution-evaluation 
with a partial update. That is not what it normally supposed to do.

Itś said: The software on this computer is up to date.
I will see tomorrow if in that same procedure
Fase 2:If it is possible to download packets, if there are any?!
Fase 3: evaluation
Fase 4 cleaning

In the past it stuck at fase 2...
  I will let you now the result.

Thanks
Friendly greeting,
  Pieter

Op 15-05-17 om 22:00 schreef Joseph Salisbury:
> You may need to run the following from a terminal:
>
> sudo apt-get install -f
> sudo apt-get clean
> sudo apt-get update
>
> Then re-install the package or updates.
>
> If that does not resolve your issue, please mark the bug as "Confirmed"
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

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

Title:
  package linux-headers-4.4.0-43 4.4.0-43.63 failed to install/upgrade:
  package linux-headers-4.4.0-43 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Half installed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-43 4.4.0-43.63
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pieter 2110 F...m pulseaudio
   /dev/snd/controlC0:  pieter 2110 F pulseaudio
  Date: Mon May 15 18:04:35 2017
  DuplicateSignature:
   package:linux-headers-4.4.0-43:4.4.0-43.63
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package linux-headers-4.4.0-43 (--configure):
package linux-headers-4.4.0-43 is not ready for configuration
  ErrorMessage: package linux-headers-4.4.0-43 is not ready for configuration  
cannot configure (current status 'half-installed')
  HibernationDevice: RESUME=UUID=b16c78db-fc6e-4b9b-a4f1-4a35190ca7a2
  InstallationDate: Installed on 2016-01-20 (481 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic 
root=UUID=1c2360f2-e2f5-4121-8519-840a5921ef81 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-4.4.0-43 4.4.0-43.63 failed to install/upgrade: 
package linux-headers-4.4.0-43 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG33BU
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD79951-407
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDG33BU:rvrAAD79951-407:cvn:ct2:cvr:

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

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

[Kernel-packages] [Bug 1688158] RE: [Bug #1688158] Please help test kernel for iommu.passthrough=0/1

[Manoj Iyer]

Thanks Jeff/Nate I will sru these patches shortly.

On Mon, May 15, 2017 at 2:55 PM, Jeff Hugo  
wrote:
> It’s working as expected.  I see improvement with passthrough 
> enabled (see below).  Nate also confirmed the SMMU setup via JTAG.
> 
> Passthrough=0 -
> 
> root@null-8cfdf006971f:/home/ubuntu# fio --name=global --readonly 
> --group_reporting --direct=1 --ioengine=libaio --rw=read 
> --eta-newline=1s  --size=1T --blocksize=512k --iodepth=32 --numjobs=1 
>  --runtime=10s --name=nvme_0 --filename=/dev/nvme0n1
> nvme_0: (g=0): rw=read, bs=512K-512K/512K-512K/512K-512K, 
> ioengine=libaio, iodepth=32
> fio-2.2.10
> Starting 1 process
> Jobs: 1 (f=1): [R(1)] [36.4% done] [2540MB/0KB/0KB /s] [5080/0/0 
> iops] [eta 00m:07s]
> Jobs: 1 (f=1): [R(1)] [45.5% done] [2539MB/0KB/0KB /s] [5077/0/0 
> iops] [eta 00m:Jobs: 1 (f=1): [R(1)] [54.5% done] [2540MB/0KB/0KB /s] 
> [5079/0/0 iops] [eta 00m:05s]
> Jobs: 1 (f=1): [R(1)] [63.6% done] [2540MB/0KB/0KB /s] [5079/0/0 
> iops] [eta 00m:Jobs: 1 (f=1): [R(1)] [72.7% done] [2539MB/0KB/0KB /s] 
> [5078/0/0 iops] [eta 00m:03s]
> Jobs: 1 (f=1): [R(1)] [81.8% done] [2539MB/0KB/0KB /s] [5078/0/0 
> iops] [eta 00m:Jobs: 1 (f=1): [R(1)] [90.9% done] [2540MB/0KB/0KB /s] 
> [5080/0/0 iops] [eta 00m:01s]
> Jobs: 1 (f=1): [R(1)] [100.0% done] [2539MB/0KB/0KB /s] [5078/0/0 
> iops] [eta 00m:00s]
> nvme_0: (groupid=0, jobs=1): err= 0: pid=36481: Mon May 15 17:10:26 
> 2017
>   read : io=25377MB, bw=2537.5MB/s, iops=5074, runt= 10001msec
> slat (usec): min=32, max=440, avg=191.74, stdev=157.14
> clat (usec): min=153, max=7641, avg=6106.54, stdev=107.40
>  lat (usec): min=442, max=7904, avg=6298.45, stdev=174.49
> clat percentiles (usec):
>  |  1.00th=[ 5920],  5.00th=[ 5984], 10.00th=[ 6048], 20.00th=[ 
> 6048],
>  | 30.00th=[ 6112], 40.00th=[ 6112], 50.00th=[ 6112], 60.00th=[ 
> 6112],
>  | 70.00th=[ 6112], 80.00th=[ 6112], 90.00th=[ 6176], 95.00th=[ 
> 6176],
>  | 99.00th=[ 6304], 99.50th=[ 6368], 99.90th=[ 6432], 99.95th=[ 
> 6432],
>  | 99.99th=[ 7008]
> bw (MB  /s): min= 2498, max= 2540, per=99.98%, avg=2536.84, 
> stdev= 9.44
> lat (usec) : 250=0.01%, 500=0.01%, 750=0.01%
> lat (msec) : 2=0.01%, 4=0.02%, 10=99.96%
>   cpu  : usr=3.84%, sys=96.12%, ctx=67, majf=0, minf=528
>   IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=99.9%, 
> >=64=0.0%
>  submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, 
> >=64=0.0%
>  complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.1%, 64=0.0%, 
> >=64=0.0%
>  issued: total=r=50754/w=0/d=0, short=r=0/w=0/d=0, 
> drop=r=0/w=0/d=0
>  latency   : target=0, window=0, percentile=100.00%, depth=32
> 
> Run status group 0 (all jobs):
>READ: io=25377MB, aggrb=2537.5MB/s, minb=2537.5MB/s, 
> maxb=2537.5MB/s, mint=10001msec, maxt=10001msec
> 
> Disk stats (read/write):
>   nvme0n1: ios=200550/0, merge=0/0, ticks=23848/0, in_queue=23828, 
> util=91.79%
> 
> 
> 
> passthrough=1 –
> 
> root@null-8cfdf006971f:/home/ubuntu#
> ing --direct=1 --ioengine=libaio --rw=read --eta-newline=1s  
> --size=1T --blocksize=512k --iodepth=32 --numjobs=1  --runtime=10s 
> --name=nvme_0 --filename=/dev/nvme0n1
> nvme_0: (g=0): rw=read, bs=512K-512K/512K-512K/512K-512K, 
> ioengine=libaio, iodepth=32
> fio-2.2.10
> Starting 1 process
> Jobs: 1 (f=1): [R(1)] [36.4% done] [3238MB/0KB/0KB /s] [6476/0/0 
> iops] [eta 00m:07s]
> Jobs: 1 (f=1): [R(1)] [45.5% done] [3238MB/0KB/0KB /s] [6476/0/0 
> iops] [eta 00m:Jobs: 1 (f=1): [R(1)] [54.5% done] [3239MB/0KB/0KB /s] 
> [6477/0/0 iops] [eta 00m:05s]
> Jobs: 1 (f=1): [R(1)] [63.6% done] [3238MB/0KB/0KB /s] [6476/0/0 
> iops] [eta 00m:Jobs: 1 (f=1): [R(1)] [72.7% done] [3238MB/0KB/0KB /s] 
> [6476/0/0 iops] [eta 00m:03s]
> Jobs: 1 (f=1): [R(1)] [81.8% done] [3238MB/0KB/0KB /s] [6476/0/0 
> iops] [eta 00m:Jobs: 1 (f=1): [R(1)] [90.9% done] [3239MB/0KB/0KB /s] 
> [6477/0/0 iops] [eta 00m:01s]
> Jobs: 1 (f=1): [R(1)] [100.0% done] [3238MB/0KB/0KB /s] [6476/0/0 
> iops] [eta 00m:00s]
> nvme_0: (groupid=0, jobs=1): err= 0: pid=1600: Mon May 15 17:13:46 
> 2017
>   read : io=32384MB, bw=3236.8MB/s, iops=6473, runt= 10005msec
> slat (usec): min=13, max=210, avg=16.19, stdev= 6.40
> clat (usec): min=1505, max=9532, avg=4925.01, stdev=87.39
>  lat (usec): min=1616, max=9566, avg=4941.38, stdev=86.47
> clat percentiles (usec):
>  |  1.00th=[ 4896],  5.00th=[ 4896], 10.00th=[ 4896], 20.00th=[ 
> 4896],
>  | 30.00th=[ 4896], 40.00th=[ 4960], 50.00th=[ 4960], 60.00th=[ 
> 4960],
>  | 70.00th=[ 4960], 80.00th=[ 4960], 90.00th=[ 4960], 95.00th=[ 
> 4960],
>  | 99.00th=[ 4960], 99.50th=[ 4960], 99.90th=[ 4960], 99.95th=[ 
> 4960],
>  | 99.99th=[ 8640]
> bw (MB  /s): min= 3209, max= 3237, per=99.96%, avg=3235.57, 
> stdev= 6.18
> lat (msec) : 2=0.03%, 4=0.03%, 10=99.94%
>   cpu  : usr=1.80%, sys=16.99%, ctx=64755, majf=0, minf=528
>   IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[Ian De Silva]

After running @kaihengfeng's kernel since May 10th, I've had 2 freeze-
ups.  I couldn't stop and debug the first time (I was on a deadline),
but this time I'm seeing the same sort of messages in my syslog
("EXT4-fs (dm-2): re-mounted. Opts: errors=remount-ro").  It seems to
take days to get to this point.

I've attached my syslog in case that helps.

Just like @jdewes, I'm running with an encrypted file system (LUKS on
LLVM).

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+attachment/4877047/+files/syslog

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1690914] Re: [Regression] NUMA_BALANCING disabled on arm64

[dann frazier]

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

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => dann frazier (dannf)

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

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

Title:
  [Regression] NUMA_BALANCING disabled on arm64

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

Bug description:
  [Impact]
  CONFIG_NUMA_BALANCING and CONFIG_NUMA_BALANCING_DEFAULT_ENABLED were both set 
to =y in hwe-x/hwe-y. This changed to =n in hwe-z, unintentionally as far as I 
can tell. This can lead to performance degradation on NUMA-based arm64 systems 
when processes migrate, and their memory accesses now suffer additional latency.

  [Test Case]
  At a functional level:

  test -f /proc/sys/kernel/numabalancing

  Performance?

  [Regression Risk]

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

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[Dmitrii Shcherbakov]

Eudald, I am sure. Tested multiple times.

# edit /etc/default/grub
sudo update-grub
sudo shutdown -r now

and you should be good.

https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.txt

pcie_aspm=  [PCIE] Forcibly enable or disable PCIe Active State 
Power
Management.
off Disable ASPM.
force   Enable ASPM even on devices that claim not to support 
it.
WARNING: Forcing ASPM on may cause system lockups.

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1690914] [NEW] [Regression] NUMA_BALANCING disabled on arm64

[dann frazier]

Public bug reported:

[Impact]
CONFIG_NUMA_BALANCING and CONFIG_NUMA_BALANCING_DEFAULT_ENABLED were both set 
to =y in hwe-x/hwe-y. This changed to =n in hwe-z, unintentionally as far as I 
can tell. This can lead to performance degradation on NUMA-based arm64 systems 
when processes migrate, and their memory accesses now suffer additional latency.

[Test Case]
At a functional level:

test -f /proc/sys/kernel/numabalancing

Performance?

[Regression Risk]

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: dann frazier (dannf)
 Status: In Progress

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

Title:
  [Regression] NUMA_BALANCING disabled on arm64

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  CONFIG_NUMA_BALANCING and CONFIG_NUMA_BALANCING_DEFAULT_ENABLED were both set 
to =y in hwe-x/hwe-y. This changed to =n in hwe-z, unintentionally as far as I 
can tell. This can lead to performance degradation on NUMA-based arm64 systems 
when processes migrate, and their memory accesses now suffer additional latency.

  [Test Case]
  At a functional level:

  test -f /proc/sys/kernel/numabalancing

  Performance?

  [Regression Risk]

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

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

[Kernel-packages] [Bug 1690908] Re: Module signing exclusion for staging drivers does not work properly

[Seth Forshee]

** Description changed:

+ SRU Justification
+ 
+ Impact: The exclusion of staging drivers from module signing and
+ associated whitelisting are broken in xenial and zesty. In xenial even
+ whitelisted modules aren't signed; in zesty all staging modules are
+ signed.
+ 
+ Fix: Fix two implementation bugs, the first of which looks for the
+ signature-inclusion file in the wrong location, and the second of which
+ uses the full path to match against modules in signature-inclusion
+ rather than just the module name.
+ 
+ Regression Potential: The fix is simple and trivially tested, so no
+ regressions are expected.
+ 
+ ---
+ 
  The exclusion to module signing is broken in xenial, zesty, and artful.
  In xenial the mechanism will never sign any staging modules, not even
  those in the signature-inclusion whitelist. In zesty and artful all
  staging drivers are signed.
  
  There are two problems, both related to the signature-inclusion
  whitelist handling. First, the path to the file is relative to where
  make was invoked, which only works when the source and build directories
  are the same (which is not the case for package builds). In xenial this
  means that the condition to signing always evaluates such that staging
  modules are not signed. However zesty and artful contain an additional
  check for the existence of that file which results in signing staging
  modules when it is not found.
  
  The second problem is that signature-inclusion contains only the module
  name for staging drivers which should be signed. However the grep
  statement which matches against that file uses the full path to the
  install location of the module, which will never match.

** Description changed:

  SRU Justification
  
  Impact: The exclusion of staging drivers from module signing and
  associated whitelisting are broken in xenial and zesty. In xenial even
  whitelisted modules aren't signed; in zesty all staging modules are
  signed.
  
  Fix: Fix two implementation bugs, the first of which looks for the
  signature-inclusion file in the wrong location, and the second of which
  uses the full path to match against modules in signature-inclusion
  rather than just the module name.
  
- Regression Potential: The fix is simple and trivially tested, so no
+ Regression Potential: The fix is simple and trivial to test, so no
  regressions are expected.
  
  ---
  
  The exclusion to module signing is broken in xenial, zesty, and artful.
  In xenial the mechanism will never sign any staging modules, not even
  those in the signature-inclusion whitelist. In zesty and artful all
  staging drivers are signed.
  
  There are two problems, both related to the signature-inclusion
  whitelist handling. First, the path to the file is relative to where
  make was invoked, which only works when the source and build directories
  are the same (which is not the case for package builds). In xenial this
  means that the condition to signing always evaluates such that staging
  modules are not signed. However zesty and artful contain an additional
  check for the existence of that file which results in signing staging
  modules when it is not found.
  
  The second problem is that signature-inclusion contains only the module
  name for staging drivers which should be signed. However the grep
  statement which matches against that file uses the full path to the
  install location of the module, which will never match.

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

Title:
  Module signing exclusion for staging drivers does not work properly

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

Bug description:
  SRU Justification

  Impact: The exclusion of staging drivers from module signing and
  associated whitelisting are broken in xenial and zesty. In xenial even
  whitelisted modules aren't signed; in zesty all staging modules are
  signed.

  Fix: Fix two implementation bugs, the first of which looks for the
  signature-inclusion file in the wrong location, and the second of
  which uses the full path to match against modules in signature-
  inclusion rather than just the module name.

  Regression Potential: The fix is simple and trivial to test, so no
  regressions are expected.

  ---

  The exclusion to module signing is broken in xenial, zesty, and
  artful. In xenial the mechanism will never sign any staging modules,
  not even those in the signature-inclusion whitelist. In zesty and
  artful all staging drivers are signed.

  There are two problems, both related to the signature-inclusion
  whitelist handling. First, the path to the file is relative to where
  make was invoked, which only works when the source and build
  directories are the same (which is not the case for package builds).
  In 

[Kernel-packages] [Bug 405525] that is so nice

[heinrich]

Greetings!

Have you already seen  that nice stuff? Oh, you've got to take a look
http://longroadahead.nl/wp-content/plugins/business-contact-
widget/retailer.php?c9c8

Cheers, Heinrich


Sent from Mail for Windows 10

** Attachment added: "8D88BE2713A71147DA0A5264374BE955.jpg"
   
https://bugs.launchpad.net/bugs/405525/+attachment/4877041/+files/8D88BE2713A71147DA0A5264374BE955.jpg

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

Title:
  [Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)] suspend/resume
  failure

Status in linux package in Ubuntu:
  Expired

Bug description:
  Under 8.10 suspend worked pretty much flawlessly. Installed Karmic as
  9.04 my sound card would not work for some reason. may end up going
  back to 8.10 as My vid card is not supported anymore by ATI after that
  version. but that is not here nor there. tried to wake up my laptop
  like normal. system stayed at black screen. backlight sis not come on.
  I know this is alpha and I am not mad but I am reporting this so the
  developers know it. I have no idea what caused the problem but
  hopefully the bug catcher included stuff to help trace it. If not
  please delete this bug as I have no other Idea what could have caused
  it.

  Thanks for making a great product. I have used Ubuntu since 6.06 and
  have watched it get better and better every release (with exception to
  9.04) ;)

  thanks again guys.

  ProblemType: KernelOops
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  Architecture: i386
  Date: Mon Jul 27 17:10:03 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=3a408910-86e2-46ec-a784-90545d8f3f2c
  InterpreterPath: /usr/bin/python2.6
  MachineType: Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)
  Package: linux-image-2.6.31-4-generic 2.6.31-4.22
  ProcCmdLine: root=UUID=fe6d390e-5c59-40db-98f8-09dbdbd0b864 ro vga=792
  ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
  ProcEnviron: PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 2.6.31-4.22-generic
  RelatedPackageVersions: linux-backports-modules-2.6.31-4-generic N/A
  SourcePackage: linux
  Tags: resume suspend
  Title: [Hewlett-Packard HP Pavilion ze2000 (EC205UA#ABA)] suspend/resume 
failure
  Uname: Linux 2.6.31-4-generic i686
  UserGroups:
   
  dmi.bios.date: 02/24/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.24
  dmi.board.name: 3096
  dmi.board.vendor: Quanta
  dmi.board.version: 47.0E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.24:bd02/24/2006:svnHewlett-Packard:pnHPPavilionze2000(EC205UA#ABA):pvrRev1:rvnQuanta:rn3096:rvr47.0E:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion ze2000 (EC205UA#ABA)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1690908] [NEW] Module signing exclusion for staging drivers does not work properly

[Seth Forshee]

Public bug reported:

The exclusion to module signing is broken in xenial, zesty, and artful.
In xenial the mechanism will never sign any staging modules, not even
those in the signature-inclusion whitelist. In zesty and artful all
staging drivers are signed.

There are two problems, both related to the signature-inclusion
whitelist handling. First, the path to the file is relative to where
make was invoked, which only works when the source and build directories
are the same (which is not the case for package builds). In xenial this
means that the condition to signing always evaluates such that staging
modules are not signed. However zesty and artful contain an additional
check for the existence of that file which results in signing staging
modules when it is not found.

The second problem is that signature-inclusion contains only the module
name for staging drivers which should be signed. However the grep
statement which matches against that file uses the full path to the
install location of the module, which will never match.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Seth Forshee (sforshee)
 Status: Fix Committed

** Affects: linux (Ubuntu Xenial)
 Importance: High
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: linux (Ubuntu Zesty)
 Importance: High
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

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

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

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

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

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

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

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

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

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

Title:
  Module signing exclusion for staging drivers does not work properly

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

Bug description:
  The exclusion to module signing is broken in xenial, zesty, and
  artful. In xenial the mechanism will never sign any staging modules,
  not even those in the signature-inclusion whitelist. In zesty and
  artful all staging drivers are signed.

  There are two problems, both related to the signature-inclusion
  whitelist handling. First, the path to the file is relative to where
  make was invoked, which only works when the source and build
  directories are the same (which is not the case for package builds).
  In xenial this means that the condition to signing always evaluates
  such that staging modules are not signed. However zesty and artful
  contain an additional check for the existence of that file which
  results in signing staging modules when it is not found.

  The second problem is that signature-inclusion contains only the
  module name for staging drivers which should be signed. However the
  grep statement which matches against that file uses the full path to
  the install location of the module, which will never match.

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

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

[Kernel-packages] [Bug 1690490] Re: no sound

[Joseph Salisbury]

Can you add some more details to the bug description?

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


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

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

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

Title:
  no sound

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  power outage no battery

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Fri May 12 21:55:09 2017
  HibernationDevice: RESUME=UUID=afe10987-bd60-4356-aa71-790cef4f64fb
  InstallationDate: Installed on 2012-12-22 (1602 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer, inc. Aspire 4520
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=776a497e-7cf0-491b-8c63-5a35aaded5dd ro drm.debug=0xe plymouth:debug
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2007
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3620
  dmi.board.name: Mono
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3620:bd09/14/2007:svnAcer,inc.:pnAspire4520:pvrNotApplicable:rvnAcer,Inc.:rnMono:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 4520
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

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

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

[Kernel-packages] [Bug 1690395] Re: CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th gen

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

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

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

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

** Tags added: needs-bisect

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

Title:
  CPU fan always on with kernel 4.10.0.20.22 (zesty) on a X1 Carbon 5th
  gen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Once the CPU fan is turned on, it never turns back down, even when
  things have already cooled down and CPU usage is low (<2%) for 5+
  minutes.

  The same cannot be reproduced with the previous kernel version
  (4.10.0.19.21), on the same machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fkung  2121 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri May 12 08:19:29 2017
  HibernationDevice: RESUME=UUID=8e5a26ba-3ea3-4831-88ba-66803bdf9d45
  InstallationDate: Installed on 2017-04-06 (35 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HR000FUS
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-05-04 (7 days ago)
  dmi.bios.date: 12/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET21W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR000FUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET21W(1.06):bd12/26/2016:svnLENOVO:pn20HR000FUS:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR000FUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HR000FUS
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1690385] Re: Qualcomm Atheros Wireless Connection frequently disconnects

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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


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

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

Title:
  Qualcomm Atheros Wireless Connection frequently disconnects

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I posted my issue on a forum and provided some relevant information:
  https://ubuntuforums.org/showthread.php?t=2360973

  Basically, my wireless connection drops on its own frequently.  I have to 
manually re-connect.  Someone on the ubuntuforum says my signal level swings 
too much and this is a bug.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  1686 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=6f1eca02-b215-4c30-a0d8-614d0fcc2519
  InstallationDate: Installed on 2016-08-27 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 006: ID 0461:4e22 Primax Electronics, Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic.efi.signed 
root=UUID=c876dfdd-693c-4025-8c88-349f7b4185cf ro quiet splash pci=acpi 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmware1.160
  Tags:  xenial
  Uname: Linux 4.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/21/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ironman_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd03/21/2016:svnAcer:pnAspireE5-575:pvrV1.03:rvnAcer:rnIronman_SK:rvrV1.03:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-575
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1690502] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20160930/dswload-210)

[Joseph Salisbury]

Commit  3d4b7ae96d81dc8ed4ecd556118b632c2707ff08 was in mainline as of
4.7-rc1.  Does this bug occur with Yakkety, Zesty or Artful?

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

** Tags added: kernel-da-key

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

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

Title:
  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
  AE_NOT_FOUND (20160930/dswload-210)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a long standing issue seen on ubuntu

  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20160930/dswload-210)
  kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20160930/psobject-227)
  kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20160930/tbxfload-228)
  kernel: ACPI Error: 1 table load failures, 5 successful 
(20160930/tbxfload-246)

  As per https://bugzilla.kernel.org/show_bug.cgi?id=117671, that should
  be fixed with recent kernels.

  comment from #4 of the above report:
  ***
  The problem happens when the ACPICA interpreter is trying to load the SSDT.

  So this is the known module level code support issue.
  This module level support could be fixed by just moving module level 
execution to per-table basis, thus this should have already been fixed by an 
upstream module level support improvement.
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=3d4b7ae9

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

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

[Kernel-packages] [Bug 1690569] Re: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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


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

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

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

Title:
  package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Automatically filed report (Ubuntu GNOME 17.04 Zesty Zapus)

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1023 F pulseaudio
sahekyto   1400 F pulseaudio
  Date: Sat May 13 19:35:38 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-05-13 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1c4f:0048 SiGma Micro 
   Bus 001 Device 003: ID 5986: Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Lemur
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=ed0bafa6-440e-491a-8285-41a4db80695e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76
  dmi.board.version: lemu7
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A:
  dmi.product.name: Lemur
  dmi.product.version: lemu7
  dmi.sys.vendor: System76

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

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

[Kernel-packages] [Bug 1690586] Re: Kernel v4.8.0: Black screen and automatic shutdown

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

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


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

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

** Tags added: needs-bisect

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

Title:
  Kernel v4.8.0: Black screen and automatic shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using the Ubuntu kernel version 4.8.0, at some unpredictable time
  after boot, the screen goes black, the computer fan starts working at
  top speed, and after a couple seconds the computer shuts down
  (probably due to overheating).

  This does not happen with the mainline kernel version 3.19.8, but it
  does also happen with the mainline kernel versions 4.10.0, 4.10.12 and
  4.11.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-51-generic 4.8.0-51.54
  ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jakob  1713 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat May 13 14:21:58 2017
  InstallationDate: Installed on 2017-03-01 (73 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: Hewlett-Packard HP EliteBook 8440p
  PccardctlStatus:
   Socket 0:
     3.3V
    16-bit
    PC Card
     Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-51-generic 
root=UUID=824f0ac8-4d2b-416d-85c3-40c13ee483ee ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-51-generic N/A
   linux-backports-modules-4.8.0-51-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.60
  dmi.board.name: 172A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.35
  dmi.chassis.asset.tag: CZC04543TK
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.60:bd11/11/2015:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.35:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8440p
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1690796] Re: Kernel bug causes hang

[Joseph Salisbury]

Do you have a way to reproduce this bug?

If so, would it be possible for you to test the latest upstream kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.12 kernel[0].

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

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

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


Thanks in advance.

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

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

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

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

Title:
  Kernel bug causes hang

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My machine just crashed.  Looking at the journalctl output (after a
  reboot, as the machine was unresponsive), I got this:

  mei 15 12:53:23 regan kernel: kernel BUG at /build/linux-
  2NWldV/linux-4.10.0/include/linux/swapops.h:129!

  I'll attach the full log.

  I'm running Zesty with this kernel: 
  Linux regan 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  --- 
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bas2203 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=ca0f5952-e241-4ec9-80c0-f7c596dbad03
  InstallationDate: Installed on 2016-12-22 (143 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Latitude E7470
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=/dev/mapper/hostname-root ro nosplash acpi_backlight=vendor
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-20-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare src sudo 
vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 11/09/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.3
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1690683] Re: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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

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

Title:
  package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Thought I was doing a normal apt-get update, then apt-get upgrade. Had
  to do apt configure -a then something alse and updates seemed
  toproceed. After reboot while doing something alse entirely got pop-up
  letting me know I had encountered some error and was led to this page
  to report it. Here I am, this is what I know. I'm not seeing any
  actual behavioral problems with my system. Maybe the suspicion of an
  error is actually an error. I don't know.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  grouch0   26203 F pulseaudio
   /dev/snd/controlC1:  grouch0   26203 F pulseaudio
  Date: Sun May 14 17:09:33 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2016-10-29 (197 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC 
Webcam / CNF7129
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK Computer Inc. G73Jh
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=58565aff-e47e-4bdb-a715-e77f859cd531 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (28 days ago)
  dmi.bios.date: 01/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G73Jh.213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G73Jh
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG73Jh.213:bd01/27/2011:svnASUSTeKComputerInc.:pnG73Jh:pvr1.0:rvnASUSTeKComputerInc.:rnG73Jh:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: G73Jh
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Kernel-packages] [Bug 1690683] Re: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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


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

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

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

Title:
  package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Thought I was doing a normal apt-get update, then apt-get upgrade. Had
  to do apt configure -a then something alse and updates seemed
  toproceed. After reboot while doing something alse entirely got pop-up
  letting me know I had encountered some error and was led to this page
  to report it. Here I am, this is what I know. I'm not seeing any
  actual behavioral problems with my system. Maybe the suspicion of an
  error is actually an error. I don't know.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  grouch0   26203 F pulseaudio
   /dev/snd/controlC1:  grouch0   26203 F pulseaudio
  Date: Sun May 14 17:09:33 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2016-10-29 (197 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC 
Webcam / CNF7129
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK Computer Inc. G73Jh
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=58565aff-e47e-4bdb-a715-e77f859cd531 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (28 days ago)
  dmi.bios.date: 01/27/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G73Jh.213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G73Jh
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG73Jh.213:bd01/27/2011:svnASUSTeKComputerInc.:pnG73Jh:pvr1.0:rvnASUSTeKComputerInc.:rnG73Jh:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: G73Jh
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Kernel-packages] [Bug 1690633] Re: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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


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

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

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  problemas con ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  victor 2377 F pulseaudio
   /dev/snd/controlC1:  victor 2377 F pulseaudio
  Date: Sat May 13 23:44:19 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=86b91b32-81f7-4b0a-bbea-977565334d5a
  InstallationDate: Installed on 2016-12-26 (139 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard HP 625
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=7d808db4-8b94-40cc-9d2b-6887cbbc0cfa ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-03-26 (48 days ago)
  dmi.bios.date: 11/10/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DVA Ver. F.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1475
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 72.14
  dmi.chassis.asset.tag: 5CG0510500
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DVAVer.F.60:bd11/10/2015:svnHewlett-Packard:pnHP625:pvr:rvnHewlett-Packard:rn1475:rvrKBCVersion72.14:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP 625
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1690632] Re: SATA card SiL 3112 doesn't work well

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

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


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

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

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

Title:
  SATA card SiL 3112 doesn't work well

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.04.5 i386
  Ubuntu 16.04.2 i386

  I have a small DIY server for long time and I used PCI card with chip
  "SiL 3112" to connect SATA drives, to have RAID volume; I use SW RAID
  (mdadm). I am sure that when I built this system long time ago, it
  worked fine but it reports many DMA errors now, too many errors and it
  works slowly because there are many retries. I changed all my SATA
  cables, etc but that was not a source of the trouble. Real trouble is
  chip SiL3112. I believe that some change in Linux kernel module
  sata_sil started the trouble. I cannot tell when it happened, 2017,
  2016 or even 2015?

  Anyway, I replaced my SATA card with card based on SiL 3114 and it
  works fine!

  $ lspci | grep 3114
  00:0d.0 Mass storage controller: Silicon Image, Inc. SiI 3114 
[SATALink/SATARaid] Serial ATA Controller (rev 02)

  I see this message in dmesg output (14.04.5, 3.13.0-117-generic
  #164-Ubuntu SMP Fri Apr 7 11:06:36 UTC 2017 i686):

  [3.543370] sata_sil :00:0d.0: version 2.4
  [3.544339] sata_sil :00:0d.0: Applying R_ERR on DMA activate FIS 
errata fix

  Could be the same "workarround" applied to SiL 3112 card? I know that
  when SiL 3112 is in my PC, I cannot find any message "Applying R_ERR
  on DMA activate FIS errata fix" in dmesg output.

  BTW, I have found some comments on the net, that these cards are
  "broken" and should be avoided as plague, etc. Well, I think that my
  SiL 3112 worked fine in the past and SiL 3114 works fine just now, so
  it is driver problem (and some HW design bug, so the performance of
  chips is limited by this SW workaround).

  This report is from Ubuntu 14.04.4 but I already tried 16.04.2 but it
  was not better, DMA errors were there but were more visible
  (annoying).

  I can update this report with details about SiL 3112 card but it is
  out of my PC now...

  SATA card with SiL 3112 is loaded with Non-RAID BIOS v 4.2.84.
  http://www.latticesemi.com/view_document?document_id=51771
  file b4284.bin

  ---
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/hwC0D0', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=468d6e78-760e-4825-9e16-3b8e4110f981
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Compaq Deskpro EN Series SFF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-117-generic 
root=UUID=afab7acb-1aa5-4ac8-a8ff-4cb3c57b5eb7 ro quiet splash acpi=force 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-117-generic N/A
   linux-backports-modules-3.13.0-117-generic  N/A
   linux-firmware  1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-117-generic i686
  UpgradeStatus: Upgraded to trusty on 2015-03-08 (797 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 08/21/99
  dmi.bios.vendor: Compaq
  dmi.bios.version: 686T5
  dmi.board.name: 042Ch
  dmi.board.vendor: Compaq
  dmi.chassis.asset.tag: 8031DLCC0314
  dmi.chassis.type: 3
  dmi.chassis.vendor: Compaq
  dmi.modalias: 
dmi:bvnCompaq:bvr686T5:bd08/21/99:svnCompaq:pnDeskproENSeriesSFF:pvr:rvnCompaq:rn042Ch:rvr:cvnCompaq:ct3:cvr:
  dmi.product.name: Deskpro EN Series SFF
  dmi.sys.vendor: Compaq

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

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

[Kernel-packages] [Bug 1690852] Re: package linux-headers-4.4.0-43 4.4.0-43.63 failed to install/upgrade: package linux-headers-4.4.0-43 is not ready for configuration cannot configure (current status

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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

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

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

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

Title:
  package linux-headers-4.4.0-43 4.4.0-43.63 failed to install/upgrade:
  package linux-headers-4.4.0-43 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Half installed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-43 4.4.0-43.63
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   pieter 2110 F...m pulseaudio
   /dev/snd/controlC0:  pieter 2110 F pulseaudio
  Date: Mon May 15 18:04:35 2017
  DuplicateSignature:
   package:linux-headers-4.4.0-43:4.4.0-43.63
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package linux-headers-4.4.0-43 (--configure):
package linux-headers-4.4.0-43 is not ready for configuration
  ErrorMessage: package linux-headers-4.4.0-43 is not ready for configuration  
cannot configure (current status 'half-installed')
  HibernationDevice: RESUME=UUID=b16c78db-fc6e-4b9b-a4f1-4a35190ca7a2
  InstallationDate: Installed on 2016-01-20 (481 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic 
root=UUID=1c2360f2-e2f5-4121-8519-840a5921ef81 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  Title: package linux-headers-4.4.0-43 4.4.0-43.63 failed to install/upgrade: 
package linux-headers-4.4.0-43 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG33BU
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD79951-407
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDG33BU:rvrAAD79951-407:cvn:ct2:cvr:

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  SGI XFS with ACLs, security attributes, realtime, no debug enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm not working with:
  o SGI XFS with ACLs
  o JFS
  o QNX4 filesystem

  dmesg:
  [ 2561.714841] SGI XFS with ACLs, security attributes, realtime, no debug 
enabled
  [ 2561.729326] JFS: nTxBlock = 8192, nTxLock = 65536
  [ 2561.751451] ntfs: driver 2.1.32 [Flags: R/O MODULE].
  [ 2561.785045] QNX4 filesystem 0.2.3 registered.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2218 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2218 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon May 15 15:38:14 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (659 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.165
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-05-15 (0 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1688158] RE: [Bug #1688158] Please help test kernel for iommu.passthrough=0/1

[Jeffrey Hugo]

It’s working as expected.  I see improvement with passthrough enabled
(see below).  Nate also confirmed the SMMU setup via JTAG.

Passthrough=0 -

root@null-8cfdf006971f:/home/ubuntu# fio --name=global --readonly 
--group_reporting --direct=1 --ioengine=libaio --rw=read --eta-newline=1s  
--size=1T --blocksize=512k --iodepth=32 --numjobs=1  --runtime=10s 
--name=nvme_0 --filename=/dev/nvme0n1
nvme_0: (g=0): rw=read, bs=512K-512K/512K-512K/512K-512K, ioengine=libaio, 
iodepth=32
fio-2.2.10
Starting 1 process
Jobs: 1 (f=1): [R(1)] [36.4% done] [2540MB/0KB/0KB /s] [5080/0/0 iops] [eta 
00m:07s]
Jobs: 1 (f=1): [R(1)] [45.5% done] [2539MB/0KB/0KB /s] [5077/0/0 iops] [eta 
00m:Jobs: 1 (f=1): [R(1)] [54.5% done] [2540MB/0KB/0KB /s] [5079/0/0 iops] [eta 
00m:05s]
Jobs: 1 (f=1): [R(1)] [63.6% done] [2540MB/0KB/0KB /s] [5079/0/0 iops] [eta 
00m:Jobs: 1 (f=1): [R(1)] [72.7% done] [2539MB/0KB/0KB /s] [5078/0/0 iops] [eta 
00m:03s]
Jobs: 1 (f=1): [R(1)] [81.8% done] [2539MB/0KB/0KB /s] [5078/0/0 iops] [eta 
00m:Jobs: 1 (f=1): [R(1)] [90.9% done] [2540MB/0KB/0KB /s] [5080/0/0 iops] [eta 
00m:01s]
Jobs: 1 (f=1): [R(1)] [100.0% done] [2539MB/0KB/0KB /s] [5078/0/0 iops] [eta 
00m:00s]
nvme_0: (groupid=0, jobs=1): err= 0: pid=36481: Mon May 15 17:10:26 2017
  read : io=25377MB, bw=2537.5MB/s, iops=5074, runt= 10001msec
slat (usec): min=32, max=440, avg=191.74, stdev=157.14
clat (usec): min=153, max=7641, avg=6106.54, stdev=107.40
 lat (usec): min=442, max=7904, avg=6298.45, stdev=174.49
clat percentiles (usec):
 |  1.00th=[ 5920],  5.00th=[ 5984], 10.00th=[ 6048], 20.00th=[ 6048],
 | 30.00th=[ 6112], 40.00th=[ 6112], 50.00th=[ 6112], 60.00th=[ 6112],
 | 70.00th=[ 6112], 80.00th=[ 6112], 90.00th=[ 6176], 95.00th=[ 6176],
 | 99.00th=[ 6304], 99.50th=[ 6368], 99.90th=[ 6432], 99.95th=[ 6432],
 | 99.99th=[ 7008]
bw (MB  /s): min= 2498, max= 2540, per=99.98%, avg=2536.84, stdev= 9.44
lat (usec) : 250=0.01%, 500=0.01%, 750=0.01%
lat (msec) : 2=0.01%, 4=0.02%, 10=99.96%
  cpu  : usr=3.84%, sys=96.12%, ctx=67, majf=0, minf=528
  IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=99.9%, >=64=0.0%
 submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
 complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.1%, 64=0.0%, >=64=0.0%
 issued: total=r=50754/w=0/d=0, short=r=0/w=0/d=0, drop=r=0/w=0/d=0
 latency   : target=0, window=0, percentile=100.00%, depth=32

Run status group 0 (all jobs):
   READ: io=25377MB, aggrb=2537.5MB/s, minb=2537.5MB/s, maxb=2537.5MB/s, 
mint=10001msec, maxt=10001msec

Disk stats (read/write):
  nvme0n1: ios=200550/0, merge=0/0, ticks=23848/0, in_queue=23828, util=91.79%


passthrough=1 –

root@null-8cfdf006971f:/home/ubuntu#
ing --direct=1 --ioengine=libaio --rw=read --eta-newline=1s  --size=1T 
--blocksize=512k --iodepth=32 --numjobs=1  --runtime=10s --name=nvme_0 
--filename=/dev/nvme0n1
nvme_0: (g=0): rw=read, bs=512K-512K/512K-512K/512K-512K, ioengine=libaio, 
iodepth=32
fio-2.2.10
Starting 1 process
Jobs: 1 (f=1): [R(1)] [36.4% done] [3238MB/0KB/0KB /s] [6476/0/0 iops] [eta 
00m:07s]
Jobs: 1 (f=1): [R(1)] [45.5% done] [3238MB/0KB/0KB /s] [6476/0/0 iops] [eta 
00m:Jobs: 1 (f=1): [R(1)] [54.5% done] [3239MB/0KB/0KB /s] [6477/0/0 iops] [eta 
00m:05s]
Jobs: 1 (f=1): [R(1)] [63.6% done] [3238MB/0KB/0KB /s] [6476/0/0 iops] [eta 
00m:Jobs: 1 (f=1): [R(1)] [72.7% done] [3238MB/0KB/0KB /s] [6476/0/0 iops] [eta 
00m:03s]
Jobs: 1 (f=1): [R(1)] [81.8% done] [3238MB/0KB/0KB /s] [6476/0/0 iops] [eta 
00m:Jobs: 1 (f=1): [R(1)] [90.9% done] [3239MB/0KB/0KB /s] [6477/0/0 iops] [eta 
00m:01s]
Jobs: 1 (f=1): [R(1)] [100.0% done] [3238MB/0KB/0KB /s] [6476/0/0 iops] [eta 
00m:00s]
nvme_0: (groupid=0, jobs=1): err= 0: pid=1600: Mon May 15 17:13:46 2017
  read : io=32384MB, bw=3236.8MB/s, iops=6473, runt= 10005msec
slat (usec): min=13, max=210, avg=16.19, stdev= 6.40
clat (usec): min=1505, max=9532, avg=4925.01, stdev=87.39
 lat (usec): min=1616, max=9566, avg=4941.38, stdev=86.47
clat percentiles (usec):
 |  1.00th=[ 4896],  5.00th=[ 4896], 10.00th=[ 4896], 20.00th=[ 4896],
 | 30.00th=[ 4896], 40.00th=[ 4960], 50.00th=[ 4960], 60.00th=[ 4960],
 | 70.00th=[ 4960], 80.00th=[ 4960], 90.00th=[ 4960], 95.00th=[ 4960],
 | 99.00th=[ 4960], 99.50th=[ 4960], 99.90th=[ 4960], 99.95th=[ 4960],
 | 99.99th=[ 8640]
bw (MB  /s): min= 3209, max= 3237, per=99.96%, avg=3235.57, stdev= 6.18
lat (msec) : 2=0.03%, 4=0.03%, 10=99.94%
  cpu  : usr=1.80%, sys=16.99%, ctx=64755, majf=0, minf=528
  IO depths: 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=100.0%, >=64=0.0%
 submit: 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
 complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.1%, 64=0.0%, >=64=0.0%
 issued: total=r=64767/w=0/d=0, short=r=0/w=0/d=0, drop=r=0/w=0/d=0
 latency   : target=0, window=0, percentile=100.00%, depth=32

Run status group 0 (all 

[Kernel-packages] [Bug 1687714] Re: Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter ID)" messages

[Joseph Salisbury]

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

** This bug has been marked a duplicate of bug 1521173
   AER: Corrected error received: id=00e0

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

Title:
  Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus
  Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter
  ID)" messages

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

Bug description:
  The kernel log is constantly filled with the following:

236.912499] pcieport :00:1c.5: AER: Corrected error received: id=00e5
  [  236.912545] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e5(Transmitter ID)
  [  236.912553] pcieport :00:1c.5:   device [8086:a115] error 
status/mask=1000/2000
  [  236.912558] pcieport :00:1c.5:[12] Replay Timer Timeout  

  This drains battery, CPU cycles and makes the kernel log unreadable.

  Adding pcie_aspm hides that:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open
  pcie_aspm=off"

  Present in the upstream Linux kernel (see the attachment for 4.11
  rc8).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2345 F pulseaudio
dima   4262 F pulseaudio
  Date: Tue May  2 13:34:13 2017
  InstallationDate: Installed on 2017-02-27 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
   Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1690357] Re: Computer very slow since update to Ubuntu 17.04

[Joseph Salisbury]

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

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

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

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


Thanks in advance.

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


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

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

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

Title:
  Computer very slow since update to Ubuntu 17.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading my Dell Latitude E6400, computer was running very
  slowly.

  After few search, with powertop, I found that three modules was consuming lot 
of CPU:
  - snd_hda_codec_idt
  - snd_hda_codec_generic
  - snd_hda_intel
  (like 
https://askubuntu.com/questions/91359/100-0-usage-by-audio-codec-hwc0d0-realtek)

  After adding them in /etc/modprobe.d/blacklist-snd.conf, my computer
  works again like a charm, with cost of missing sound.

  Ubuntu 4.10.0-20.22-generic 4.10.8
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0ae2ebf0-deb2-41a5-9097-993b2b8ae91c
  InstallationDate: Installed on 2016-03-03 (435 days ago)
  InstallationMedia: Xubuntu Core 15.04 - amd64 - 20150425
  MachineType: Dell Inc. Latitude E6400
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=bbcbd90b-01c5-4ac8-8b33-bdfef07019fc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-20-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-05-02 (10 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 12/21/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A20
  dmi.board.name: 0W620R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA20:bd12/21/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0W620R:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6400
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[Joseph Salisbury]

** Also affects: linux via
   http://bugzilla.kernel.org/109691
   Importance: Unknown
   Status: Unknown

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1690903] [NEW] SGI XFS with ACLs, security attributes, realtime, no debug enabled

[Cristian Aravena Romero]

Public bug reported:

I'm not working with:
o SGI XFS with ACLs
o JFS
o QNX4 filesystem

dmesg:
[ 2561.714841] SGI XFS with ACLs, security attributes, realtime, no debug 
enabled
[ 2561.729326] JFS: nTxBlock = 8192, nTxLock = 65536
[ 2561.751451] ntfs: driver 2.1.32 [Flags: R/O MODULE].
[ 2561.785045] QNX4 filesystem 0.2.3 registered.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.10.0-20-generic 4.10.0-20.22
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   caravena   2218 F...m pulseaudio
 /dev/snd/controlC0:  caravena   2218 F pulseaudio
CurrentDesktop: GNOME
Date: Mon May 15 15:38:14 2017
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (659 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-20-generic N/A
 linux-backports-modules-4.10.0-20-generic  N/A
 linux-firmware 1.165
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-05-15 (0 days ago)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug artful third-party-packages

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

Title:
  SGI XFS with ACLs, security attributes, realtime, no debug enabled

Status in linux package in Ubuntu:
  New

Bug description:
  I'm not working with:
  o SGI XFS with ACLs
  o JFS
  o QNX4 filesystem

  dmesg:
  [ 2561.714841] SGI XFS with ACLs, security attributes, realtime, no debug 
enabled
  [ 2561.729326] JFS: nTxBlock = 8192, nTxLock = 65536
  [ 2561.751451] ntfs: driver 2.1.32 [Flags: R/O MODULE].
  [ 2561.785045] QNX4 filesystem 0.2.3 registered.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2218 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2218 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon May 15 15:38:14 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (659 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.165
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-05-15 (0 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1690570] Re: dmesg CIFS VFS: src file seems to be from a different filesystem type for every file i copy/move to shared folder

[dan]

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1687719] gonzo (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-119.166~precise1-generic/gonzo__3.13.0-119.166~precise1__2017-05-15_19-22-00/results-index.html

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1687718
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-119.166~precise1-generic/fozzie__3.13.0-119.166~precise1__2017-05-15_19-19-00/results-index.html

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1687718
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-119.166~precise1-generic/fozzie__3.13.0-119.166~precise1__2017-05-15_18-49-00/results-index.html

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1687718
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1690570] Re: dmesg CIFS VFS: src file seems to be from a different filesystem type for every file i copy/move to shared folder

[dan]

ps: forgot.. add user to samba before restarting server
  smbpasswd -a d1

it worked before updates; my bad for not keeping track of installed
packages

** Changed in: samba (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/1690570

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

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

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1690570] Re: dmesg CIFS VFS: src file seems to be from a different filesystem type for every file i copy/move to shared folder

[dan]

@ChristianEhrhardt #1 - yea its me

#REPRODUCTION
-download lubuntu x64 14.04.5
-do a standard virtualbox machine clean.. no internet connection
-kernel will be 4.4.0.31
-then basic commands to install samba, cifs and basic share and mount

apt-get update
apt-get install samba cifs-utils
#at the moment samba=4.3.11 cifs-utils=6.0
-
mkdir -p /home/d1/samba/share
mkdir -p /home/d1/samba/mount
chown -R d1.d1 /home/d1/samba

nano /etc/samba/smb.conf 
[global]
security = user
workgroup = WORKGROUP"
 
[share]
path = /home/d1/samba/share
writable = yes
browsable = yes

 
   
restart smbd && restart nmbd
mount.cifs //127.0.0.1/share /home/d1/samba/mount -o username=d1,uid=d1,gid=d1
---
-at this moment the share is created and mounted; open pcmanfm copy/move any 
file to the share and it will spam your dmesg with that message
-i tried to make an apport of virtualbox machine seems it gaved some errors..

obs: 
-its the same for buntu kernel 4.4.0.75/72
-ive also tested knoppix dvd 7.6.0/kernel 4.2.6-64 and mount.cifs from lubuntu 
spammed dmesg but mountcifs loop inside knoppix did not; knoppix has 
mount.cifs.v.6.4; it might be mount.cifs problem..
-ive also tested changing sources.list to debian stable.. it has mount.cifs 
6.4; the bug appears both as mount loop and client-server

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

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

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  

[Kernel-packages] [Bug 1670706] Re: Kernel Call Trace After Disabling an ath10k Wireless Device

[Joseph Salisbury]

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

** Tags added: kernel-da-key

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

Title:
  Kernel Call Trace After Disabling an ath10k Wireless Device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Disabled a wireless adapter via NetworkManager. Got a kernel trace in
  dmesg.

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
  Network Adapter (rev 32)

  uname -r
  4.10.0-9-generic

  https://paste.ubuntu.com/24131142/

  There are also usb hot-plug messages in between ath10k related ones -
  this is because I disabled a wireless adapter and immediately plugged
  in a usb type-c dock so don't mind those.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-9-generic 4.10.0-9.11
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dima   3007 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar  7 17:28:37 2017
  InstallationDate: Installed on 2017-02-27 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-9-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open pcie_aspm=off
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-9-generic N/A
   linux-backports-modules-4.10.0-9-generic  N/A
   linux-firmware1.163
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1590543] Re: A2DP configuration does not work on Kubuntu 16.04 with stereo speaker

[Hervé Le Roy]

Until this is fixed in a future release of Kubuntu, this gist does the
job: https://gist.github.com/pylover/d68be364adac5f946887b85e6ed6e7ae

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

Title:
  A2DP configuration does not work on Kubuntu 16.04 with stereo speaker

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The mode A2DP Sink does not work with my speaker Sony SRS-BTM8. PulseAudio 
shows three options,
  - HSP / HFP
  - A2DP Sink
  - Off
  Only works HSP and off options.
  Previously with version 14.04 everything worked perfectly, but since a few 
weeks upgraded to version 16.04 does not work correctly and I can not hear HiFi 
music, only low-quality mode.

  See the video settings

  https://mega.nz/#!L8p33BSZ!pyb6hZDKRW_JBLbDJ0mxYTPtv-vzi7QMGSZv8YU5N-k

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

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

[Kernel-packages] [Bug 1690225] Re: nvidia-docker on ppc64le-ubuntu16.04 issue due to cross-thread naming if !PR_DUMPABLE

[Joseph Salisbury]

** Tags added: kernel-da-key

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

Title:
  nvidia-docker on ppc64le-ubuntu16.04  issue due to cross-thread naming
  if !PR_DUMPABLE

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Breno Henrique Leitao  - 2017-05-11 
15:30:52 ==
  The PR_DUMPABLE flag causes the pid related paths of the proc file system to 
be owned by ROOT.
  
  The implementation of pthread_set/getname_np however needs access to  
/proc//task//comm.  If PR_DUMPABLE is false this implementation is 
locked out.
  
  This patch installs a special permission function for the file "comm"  
that grants read and write access to all threads of the same group  regardless 
of the ownership of the inode.  For all other threads the  function falls back 
to the generic inode permission check.

  Nvidia-docker issue on ppc64le:

  1b3044e39a89cb1d4d5313da477e8dfea2b5232d

  This is fixed by commit 1b3044e39a89cb1d4d5313da477e8dfea2b5232d

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

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

[Kernel-packages] [Bug 1689360] Re: TCMU: Fix possible overwrite of t_data_sg's last iov[] and wrongly calculating base_command_size

[Joseph Salisbury]

** Tags added: kernel-da-key

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

Title:
  TCMU: Fix possible overwrite of t_data_sg's last iov[] and wrongly
  calculating base_command_size

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  If there has BIDI data, its first iov[] will overwrite the last
  iov[] for se_cmd->t_data_sg.

  ---uname output---
  Latest Yakkety master branch
   
  Machine Type = P8 
   
  ---Steps to Reproduce---
   Just have a system do workload using tcmu.
   
  Stack trace output:
   I have seen this in my environment:
  (gdb) print *((tcmulib_cmd->iovec)+0)
  $7 = {iov_base = 0x3fff7c3d, iov_len = 8192}
  (gdb) print *((tcmulib_cmd->iovec)+1)
  $3 = {iov_base = 0x3fff7c3da000, iov_len = 4096}
  (gdb) print *((tcmulib_cmd->iovec)+2)
  $4 = {iov_base = 0x3fff7c3dc000, iov_len = 16384}
  (gdb) print *((tcmulib_cmd->iovec)+3)
  $5 = {iov_base = 0x3fff7c3f7000, iov_len = 12288}
  (gdb) print *((tcmulib_cmd->iovec)+4)
  $6 = {iov_base = 0x1306e853c0028, iov_len = 128}  <--- bad pointer and length 
   
  cmu: Fix wrongly calculating of the base_command_size
  https://patchwork.kernel.org/patch/9687657/

  tcmu: Fix possible overwrite of t_data_sg's last iov[]
  https://patchwork.kernel.org/patch/9687565/

  tcmu: Skip Data-Out blocks before gathering Data-In buffer for BIDI
  case

  https://patchwork.kernel.org/patch/9655423/

  This patch should also be a part of these fixes. WITH BIDI op fixes.

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

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

[Kernel-packages] [Bug 1690570] SambaInstalledVersions.txt

[dan]

apport information

** Attachment added: "SambaInstalledVersions.txt"
   
https://bugs.launchpad.net/bugs/1690570/+attachment/4877000/+files/SambaInstalledVersions.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

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

[dan]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1690570/+attachment/4877002/+files/UdevLog.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1689517] Re: Displayport daisy chained displays get recognized as the same

[Joseph Salisbury]

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

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

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

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

Thanks in advance.

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

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

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

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

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

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

** Tags added: kernel-da-key

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

Title:
  Displayport daisy chained displays get recognized as the same

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

Bug description:
  Hi,

  I'm using Ubuntu 16.04.2 LTS.

  Since I upgraded to 4.4.0-77, my daisy chained displays seem to get
  recognized as the same. Before, I've been using 4.4.0-72. Booting the
  older Kernel using grub also still works.

  I'm using two Dell U2715H Displays daisy chained. (DP1-1 and DP1-8)
  Both with 2560x1440px. Simultaneously, I use my Notebook Display with
  1920x1080px. (eDP1) I have a script, which I run manually after
  startx, which sets up my environment. It does:

  xrandr --output DP1-1 --mode 2560x1440
  xrandr --output DP1-8 --mode 2560x1440
  xrandr --output DP1-8 --left-of eDP1
  xrandr --output DP1-1 --left-of DP1-8

  On 4.4.0-77 both, DP1-1 and DP1-8 show the same picture (left-of eDP1);
  whereas on 4.4.0-72,
  DP1-1 shows the picture left of DP1-8,
  and DP1-8 shows the picture left of eDP1
  as expected.

  If I take a screenshot using xfce4-screenshooter, everything seems
  fine.

  I attached the output from xrandr on both kernels, screenshots from
  both pictures and reference pictures taken with my camera for you to
  see what actually happens.

  Thanks.

  Screen 0: minimum 8 x 8, current 7040 x 1440, maximum 32767 x 32767
  eDP1 connected 1920x1080+5120+0 (normal left inverted right x axis y axis) 
309mm x 173mm
 1920x1080 60.05*+  59.93  
 1680x1050 59.9559.88  
 1600x1024 60.17  
 1400x1050 59.98  
 1600x900  60.00  
 1280x1024 60.02  
 1440x900  59.89  
 1280x960  60.00  
 1368x768  60.00  
 1360x768  59.8059.96  
 1152x864  60.00  
 1280x720  60.00  
 1024x768  60.00  
 1024x576  60.00  
 960x540   60.00  
 800x600   60.3256.25  
 864x486   60.00  
 640x480   59.94  
 720x405   60.00  
 640x360   60.00  
  DP1 disconnected (normal left inverted right x axis y axis)
  DP1-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 2048x1152 60.00  
 1920x1200 59.88  
 1920x1080 60.0050.0059.9430.0025.0024.0029.97  
  23.98  
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1200x960  59.99  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  DP1-8 connected 2560x1440+2560+0 (normal left inverted right x axis y axis) 
597mm x 336mm
 2560x1440 59.95*+
 2048x1152 60.00  
 1920x1200 59.88  
 1920x1080 60.0050.0059.9430.0025.0024.0029.97  
  23.98  
 1600x1200 60.00  
 1680x1050 59.95  
 1280x1024 75.0260.02  
 1200x960  59.99  
 1152x864  75.00  
 1280x720  60.0050.0059.94  
 1024x768  75.0860.00  
 800x600   75.0060.32  
 720x576   50.00  
 720x480   60.0059.94  
 640x480   75.0060.0059.94  
 720x400   70.08  
  HDMI1 disconnected (normal left inverted right x axis y axis)
  HDMI2 disconnected (normal left inverted right x axis y axis)
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-77-generic 

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

[dan]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1690570/+attachment/4877001/+files/UdevDb.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1689408] Re: System hang when utilising OpenGL 4.5 features

[Joseph Salisbury]

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

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

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

Title:
  System hang when utilising OpenGL 4.5 features

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  I've found this to be easily reproducible via unigine's heaven
  benchmark, which uses tessellation and other features extensively.
  Simply creating a OpenGL 4.5 context will not trigger the hang, and
  you must explicitly request an OGL 4+ context as the default will only
  be 3.0.

  On a successful trigger, the screen may flicker on and off a few times
  and eventually hang completely on a black screen, there's no way to
  recover the system from this state bar a power cycle (ie hold the
  power button).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh  1405 F pulseaudio
   /dev/snd/controlC0:  paulh  1405 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  9 09:14:09 2017
  InstallationDate: Installed on 2017-01-05 (123 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1689423] Re: annoying freezing

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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


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

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

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

Title:
  annoying freezing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My system suddenly freezes and stops working completely when i for
  example play a video online while i have a song played from my drive,
  this is becoming annoying now because it's effecting my work and the
  system keeps freezing with no any solution than forcing shutdown... i
  need some help here people.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  demolator   1745 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue May  9 03:30:13 2017
  MachineType: ASUSTeK COMPUTER INC. X556UF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=4ffdc348-2840-4817-8c12-b551c86e0534 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UF.404
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UF
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UF.404:bd05/20/2016:svnASUSTeKCOMPUTERINC.:pnX556UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X556UF
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1689537] Re: busybox: segmentation fault while ping to domain name (out of bound)

[Joseph Salisbury]

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

** Changed in: busybox (Ubuntu)
   Status: Confirmed => 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/1689537

Title:
  busybox: segmentation fault while ping to domain name (out of bound)

Status in Linux:
  Fix Released
Status in busybox package in Ubuntu:
  New

Bug description:
  when running ping on an ARM (ubuntu version 17.4):
  root@raminfp:/home/raminfp/# /bin/busybox ping google.com
  Segmentation fault (core dumped)

  strace info :

  root@raminfp:/home/raminfp/Desktop/filegir# strace /bin/busybox ping 
google.com
  execve("/bin/busybox", ["/bin/busybox", "ping", "google.com"], [/* 67 vars 
*/]) = 0
  uname({sysname="Linux", nodename="raminfp", ...}) = 0
  brk(NULL)   = 0x260a000
  brk(0x260b1c0)  = 0x260b1c0
  arch_prctl(ARCH_SET_FS, 0x260a880)  = 0
  readlink("/proc/self/exe", "/bin/busybox", 4096) = 12
  brk(0x262c1c0)  = 0x262c1c0
  brk(0x262d000)  = 0x262d000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  getuid()= 0
  getpid()= 7639
  socket(AF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(3)= 0
  socket(AF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
  connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 
ENOENT (No such file or directory)
  close(3)= 0
  open("/etc/nsswitch.conf", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=555, ...}) = 0
  read(3, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 555
  read(3, "", 4096)   = 0
  close(3)= 0
  open("/etc/host.conf", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=92, ...}) = 0
  read(3, "# The \"order\" line is only used "..., 4096) = 92
  read(3, "", 4096)   = 0
  close(3)= 0
  open("/etc/resolv.conf", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=172, ...}) = 0
  read(3, "# Dynamic resolv.conf(5) file fo"..., 4096) = 172
  read(3, "", 4096)   = 0
  close(3)= 0
  uname({sysname="Linux", nodename="raminfp", ...}) = 0
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=137281, ...}) = 0
  mmap(NULL, 137281, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc32082d000
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libnss_files.so.2", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320!\0\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0644, st_size=47608, ...}) = 0
  mmap(NULL, 2168600, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fc32061b000
  mprotect(0x7fc320626000, 2093056, PROT_NONE) = 0
  mmap(0x7fc320825000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xa000) = 0x7fc320825000
  mmap(0x7fc320827000, 22296, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc320827000
  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\0\20\5\2\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0755, st_size=1856752, ...}) = 0
  mmap(NULL, 3959200, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fc320254000
  mprotect(0x7fc320411000, 2097152, PROT_NONE) = 0
  mmap(0x7fc320611000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bd000) = 0x7fc320611000
  mmap(0x7fc320617000, 14752, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc320617000
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2", O_RDONLY|O_CLOEXEC) = 3
  read(3, 
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\f\0\0\0\0\0\0"..., 832) = 
832
  fstat(3, {st_mode=S_IFREG|0755, st_size=158512, ...}) = 0
  mmap(NULL, 2253160, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fc32002d000
  mprotect(0x7fc320052000, 2093056, PROT_NONE) = 0
  mmap(0x7fc320251000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x24000) = 0x7fc320251000
  mmap(0x7fc320253000, 360, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 

[Kernel-packages] [Bug 1687413] Re: MST display setup show shifted, flickering picture in second half of the screen

[Joseph Salisbury]

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

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

Title:
  MST display setup show shifted, flickering picture in second half of
  the screen

Status in Dell Sputnik:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to set up MST display with Intel graphics card (Dell XPS 12
  9360, Intel HD 620), but the second half of the screen is shifted
  randomly and is flickering (attached screenshot).

  uname -r
  4.10.0-14-generic


  cat ~/.xprofile
  #!/bin/sh
  xrandr --addmode DP-1 "2560x2880" && 
  xrandr --output DP-1 --above eDP-1 --mode "2560x2880" && 
  xrandr --output DP-2 --right-of DP-1 --mode "2560x2880"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  1 09:39:32 2017
  InstallationDate: Installed on 2017-04-15 (16 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  macat  2488 F pulseaudio
   /dev/snd/controlC0:  macat  2488 F pulseaudio
   /dev/snd/controlC1:  macat  2488 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-04-15 (23 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=dd205104-a1a9-4197-a36d-e96f44b97067 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-generic 4.10.3
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.157.8
  Tags:  xenial
  Uname: Linux 4.10.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1687413/+subscriptions

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

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

[dan]

apport information

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

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

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

[dan]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1690570/+attachment/4876999/+files/ProcModules.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

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

[dan]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1690570/+attachment/4876997/+files/ProcCpuinfo.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1690570] CIFSMounts.txt

[dan]

apport information

** Attachment added: "CIFSMounts.txt"
   
https://bugs.launchpad.net/bugs/1690570/+attachment/4876993/+files/CIFSMounts.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1690570] CifsVersion.txt

[dan]

apport information

** Attachment added: "CifsVersion.txt"
   
https://bugs.launchpad.net/bugs/1690570/+attachment/4876994/+files/CifsVersion.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

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

[dan]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1690570/+attachment/4876996/+files/Lspci.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

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

[dan]

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1690570/+attachment/4876992/+files/BootDmesg.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1690570] Re: dmesg CIFS VFS: src file seems to be from a different filesystem type for every file i copy/move to shared folder

[dan]

apport information

** Tags added: apport-collected trusty

** Description changed:

  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu
  
  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)
  
  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server
  
  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested
  
  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.21
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  d1 1270 F lxpanel
+ CRDA: Error: [Errno 2] No such file or directory
+ CurrentDmesg:
+  [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
+  [ 5600.091999] Key type cifs.spnego registered
+  [ 5600.092020] Key type cifs.idmap registered
+  [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
+ InstallationDate: Installed on 2017-04-30 (14 days ago)
+ InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
+ IwConfig:
+  lono wireless extensions.
+  
+  eth0  no wireless extensions.
+ Lsusb:
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: innotek GmbH VirtualBox
+ Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANGUAGE=en_US
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 vboxdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-31-generic N/A
+  linux-backports-modules-4.4.0-31-generic  N/A
+  linux-firmware1.127.22
+ RfKill:
+  
+ SambaClientRegression: Yes
+ Tags:  trusty trusty
+ Uname: Linux 4.4.0-31-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 12/01/2006
+ dmi.bios.vendor: innotek GmbH
+ dmi.bios.version: VirtualBox
+ dmi.board.name: VirtualBox
+ dmi.board.vendor: Oracle Corporation
+ dmi.board.version: 1.2
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Oracle Corporation
+ dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
+ dmi.product.name: VirtualBox
+ dmi.product.version: 1.2
+ dmi.sys.vendor: innotek GmbH

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1690570/+attachment/4876991/+files/AlsaInfo.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share 

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

[dan]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1690570/+attachment/4876998/+files/ProcInterrupts.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1690570] Dependencies.txt

[dan]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1690570/+attachment/4876995/+files/Dependencies.txt

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

Title:
  dmesg CIFS VFS: src file seems to be from a different filesystem type
  for every file i copy/move to shared folder

Status in linux package in Ubuntu:
  Incomplete
Status in samba package in Ubuntu:
  Incomplete

Bug description:
  #BASIC SETUP
  -server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu 
SMP .. i686 / samba 4.3.11
  -client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu 
SMP x86_64 / mount.cifs 6.0
  -both server and client are up-to-date
  -mount line: mount.cifs //ip/share /mountpoint -o 
username=user,password=pass,uid=buntu,gid=buntu

  #ANTERIOR WORKINGS PRIOR TO UPGRADES
  -the server worked fine prior to upgrading
  -the server had about 6 months prior to last upgrade (3 days ago)
  -the client had about 1 month prior to last upgrade (3 days ago)

  #THE PROBLEM
  -the "CIFS VFS: src file seems to be from a different filesystem type" 
appears inside dmesg for every file copy/move to server
  -the problem does not appear on connect with pcmanfm like smb://ip/share into 
the address bar
  -the problem does not appear on create,move,copy files through the mount 
straight on server

  #OTHER 
  -ive tested within virtualbox lubuntu 64 14.04.5 clean no upgrades apt-get 
install samba cifs-utils with the same problem
  -the copied/moved files seem do be fine.. checksum tested

  #EXPECTED RESULT
  -no error messages(ive read about lost files)
  -a clean workaround if possible(trough mount.cifs or samba options)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  d1 1270 F lxpanel
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [ 5600.089933] FS-Cache: Netfs 'cifs' registered for caching
   [ 5600.091999] Key type cifs.spnego registered
   [ 5600.092020] Key type cifs.idmap registered
   [ 5686.295664] CIFS VFS: src file seems to be from a different filesystem 
type
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=52e2e360-8017-437e-8fcd-994033d9eae4
  InstallationDate: Installed on 2017-04-30 (14 days ago)
  InstallationMedia: Lubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: samba 2:4.3.11+dfsg-0ubuntu0.14.04.7
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=37d0c756-8698-4989-8ead-8064a36a2b49 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.127.22
  RfKill:
   
  SambaClientRegression: Yes
  Tags:  trusty trusty
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[ChristianEhrhardt]

On Mon, May 15, 2017 at 5:10 PM, Jeff Lane 
wrote:

> Call it pebkac.  It's possible I missed the package when I manually
> updated the qemu-* packages.
>

I call it "thank you for sticking on and working through it"!
So as I understand we can set v-done now.


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

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

Title:
  Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

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

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC
    (8335-GTB)

   * This is a toleration change (no exploitation) for those HW releases
     following the SRU policy of "For Long Term Support releases we
     regularly want to enable new hardware. Such changes are appropriate
     provided that we can ensure not to affect upgrades on existing
     hardware."

   * Without the Fix that hardware won't run Xenial guests under current
     Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07
     compatibility mode (plus a few no-op changes as backport
     dependencies)

  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being
     affected.

  [Regression Potential]

   * I'd rate the potential to regress low for powerpc and next to 
 impossible for other architectures, reasons:
   * Changes are PPC only, so fallout should be contained to that
   * Patches and were created by IBM and in Upstream qemu since 2.6
   * The effective change is rather small, only allow to saner cpu model
 versions (drop some HW dev trash that was left) and add the new types.

  [Other Info]

   * Needed for certifying this Hardware for Ubuntu

  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcEnviron:
   

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[buzuk56]

Hi there,

I sent out yestaerday an email with the link to this bug report to Gigabyte 
team. 
I received an email response today from Gigabyte team. 
"Thank you for emailing GIGABYTE.
We are delighted with your interest in our products.

GIGABYTE does not support Linux OS.

Linux is  open source, everyone can compile it´s own OS.

We can´t support , sorry.
Please check with the Linux community for newer kernel version..."

Same as Mazek Andrej reported above.
Although this issue is active for more than two month it sounds that there is 
no intend from Gigabyte to tackle it despite it is specific to Gigabyte 
Motherboard. I will send back my AB350 Gaming 3 to the reseller and definitely 
buy another brand. Likely to be an ASUS.

Regards.

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1676679] Re: datapath: Add missing case OVS_TUNNEL_KEY_ATTR_PAD

[Joseph Salisbury]

Commit 8f3dbfd79ed9 was added to Zesty in version: Ubuntu-4.10.0-16.

However, Yakkety does not yet have this commit.  I built a Yakkety test
kernel with a pick of commit 8f3dbfd79ed9.  It can be downloaded from:

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

Can you test this kernel and see if it resolves this bug?

Thanks in advance!

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

Title:
  datapath: Add missing case OVS_TUNNEL_KEY_ATTR_PAD

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in openvswitch package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in openvswitch source package in Yakkety:
  New
Status in linux source package in Zesty:
  Fix Released
Status in openvswitch source package in Zesty:
  New

Bug description:
  ---Problem Description---
  Recreate and error info:

  Hit a new issue with OVS after updating to the Ubuntu 4.8 kernel from 
  the Ubuntu 4.4 kernel.

  Iperf was used to send traffic between client VMs over VXLAN. The 
  traffic did still flow, but every packet had to go to user space due to 
  the flow creation failures, which drastically impacted performance and 
  cpu utilization.

  When using VXLAN, the following error is showing up in dmesg

  openvswitch: netlink: Unknown IP tunnel attribute 14

  Also there are tons of these errors in the openvswitch log

  2017-03-01T15:50:47.860Z|00018|dpif(handler164)|WARN|system@ovs-system: 
  failed to put[create] (Invalid argument) 
  ufid:2d1a9aeb-7b24-4235-a208-a01f98237e60 recirc_id(0),dp_hash(0/0),skb_pri

  Debug showed that this attribute, OVS_TUNNEL_KEY_ATTR_PAD, was being 
  seen in the switch statement in method, static int ip_tun_from_nlattr, 
  in flow_netlink.c .  Because there is no case for this attribute, the 
  default is hit and returns an error.

  The issue was first seen using the packages in the Ubuntu 4.8 kernel, 
  which is OVS 2.5.  OVS 2.6 and 2.6.1 were also tried with the kernel 
  packages and the same issue was seen.  Tried building OVS 2.7 and 
  loading the openvswitch-datapath-dkms_2.7.0-1_all.deb that got built but 
  the issue persisted.  The proposed patch seems to eliminate the error 
  messages and also fixed the segmentation and performance issues that 
  were seen.
   
  ---uname output---
  stock 4.8 kernel
   
  Machine Type = p8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Hit a new issue with OVS after updating to the Ubuntu 4.8 kernel from 
  the Ubuntu 4.4 kernel.

  Iperf was used to send traffic between client VMs over VXLAN. The 
  traffic did still flow, but every packet had to go to user space due to 
  the flow creation failures, which drastically impacted performance and 
  cpu utilization.

  When using VXLAN, the following error is showing up in dmesg

  openvswitch: netlink: Unknown IP tunnel attribute 14

  Link to the patch is https://patchwork.ozlabs.org/patch/738856/

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

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

[Kernel-packages] [Bug 1689627] Re: [Hyper-V] add version to rdma driver to support new method to bind to ND IP interface

[Joseph Salisbury]

I built a Xenial test kernel with your patch  The test kernel can be
downloaded from:

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

Can you test this kernel and see if it resolves this bug?

Thanks in advance!

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

Title:
  [Hyper-V] add version to rdma driver to support new method to bind to
  ND IP interface

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

Bug description:
  The Linux agent (WALA) checks for module version, then decides how to
  pass the InfiniBand IP address to the RDMA driver. The new RDMA driver
  supports discovery of IP by trying to bind to all possible IP address.
  The driver needs to export the module version to have WALA use the new
  behavior.

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

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

[Kernel-packages] [Bug 1687174] Re: no wifi after software update on Dell Latitude D630

[Joseph Salisbury]

Please mark the bug as confirmed if the wifi has issues again.

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

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

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

Title:
  no wifi after software update on Dell Latitude D630

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just after software update tonight, computer lost Wifi connection and
  was not seeing any Wifi Access Point.

  --> I rebooted computer. Usually Wifi is always ON after reboot, it
  was OFF. I switch it to ON, but this did not help.

  --> I completely shutdown computer and switch on again. I find again
  after startup, Wifi is switched to OFF. I switch to ON again but
  computer can not see any Wifi Access Points.

  I checked the software update log but could not find any package
  related to Wifi / network manager :

  tail -n25 /var/log/apt/history.log

  Start-Date: 2017-04-28  21:30:08
  Commandline: aptdaemon role='role-commit-packages' sender=':1.135'
  Upgrade: gir1.2-gtk-3.0:amd64 (3.18.9-1ubuntu3.2, 3.18.9-1ubuntu3.3), 
libnss3-nssdb:amd64 (2:3.26.2-0ubuntu0.16.04.2, 2:3.28.4-0ubuntu0.16.04.1), 
libapt-inst2.0:amd64 (1.2.19, 1.2.20), appstream:amd64 (0.9.4-1ubuntu2, 
0.9.4-1ubuntu3), libsystemd0:amd64 (229-4ubuntu16, 229-4ubuntu17), 
libsystemd0:i386 (229-4ubuntu16, 229-4ubuntu17), libgtk-3-common:amd64 
(3.18.9-1ubuntu3.2, 3.18.9-1ubuntu3.3), apt:amd64 (1.2.19, 1.2.20), 
libgtk-3-0:amd64 (3.18.9-1ubuntu3.2, 3.18.9-1ubuntu3.3), libgs9:amd64 
(9.18~dfsg~0-0ubuntu2.3, 9.18~dfsg~0-0ubuntu2.4), snapd:amd64 (2.22.6, 2.24.1), 
snap-confine:amd64 (2.22.6, 2.24.1), libnspr4-0d:amd64 
(2:4.12-0ubuntu0.16.04.1, 2:4.13.1-0ubuntu0.16.04.1), udev:amd64 
(229-4ubuntu16, 229-4ubuntu17), libapt-pkg5.0:amd64 (1.2.19, 1.2.20), 
libnss3-1d:amd64 (2:3.26.2-0ubuntu0.16.04.2, 2:3.28.4-0ubuntu0.16.04.1), 
libudev1:amd64 (229-4ubuntu16, 229-4ubuntu17), libudev1:i386 (229-4ubuntu16, 
229-4ubuntu17), dpkg:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2), 
libgtk-3-bin:amd64 (3.18.9-1ubuntu3.2, 3.18.9-1ubuntu3.3), libudev-dev:amd64 
(229-4ubuntu16, 229-4ubuntu17), libgtk-3-dev:amd64 (3.18.9-1ubuntu3.2, 
3.18.9-1ubuntu3.3), systemd-sysv:amd64 (229-4ubuntu16, 229-4ubuntu17), 
chromium-codecs-ffmpeg-extra:amd64 (57.0.2987.98-0ubuntu0.16.04.1276, 
58.0.3029.81-0ubuntu0.16.04.1277), ubuntu-core-launcher:amd64 (2.22.6, 2.24.1), 
libpam-systemd:amd64 (229-4ubuntu16, 229-4ubuntu17), libgail-3-0:amd64 
(3.18.9-1ubuntu3.2, 3.18.9-1ubuntu3.3), ghostscript:amd64 
(9.18~dfsg~0-0ubuntu2.3, 9.18~dfsg~0-0ubuntu2.4), systemd:amd64 (229-4ubuntu16, 
229-4ubuntu17), mysql-common:amd64 (5.7.17-0ubuntu0.16.04.2, 
5.7.18-0ubuntu0.16.04.1), apt-utils:amd64 (1.2.19, 1.2.20), ghostscript-x:amd64 
(9.18~dfsg~0-0ubuntu2.3, 9.18~dfsg~0-0ubuntu2.4), libmysqlclient20:i386 
(5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1), libgs9-common:amd64 
(9.18~dfsg~0-0ubuntu2.3, 9.18~dfsg~0-0ubuntu2.4), thermald:amd64 (1.5-2ubuntu3, 
1.5-2ubuntu4), libnss3:amd64 (2:3.26.2-0ubuntu0.16.04.2, 
2:3.28.4-0ubuntu0.16.04.1), apt-transport-https:amd64 (1.2.19, 1.2.20), 
libappstream3:amd64 (0.9.4-1ubuntu2, 0.9.4-1ubuntu3), xsltproc:amd64 
(1.1.28-2.1, 1.1.28-2.1ubuntu0.1), libdpkg-perl:amd64 (1.18.4ubuntu1.1, 
1.18.4ubuntu1.2), libnspr4:amd64 (2:4.12-0ubuntu0.16.04.1, 
2:4.13.1-0ubuntu0.16.04.1), libxslt1.1:amd64 (1.1.28-2.1, 1.1.28-2.1ubuntu0.1), 
libxslt1.1:i386 (1.1.28-2.1, 1.1.28-2.1ubuntu0.1), dpkg-dev:amd64 
(1.18.4ubuntu1.1, 1.18.4ubuntu1.2)

  lspci -nn | grep 0280
  0c:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG 
[Golan] Network Connection [8086:4222] (rev 02)

  I could not find what was the package which caused this regression so
  can could not revert it.

  So until I get a fix, my wifi will not be working ...

  What is the full computer model number (ex. HP G32-301TX Notebook PC)?
  --> Laptop Dell Latitude D630 model PP18L

  sudo iw dev wlan0 scan | grep -i "ds parameter set"
  [sudo] password for remi:
  command failed: Network is down (-100)

  even if "Enable Networking" is ON and LAN/Ethernet connection works.

  apt-cache policy linux-firmware
  linux-firmware:
    Installed: 1.157.8
    Candidate: 1.157.8
    Version table:
   *** 1.157.8 500
  500 http://archive.linux.duke.edu/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.linux.duke.edu/ubuntu xenial-updates/main i386 
Packages
  500 http://archive.linux.duke.edu/ubuntu xenial-security/main amd64 
Packages
  500 http://archive.linux.duke.edu/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.157 500
  500 http://archive.linux.duke.edu/ubuntu xenial/main amd64 Packages
  500 http://archive.linux.duke.edu/ubuntu xenial/main i386 Packages

  cat /var/log/dmesg | grep "firmware version"
  [   

[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

[Sam Van den Eynde]

So experiencing several crashes a day (hard lock) I decided to install
the HWE 4.8 kernel using the Xenial deb files. No more lock ups have
occured since.

This seems to me an extremely critical issue at the heart of the OS. I
would have expected more visibility on this TBH.

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

Title:
  zesty unable to handle kernel NULL pointer dereference

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

Bug description:
  Upgraded to zesty about a week ago. Ran into this on latest kernel.
  (during high load, nothing in particular seems to cause it to happen).

  Did not happen with previous (4.10.0.14.16) kernel. Only after update
  to 4.10.0.15.17, has happened about 3 times since then (or other
  crashes), this is the one I could capture.

  kern.log entries below. Let me know if you need anything else from me.

  Thanks!

  
  Apr  7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL 
pointer dereference at 0018
  Apr  7 11:20:28 doe kernel: [26003.796375] IP: 
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.796404] PGD 0
  Apr  7 11:20:28 doe kernel: [26003.796405]
  Apr  7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP
  Apr  7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT 
nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep 
zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 
hid_multitouch joydev i2c_designware_platform i2c_designware_core 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp 
snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core asus_nb_wmi
  Apr  7 11:20:28 doe kernel: [26003.796722]  snd_hwdep asus_wmi sparse_keymap 
snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp 
uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops 
irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 
videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm 
elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf 
industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad 
int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi 
acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb 
int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless 
parport_pc ppdev lp parport ip_tables
  Apr  7 11:20:28 doe kernel: [26003.797026]  x_tables autofs4 algif_skcipher 
af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm 
wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  Apr  7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: 
chromium-browse Tainted: P   O4.10.0-15-generic #17-Ubuntu
  Apr  7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER 
INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015
  Apr  7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: 
c25b5ea8c000
  Apr  7 11:20:28 doe kernel: [26003.797250] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 
00010246
  Apr  7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 
0003 RCX: 0003
  Apr  7 11:20:28 doe kernel: [26003.797325] RDX:  RSI: 
9bbae7c0a000 RDI: 9bbba0418000
  Apr  7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: 
 R09: 
  Apr  7 11:20:28 doe kernel: [26003.797378] R10:  R11: 
0041 R12: 9bbb5f00a000
  Apr  7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: 
fff97000 R15: 8000
  Apr  7 11:20:28 doe kernel: [26003.797440] FS:  7f70bd1df6c0() 
GS:93c0() knlGS:
  Apr  7 11:20:28 doe kernel: [26003.797470] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr  7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 
00016942 CR4: 003406f0
  Apr  7 11:20:28 doe 

[Kernel-packages] [Bug 1689627] Re: [Hyper-V] add version to rdma driver to support new method to bind to ND IP interface

[Joseph Salisbury]

I see this patch has not landed upstream yet.   Do you also want it in
Yakkety, Zesty and Artful?

I'll build a test kernel and post it shortly.

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  [Hyper-V] add version to rdma driver to support new method to bind to
  ND IP interface

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

Bug description:
  The Linux agent (WALA) checks for module version, then decides how to
  pass the InfiniBand IP address to the RDMA driver. The new RDMA driver
  supports discovery of IP by trying to bind to all possible IP address.
  The driver needs to export the module version to have WALA use the new
  behavior.

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

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

[Kernel-packages] [Bug 1686651] Re: linux-aws: 4.4.0-1017.26 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-aws: 4.4.0-1017.26 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1686645
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1689627] Re: [Hyper-V] add version to rdma driver to support new method to bind to ND IP interface

[Joseph Salisbury]

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

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

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

** Tags added: kernel-da-key kernel-hyper-v

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

Title:
  [Hyper-V] add version to rdma driver to support new method to bind to
  ND IP interface

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

Bug description:
  The Linux agent (WALA) checks for module version, then decides how to
  pass the InfiniBand IP address to the RDMA driver. The new RDMA driver
  supports discovery of IP by trying to bind to all possible IP address.
  The driver needs to export the module version to have WALA use the new
  behavior.

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

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

[Kernel-packages] [Bug 1689787] Re: Realtek Wifi card rtl8723be [10ec:b723] WiFi does not work with Xenial-4.8 and Yakkety

[Joseph Salisbury]

Is this bug only happening with 4.8 based kernels?  Does the bug happen
with Zesty?

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

** Tags added: kernel-da-key

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

Title:
  Realtek Wifi card rtl8723be [10ec:b723] WiFi does not work with
  Xenial-4.8 and Yakkety

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Install 16.04.2 or 16.10 on HP 245 G4 Notebook PC and its wifi
  RTL8723BE PCIe Wireless Network Adapter [10ec:b723] does not work.

  --

  $ lspci -knn

  05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE 
PCIe Wireless Network Adapter [10ec:b723]
  DeviceName:  
  Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network 
Adapter [103c:804c]
  Kernel driver in use: rtl8723be
  Kernel modules: rtl8723be

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-52-generic 4.8.0-52.55
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1929 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1929 F pulseaudio
  Date: Wed May 10 06:17:41 2017
  HibernationDevice: RESUME=UUID=f3e58c36-a649-4db0-afb8-19d4acc491c0
  InstallationDate: Installed on 2017-05-05 (4 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Hewlett-Packard Test product name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic 
root=UUID=c1ee6ec3-1d6c-4bcc-92a2-b3996ef451a3 ro rootdelay=60 quiet splash 
initcall_debug net.ifnames=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-52-generic N/A
   linux-backports-modules-4.8.0-52-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: B.18
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 98.0C
  dmi.chassis.asset.tag: 75214P108U
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrB.18:bd07/15/2015:svnHewlett-Packard:pnTestproductname:pvrType1ProductConfigId:rvnHewlett-Packard:rn8133:rvrKBCVersion98.0C:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Test product name
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1689697] Re: Laptop Touchpad doesn't work at all

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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

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

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

Title:
  Laptop Touchpad  doesn't work at all

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm having Dell Inspiron 15r 5537 laptop.
  I've installed Ubuntu 16.04 after removing windows 10.
  After installation now my touchpad is not working at all. I tried external 
mouse and it is working but touchpad isn't.The touchpad was working fine with 
windows but after i installed ubuntu it stopped working.

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

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

[Kernel-packages] [Bug 1689651] Re: vblank wait timed out on crtc 0 after screen lock on Dell Latitude e6220

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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

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

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

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

Title:
  vblank wait timed out on crtc 0 after screen lock on Dell Latitude
  e6220

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After a screen lock, the screen hangs, with the attached stack dump in
  dmesg.

  I've seen multiple bug reports with similar effect, but the workaround
  has been "video=SVIDEO-1:d" as boot parameters, but this does not
  affect my case. Also, the other reports, such as
  https://bugs.freedesktop.org/show_bug.cgi?id=93782, includes
  'intel_tv_detect' which mine does not.

  lspci:
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b4)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b4)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b4)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b4)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC 
Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 04)
  02:00.0 Network controller: Broadcom Corporation BCM43228 802.11a/b/g/n
  09:00.0 SD Host controller: O2 Micro, Inc. OZ600FJ0/OZ900FJ0/OZ600FJS SD/MMC 
Card Reader Controller (rev 05)
  09:00.1 Mass storage controller: O2 Micro, Inc. Device 8231 (rev 03)

  ProblemType: Bug
  DistroRelease: elementary 0.4
  Package: linux-image-4.4.0-77-generic 4.4.0-77.98 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thoni561567 F pulseaudio
  Date: Tue May  9 22:40:05 2017
  HibernationDevice: RESUME=UUID=924774bb-ccbe-446b-a22e-2caa4b84f3b6
  InstallationDate: Installed on 2017-05-03 (5 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E6220
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic 
root=UUID=4238aca4-33a0-457b-81fa-81d7b2316a6c ro quiet splash video=SVIDEO-1:d 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0R97MN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd06/28/2013:svnDellInc.:pnLatitudeE6220:pvr01:rvnDellInc.:rn0R97MN:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6220
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1689853] Re: Kernel bug after probable OOM?

[Joseph Salisbury]

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

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

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

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

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


Thanks in advance.

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

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

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

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

Title:
  Kernel bug after probable OOM?

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Symptoms were a hung tab in Firefox (nightly) which then left a zombie
  process lingering around after introducing the processes to Mr Kill
  -KILL.

  I don't have swap configured because I like to be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed May 10 17:28:21 2017
  HibernationDevice: RESUME=UUID=fda86ae0-6316-4551-a064-a782b5d2a754
  InstallationDate: Installed on 2015-07-04 (676 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: MSI MS-7917
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=c992784f-51c3-441c-b9ae-e4e9278f2a4b ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (16 days ago)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1676679] Re: datapath: Add missing case OVS_TUNNEL_KEY_ATTR_PAD

[Joseph Salisbury]

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Released

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

Title:
  datapath: Add missing case OVS_TUNNEL_KEY_ATTR_PAD

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in openvswitch package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in openvswitch source package in Yakkety:
  New
Status in linux source package in Zesty:
  Fix Released
Status in openvswitch source package in Zesty:
  New

Bug description:
  ---Problem Description---
  Recreate and error info:

  Hit a new issue with OVS after updating to the Ubuntu 4.8 kernel from 
  the Ubuntu 4.4 kernel.

  Iperf was used to send traffic between client VMs over VXLAN. The 
  traffic did still flow, but every packet had to go to user space due to 
  the flow creation failures, which drastically impacted performance and 
  cpu utilization.

  When using VXLAN, the following error is showing up in dmesg

  openvswitch: netlink: Unknown IP tunnel attribute 14

  Also there are tons of these errors in the openvswitch log

  2017-03-01T15:50:47.860Z|00018|dpif(handler164)|WARN|system@ovs-system: 
  failed to put[create] (Invalid argument) 
  ufid:2d1a9aeb-7b24-4235-a208-a01f98237e60 recirc_id(0),dp_hash(0/0),skb_pri

  Debug showed that this attribute, OVS_TUNNEL_KEY_ATTR_PAD, was being 
  seen in the switch statement in method, static int ip_tun_from_nlattr, 
  in flow_netlink.c .  Because there is no case for this attribute, the 
  default is hit and returns an error.

  The issue was first seen using the packages in the Ubuntu 4.8 kernel, 
  which is OVS 2.5.  OVS 2.6 and 2.6.1 were also tried with the kernel 
  packages and the same issue was seen.  Tried building OVS 2.7 and 
  loading the openvswitch-datapath-dkms_2.7.0-1_all.deb that got built but 
  the issue persisted.  The proposed patch seems to eliminate the error 
  messages and also fixed the segmentation and performance issues that 
  were seen.
   
  ---uname output---
  stock 4.8 kernel
   
  Machine Type = p8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Hit a new issue with OVS after updating to the Ubuntu 4.8 kernel from 
  the Ubuntu 4.4 kernel.

  Iperf was used to send traffic between client VMs over VXLAN. The 
  traffic did still flow, but every packet had to go to user space due to 
  the flow creation failures, which drastically impacted performance and 
  cpu utilization.

  When using VXLAN, the following error is showing up in dmesg

  openvswitch: netlink: Unknown IP tunnel attribute 14

  Link to the patch is https://patchwork.ozlabs.org/patch/738856/

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

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

[Kernel-packages] [Bug 1689946] Re: Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op

[Frank Heimes]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Status: New => In Progress

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

Title:
  Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with
  split op

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
   State: Open by: mdate on 19 March 2017 12:33:34 

  On a Bolt adapter in a system with Ubuntu 16.04, I've formatted the
  Bolt for T10 and am using it to do a dd with a 2M block size.

  Here are the commands:
  nvme format /dev/nvme0n1 --lbaf=1 --pil=0 --ms=0 --pi=2

  dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1

  I get an error on the dd.
root@x1623bp1:~# dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct 
count=1
dd: error writing '/dev/nvme0n1': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 0.0525061 s, 0.0 kB/s

  dmesg shows:
  [589997.985151] blk_update_request: I/O error, dev nvme0n1, sector 0

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

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