[Kernel-packages] [Bug 1722838] Re: No sound and Microsd Card reader not working on Asus e200ha

[Kai-Heng Feng]

There's no codec support for CX2072X.
The author of CX2072X support didn't resend a new patch to address also 
maintainer's concern [1].

I guess this is something you can work on.

[1] http://mailman.alsa-project.org/pipermail/alsa-
devel/2017-April/119501.html

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

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

Title:
  No sound and Microsd Card reader not working on Asus e200ha

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed both Ubuntu 17.04 and 16.04 and neither sound or MicroSD card 
reader are working.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/2400/fd/17: Stale file handle
   Cannot stat file /proc/2400/fd/18: Stale file handle
   Cannot stat file /proc/2529/fd/11: Stale file handle
   Cannot stat file /proc/2529/fd/12: Stale file handle
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 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 0781:5406 SanDisk Corp. Cruzer Micro U3
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.303:bd12/21/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/2400/fd/17: Stale file handle
   Cannot stat file /proc/2400/fd/18: Stale file handle
   Cannot stat file /proc/2529/fd/11: Stale file handle
   Cannot stat file /proc/2529/fd/12: Stale file handle
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 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 0781:5406 SanDisk Corp. Cruzer Micro U3
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  

[Kernel-packages] [Bug 1722269] Re: No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

[Kai-Heng Feng]

Why did you use nouveau instead of nvidia? The latter one is the one
with problem, right?

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

Title:
  No graphical boot with 4.4.0-96 and NVIDIA GeForce 840M

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My computer (using XUbuntu 16.04) boots and works normally with kernel
  4.4.0-92 but upgrading to 4.4.0-96 prevents lightdm from starting. In
  fact, the GPU detection service fails.

  The problem also appears with proposed 4.4.0-97.

  I tested with mainline kernel 4.13. It boots to lightdm but it is
  difficult to exactly tell what happens as some modules for my hardware
  were not found/compiled/installed (as a result, I cannot connect to
  wifi with this kernel).

  GPU is GEForce 840M with proprietary nvidia 475 drivers (purged and
  reinstalled once).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-92-generic 4.4.0-92.115
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yann   1476 F pulseaudio
   /dev/snd/controlC0:  yann   1476 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct  9 15:40:16 2017
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (448 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-92-generic N/A
   linux-backports-modules-4.4.0-92-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yann   1438 F pulseaudio
   /dev/snd/controlC1:  yann   1438 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d967f5cb-08d3-468b-b161-2e63743f0ccd
  InstallationDate: Installed on 2016-07-18 (450 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed 
root=UUID=4ad8fadb-26cb-4b9c-9d08-ae6b7f41d91f ro
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-97-generic N/A
   linux-backports-modules-4.4.0-97-generic  N/A
   linux-firmware1.157.12
  Tags:  xenial
  Uname: Linux 4.4.0-97-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/05/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd05/05/2017:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1720197] Re: Every second(?) boot fails to display anything [MSHYBRID mode]

[Chris Halse Rogers]

Oh, it might be worth mentioning - on the boots where I wouldn't see
anything, adding the fbcon=map:1 parameter to the kernel command line
gives a usable system - the console and X¹ both come up correctly.

¹: For X there's an additional wrinkle in that the hybrid graphics
detection in gpu-detect fails to correctly identify the need for
offloading, but if I have a correct Xorg.conf already in place X will
run just fine.

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

Title:
  Every second(?) boot fails to display anything [MSHYBRID mode]

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When this laptop's firmware is set to MSHYBRID mode (intel/nvidia
  switchable graphics) it seems that every second boot it fails to
  display anything.

  This appears to be regardless of whether or not I enter the grub menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  3020 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Sep 28 13:41:53 2017
  InstallationDate: Installed on 2017-09-20 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170919)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Oryx Pro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed 
root=ZFS=rpool/system ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA1 02/20/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

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

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

[Kernel-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate

[Haw Loeung]

NOTE: That these are systems using the pcc-cpufreq and acpi-cpufreq
drivers.

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

Title:
  Keep powersave CPU frequency scaling governor for CPUs that support
  intel_pstate

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in sysvinit package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in sysvinit source package in Xenial:
  Triaged

Bug description:
  Hi,

  With the new Ubuntu archive servers, we saw constantly high load and
  after some tinkering, we found that it was mostly CPUs being woken up
  to see if they should enter idle states. Changing the CPU frequency
  scaling governor to "performance" saw a considerable drop.

  Perf report using the following commands:

  | perf record -g -a sleep 10
  | perf report

  | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906
  |   Children  Self  Command  Shared Object Symbol
  | +   55.24% 0.20%  swapper  [kernel.kallsyms] [k] 
cpu_startup_entry
  | +   53.51% 0.00%  swapper  [kernel.kallsyms] [k] 
start_secondary
  | +   53.02% 0.08%  swapper  [kernel.kallsyms] [k] 
call_cpuidle
  | +   52.94% 0.02%  swapper  [kernel.kallsyms] [k] 
cpuidle_enter
  | +   31.81% 0.67%  swapper  [kernel.kallsyms] [k] 
cpuidle_enter_state
  | +   29.59% 0.12%  swapper  [kernel.kallsyms] [k] 
acpi_idle_enter
  | +   29.45% 0.05%  swapper  [kernel.kallsyms] [k] 
acpi_idle_do_entry
  | +   29.43%29.43%  swapper  [kernel.kallsyms] [k] 
acpi_processor_ffh_cstate_enter
  | +   20.51% 0.04%  swapper  [kernel.kallsyms] [k] 
ret_from_intr
  | +   20.47% 0.12%  swapper  [kernel.kallsyms] [k] do_IRQ
  | +   19.30% 0.07%  swapper  [kernel.kallsyms] [k] 
irq_exit
  | +   19.18% 0.07%  apache2  [kernel.kallsyms] [k] 
entry_SYSCALL_64_fastpath
  | +   18.80% 0.17%  swapper  [kernel.kallsyms] [k] 
__do_softirq
  | +   16.45% 0.11%  swapper  [kernel.kallsyms] [k] 
net_rx_action
  | +   16.25% 0.43%  swapper  [kernel.kallsyms] [k] be_poll
  | +   14.74% 0.21%  swapper  [kernel.kallsyms] [k] 
be_process_rx
  | +   13.61% 0.07%  swapper  [kernel.kallsyms] [k] 
napi_gro_frags
  | +   12.58% 0.04%  swapper  [kernel.kallsyms] [k] 
netif_receive_skb_internal
  | +   12.48% 0.03%  swapper  [kernel.kallsyms] [k] 
__netif_receive_skb
  | +   12.42% 0.24%  swapper  [kernel.kallsyms] [k] 
__netif_receive_skb_core
  | +   12.41% 0.00%  apache2  [unknown] [k] 
0x7f27983b5028
  | +   12.41% 0.00%  apache2  [unknown] [k] 
0x7f2798369028
  | +   11.49% 0.16%  swapper  [kernel.kallsyms] [k] ip_rcv
  | +   11.29% 0.09%  swapper  [kernel.kallsyms] [k] 
ip_rcv_finish
  | +   10.77% 0.05%  swapper  [kernel.kallsyms] [k] 
ip_local_deliver
  | +   10.70% 0.06%  swapper  [kernel.kallsyms] [k] 
ip_local_deliver_finish
  | +   10.55% 0.22%  swapper  [kernel.kallsyms] [k] 
tcp_v4_rcv
  | +   10.10% 0.00%  apache2  [unknown] [k] 

  | +   10.01% 0.04%  swapper  [kernel.kallsyms] [k] 
tcp_v4_do_rcv

  Expanding in a few of those, you'll see:

  | -   55.24% 0.20%  swapper  [kernel.kallsyms] [k] 
cpu_startup_entry
  |- 55.04% cpu_startup_entry
  |   - 52.98% call_cpuidle
  |  + 52.93% cpuidle_enter
  |  + 0.00% ret_from_intr
  |0.00% cpuidle_enter_state
  |0.00% irq_entries_start
  |   + 1.14% cpuidle_select
  |   + 0.47% schedule_preempt_disabled
  | 0.10% rcu_idle_enter
  | 0.09% rcu_idle_exit
  |   + 0.05% ret_from_intr
  |   + 0.05% tick_nohz_idle_enter
  |   + 0.04% arch_cpu_idle_enter
  | 0.02% cpuidle_enter
  | 0.02% tick_check_broadcast_expired
  |   + 0.01% cpuidle_reflect
  | 0.01% menu_reflect
  | 0.01% atomic_notifier_call_chain
  | 0.01% local_touch_nmi
  | 0.01% cpuidle_not_available
  | 0.01% menu_select
  | 0.01% cpuidle_get_cpu_driver
  |   + 0.01% tick_nohz_idle_exit
  |   + 0.01% sched_ttwu_pending
  | 0.00% set_cpu_sd_state_idle
  | 0.00% native_irq_return_iret
  | 0.00% schedule
  |   + 0.00% arch_cpu_idle_exit
  | 0.00% 

[Kernel-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate

[Haw Loeung]

@dsmythies, sorry, missed your question. We're actually seeing
performance issues/load on a couple of our Ubuntu Archive servers
(archive.ubuntu.com). They're high traffic servers with 10GbE NICs with
just apache2 serving .deb packages from disk. We've recently upgraded a
few to 4.11.0-14-generic from linux-image-generic-hwe-16.04-edge (for
TCP BBR).

** Attachment added: "cpu usage 2017-08-23 02-11-45"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278/+attachment/4969405/+files/cpu%20usage%202017-08-23%2002-11-45.png

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

Title:
  Keep powersave CPU frequency scaling governor for CPUs that support
  intel_pstate

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in sysvinit package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in sysvinit source package in Xenial:
  Triaged

Bug description:
  Hi,

  With the new Ubuntu archive servers, we saw constantly high load and
  after some tinkering, we found that it was mostly CPUs being woken up
  to see if they should enter idle states. Changing the CPU frequency
  scaling governor to "performance" saw a considerable drop.

  Perf report using the following commands:

  | perf record -g -a sleep 10
  | perf report

  | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906
  |   Children  Self  Command  Shared Object Symbol
  | +   55.24% 0.20%  swapper  [kernel.kallsyms] [k] 
cpu_startup_entry
  | +   53.51% 0.00%  swapper  [kernel.kallsyms] [k] 
start_secondary
  | +   53.02% 0.08%  swapper  [kernel.kallsyms] [k] 
call_cpuidle
  | +   52.94% 0.02%  swapper  [kernel.kallsyms] [k] 
cpuidle_enter
  | +   31.81% 0.67%  swapper  [kernel.kallsyms] [k] 
cpuidle_enter_state
  | +   29.59% 0.12%  swapper  [kernel.kallsyms] [k] 
acpi_idle_enter
  | +   29.45% 0.05%  swapper  [kernel.kallsyms] [k] 
acpi_idle_do_entry
  | +   29.43%29.43%  swapper  [kernel.kallsyms] [k] 
acpi_processor_ffh_cstate_enter
  | +   20.51% 0.04%  swapper  [kernel.kallsyms] [k] 
ret_from_intr
  | +   20.47% 0.12%  swapper  [kernel.kallsyms] [k] do_IRQ
  | +   19.30% 0.07%  swapper  [kernel.kallsyms] [k] 
irq_exit
  | +   19.18% 0.07%  apache2  [kernel.kallsyms] [k] 
entry_SYSCALL_64_fastpath
  | +   18.80% 0.17%  swapper  [kernel.kallsyms] [k] 
__do_softirq
  | +   16.45% 0.11%  swapper  [kernel.kallsyms] [k] 
net_rx_action
  | +   16.25% 0.43%  swapper  [kernel.kallsyms] [k] be_poll
  | +   14.74% 0.21%  swapper  [kernel.kallsyms] [k] 
be_process_rx
  | +   13.61% 0.07%  swapper  [kernel.kallsyms] [k] 
napi_gro_frags
  | +   12.58% 0.04%  swapper  [kernel.kallsyms] [k] 
netif_receive_skb_internal
  | +   12.48% 0.03%  swapper  [kernel.kallsyms] [k] 
__netif_receive_skb
  | +   12.42% 0.24%  swapper  [kernel.kallsyms] [k] 
__netif_receive_skb_core
  | +   12.41% 0.00%  apache2  [unknown] [k] 
0x7f27983b5028
  | +   12.41% 0.00%  apache2  [unknown] [k] 
0x7f2798369028
  | +   11.49% 0.16%  swapper  [kernel.kallsyms] [k] ip_rcv
  | +   11.29% 0.09%  swapper  [kernel.kallsyms] [k] 
ip_rcv_finish
  | +   10.77% 0.05%  swapper  [kernel.kallsyms] [k] 
ip_local_deliver
  | +   10.70% 0.06%  swapper  [kernel.kallsyms] [k] 
ip_local_deliver_finish
  | +   10.55% 0.22%  swapper  [kernel.kallsyms] [k] 
tcp_v4_rcv
  | +   10.10% 0.00%  apache2  [unknown] [k] 

  | +   10.01% 0.04%  swapper  [kernel.kallsyms] [k] 
tcp_v4_do_rcv

  Expanding in a few of those, you'll see:

  | -   55.24% 0.20%  swapper  [kernel.kallsyms] [k] 
cpu_startup_entry
  |- 55.04% cpu_startup_entry
  |   - 52.98% call_cpuidle
  |  + 52.93% cpuidle_enter
  |  + 0.00% ret_from_intr
  |0.00% cpuidle_enter_state
  |0.00% irq_entries_start
  |   + 1.14% cpuidle_select
  |   + 0.47% schedule_preempt_disabled
  | 0.10% rcu_idle_enter
  | 0.09% rcu_idle_exit
  |   + 0.05% ret_from_intr
  |   + 0.05% tick_nohz_idle_enter
  |   + 0.04% arch_cpu_idle_enter
  | 0.02% cpuidle_enter
  | 0.02% tick_check_broadcast_expired
  |   + 0.01% cpuidle_reflect
  |

[Kernel-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate

[Haw Loeung]

** Attachment added: "load 15m 2017-08-23 02-10-53"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278/+attachment/4969406/+files/load%2015m%202017-08-23%2002-10-53.png

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

Title:
  Keep powersave CPU frequency scaling governor for CPUs that support
  intel_pstate

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in sysvinit package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in sysvinit source package in Xenial:
  Triaged

Bug description:
  Hi,

  With the new Ubuntu archive servers, we saw constantly high load and
  after some tinkering, we found that it was mostly CPUs being woken up
  to see if they should enter idle states. Changing the CPU frequency
  scaling governor to "performance" saw a considerable drop.

  Perf report using the following commands:

  | perf record -g -a sleep 10
  | perf report

  | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906
  |   Children  Self  Command  Shared Object Symbol
  | +   55.24% 0.20%  swapper  [kernel.kallsyms] [k] 
cpu_startup_entry
  | +   53.51% 0.00%  swapper  [kernel.kallsyms] [k] 
start_secondary
  | +   53.02% 0.08%  swapper  [kernel.kallsyms] [k] 
call_cpuidle
  | +   52.94% 0.02%  swapper  [kernel.kallsyms] [k] 
cpuidle_enter
  | +   31.81% 0.67%  swapper  [kernel.kallsyms] [k] 
cpuidle_enter_state
  | +   29.59% 0.12%  swapper  [kernel.kallsyms] [k] 
acpi_idle_enter
  | +   29.45% 0.05%  swapper  [kernel.kallsyms] [k] 
acpi_idle_do_entry
  | +   29.43%29.43%  swapper  [kernel.kallsyms] [k] 
acpi_processor_ffh_cstate_enter
  | +   20.51% 0.04%  swapper  [kernel.kallsyms] [k] 
ret_from_intr
  | +   20.47% 0.12%  swapper  [kernel.kallsyms] [k] do_IRQ
  | +   19.30% 0.07%  swapper  [kernel.kallsyms] [k] 
irq_exit
  | +   19.18% 0.07%  apache2  [kernel.kallsyms] [k] 
entry_SYSCALL_64_fastpath
  | +   18.80% 0.17%  swapper  [kernel.kallsyms] [k] 
__do_softirq
  | +   16.45% 0.11%  swapper  [kernel.kallsyms] [k] 
net_rx_action
  | +   16.25% 0.43%  swapper  [kernel.kallsyms] [k] be_poll
  | +   14.74% 0.21%  swapper  [kernel.kallsyms] [k] 
be_process_rx
  | +   13.61% 0.07%  swapper  [kernel.kallsyms] [k] 
napi_gro_frags
  | +   12.58% 0.04%  swapper  [kernel.kallsyms] [k] 
netif_receive_skb_internal
  | +   12.48% 0.03%  swapper  [kernel.kallsyms] [k] 
__netif_receive_skb
  | +   12.42% 0.24%  swapper  [kernel.kallsyms] [k] 
__netif_receive_skb_core
  | +   12.41% 0.00%  apache2  [unknown] [k] 
0x7f27983b5028
  | +   12.41% 0.00%  apache2  [unknown] [k] 
0x7f2798369028
  | +   11.49% 0.16%  swapper  [kernel.kallsyms] [k] ip_rcv
  | +   11.29% 0.09%  swapper  [kernel.kallsyms] [k] 
ip_rcv_finish
  | +   10.77% 0.05%  swapper  [kernel.kallsyms] [k] 
ip_local_deliver
  | +   10.70% 0.06%  swapper  [kernel.kallsyms] [k] 
ip_local_deliver_finish
  | +   10.55% 0.22%  swapper  [kernel.kallsyms] [k] 
tcp_v4_rcv
  | +   10.10% 0.00%  apache2  [unknown] [k] 

  | +   10.01% 0.04%  swapper  [kernel.kallsyms] [k] 
tcp_v4_do_rcv

  Expanding in a few of those, you'll see:

  | -   55.24% 0.20%  swapper  [kernel.kallsyms] [k] 
cpu_startup_entry
  |- 55.04% cpu_startup_entry
  |   - 52.98% call_cpuidle
  |  + 52.93% cpuidle_enter
  |  + 0.00% ret_from_intr
  |0.00% cpuidle_enter_state
  |0.00% irq_entries_start
  |   + 1.14% cpuidle_select
  |   + 0.47% schedule_preempt_disabled
  | 0.10% rcu_idle_enter
  | 0.09% rcu_idle_exit
  |   + 0.05% ret_from_intr
  |   + 0.05% tick_nohz_idle_enter
  |   + 0.04% arch_cpu_idle_enter
  | 0.02% cpuidle_enter
  | 0.02% tick_check_broadcast_expired
  |   + 0.01% cpuidle_reflect
  | 0.01% menu_reflect
  | 0.01% atomic_notifier_call_chain
  | 0.01% local_touch_nmi
  | 0.01% cpuidle_not_available
  | 0.01% menu_select
  | 0.01% cpuidle_get_cpu_driver
  |   + 0.01% tick_nohz_idle_exit
  |   + 0.01% sched_ttwu_pending
  | 0.00% set_cpu_sd_state_idle
  | 0.00% 

[Kernel-packages] [Bug 1716751] Re: zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Error occurred during install of updates.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu18
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-93-generic (x86_64)
   Tue Sep 12 15:08:17 EDT 2017
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-93-generic
  Date: Tue Sep 12 15:08:20 2017
  InstallationDate: Installed on 2015-03-08 (919 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  PackageVersion: 0.6.5.6-0ubuntu18
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-10-29 (317 days ago)

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

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

[Kernel-packages] [Bug 1723271] [NEW] Hide kerneloops applet from Startup Applications

[Jeremy Bicha]

Public bug reported:

Ubuntu still includes the Startup Applications app in the default
install (it was dropped in gnome-session upstream years ago).

To prevent users from being able to easily disable system services that
they probably shouldn't, Ubuntu makes sure that apps included by default
set NoDisplay=true in their autostart files. This hides the services
from the Startup Applications app.

Test Case
=
Open Startup Applications
Does kerneloops-applet show in the list?

Other Info
==
SSH Key Agent is intentionally in the Startup Applications list.

By the way, MATE has a similar tool but it doesn't respect NoDisplay yet.
https://github.com/mate-desktop/mate-session-manager/issues/134

** Affects: kerneloops (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: artful

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

Title:
  Hide kerneloops applet from Startup Applications

Status in kerneloops package in Ubuntu:
  Triaged

Bug description:
  Ubuntu still includes the Startup Applications app in the default
  install (it was dropped in gnome-session upstream years ago).

  To prevent users from being able to easily disable system services
  that they probably shouldn't, Ubuntu makes sure that apps included by
  default set NoDisplay=true in their autostart files. This hides the
  services from the Startup Applications app.

  Test Case
  =
  Open Startup Applications
  Does kerneloops-applet show in the list?

  Other Info
  ==
  SSH Key Agent is intentionally in the Startup Applications list.

  By the way, MATE has a similar tool but it doesn't respect NoDisplay yet.
  https://github.com/mate-desktop/mate-session-manager/issues/134

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

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

[Kernel-packages] [Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260

[Braden Maccke]

Experiencing this bug using 7265

 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59)
Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5110]
Kernel driver in use: iwlwifi


running kernel 4.8.0-53-generic, ubuntu 16.04.1 based Peppermint 8

The machine connected to 5G signals flawlessly running windows and
previous kernels, but the firmware bucks on connection to 5G signals.

it tries to load a few .ucode firmwares before settling on -22.


PIOTR from comment 6! You've got it working on 16.04!? Get at me, bro!

Pasted the relevant parts of journalctl at:
http://paste.ubuntu.com/25728936/

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

Title:
  Connecting to wifi 5GHz network causes iwlwifi firmware/driver error.
  Intel Wireless 7260

Status in Ubuntu:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Only happens when connecting to 5GHz network, 2.5 GHz work fine.
  Network controller: Intel Corporation Wireless 7260 (rev 6b)

  iwlwifi :02:00.0: loaded firmware version 17.459231.0 op_mode
  iwlmvm

  
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4289] device 
(wlan0): Activation: starting connection 'NewHibernia5' 
(104460fe-9e5b-4a8c-8735-cfe48dec488e)
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4290] audit: 
op="connection-activate" uuid="104460fe-9e5b-4a8c-8735-cfe48dec488e" 
name="NewHibernia5" pid=7054 uid=1000 result="success"
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4291] device 
(wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4293] 
manager: NetworkManager state is now CONNECTING
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4339] device 
(wlan0): set-hw-addr: set-cloned MAC address to E8:2A:EA:D4:16:6F (permanent)
  апр 14 10:32:34 liasus kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not 
ready
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4381] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4383] device 
(wlan0): Activation: (wifi) access point 'NewHibernia5' has security, but 
secrets are required.
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4384] device 
(wlan0): state change: config -> need-auth (reason 'none') [50 60 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4433] device 
(wlan0): state change: need-auth -> prepare (reason 'none') [60 40 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4438] device 
(wlan0): state change: prepare -> config (reason 'none') [40 50 0]
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4450] device 
(wlan0): Activation: (wifi) connection 'NewHibernia5' has security, and secrets 
exist.  No new secrets needed.
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4451] 
Config: added 'ssid' value 'NewHibernia5'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4451] 
Config: added 'scan_ssid' value '1'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'key_mgmt' value 'WPA-PSK'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'auth_alg' value 'OPEN'
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4452] 
Config: added 'psk' value ''
  апр 14 10:32:34 liasus NetworkManager[1435]:   [1492155154.4654] 
sup-iface[0x55900cef86c0,wlan0]: config: set interface ap_scan to 1
  апр 14 10:32:34 liasus wpa_supplicant[1923]: wlan0: SME: Trying to 
authenticate with e4:8d:8c:61:7d:04 (SSID='NewHibernia5' freq=5280 MHz)
  апр 14 10:32:34 liasus kernel: wlan0: authenticate with e4:8d:8c:61:7d:04
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: Microcode SW error 
detected.  Restarting 0x200.
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR values:
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: (2nd byte of 
CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_HW_IF_CONFIG_REG: 0X40489204
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:  
CSR_INT_COALESCING: 0X8000ff40
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_INT: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_INT_MASK: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_FH_INT_STATUS: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: 
CSR_GPIO_IN: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:   
CSR_RESET: 0X
  апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
CSR_GP_CNTRL: 0X080403cd
  апр 14 10:32:34 liasus kernel: 

[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works with Ubuntu 17.10

[Ghislain Antony Vaillant]

And it's gone again :(

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

Title:
  Two-finger scrolling no longer works with Ubuntu 17.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1723223] Re: linux-lts and linux-hwe autopkgtests fail due to version mismatch

[Eric Desrochers]

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

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

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

Title:
  linux-lts and linux-hwe autopkgtests fail due to version mismatch

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

Bug description:
  the autopkgtests for the kernel include 'ubuntu-regression-suite'
  which contains this test:

  sver=`dpkg-parsechangelog -SVersion`
  read x rver x &2
  exit 1
  fi

  
  However, when testing a -lts or -hwe kernel build, the running kernel will 
not match because the running kernel is the stock version while the 
building/testing kernel is the newer -lts/-hwe version.

  This failure results in autopkgtest errors for all other packages that
  invoke linux autopkgtests - for example, initramfs-tools.  This
  requires unnecessary work to investigate the autopkgtest errors every
  time, only to find it's a autopkgtest error.

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

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

[Kernel-packages] [Bug 1723223] Re: linux-lts and linux-hwe autopkgtests fail due to version mismatch

[Dan Streetman]

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1723223

Title:
  linux-lts and linux-hwe autopkgtests fail due to version mismatch

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

Bug description:
  the autopkgtests for the kernel include 'ubuntu-regression-suite'
  which contains this test:

  sver=`dpkg-parsechangelog -SVersion`
  read x rver x &2
  exit 1
  fi

  
  However, when testing a -lts or -hwe kernel build, the running kernel will 
not match because the running kernel is the stock version while the 
building/testing kernel is the newer -lts/-hwe version.

  This failure results in autopkgtest errors for all other packages that
  invoke linux autopkgtests - for example, initramfs-tools.  This
  requires unnecessary work to investigate the autopkgtest errors every
  time, only to find it's a autopkgtest error.

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

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

[Kernel-packages] [Bug 1723223] Re: linux-lts and linux-hwe autopkgtests fail due to version mismatch

[Dan Streetman]

For example, here is a autopkgtest failure that was flagged by my update
to initramfs-tools package:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-trusty/trusty/ppc64el/l/linux-lts-
xenial/20171012_183054_740b6@/log.gz

the failure is simply due to the ubuntu-regression-suite test:

autopkgtest [18:30:28]: test ubuntu-regression-suite: [---
Source Package Version: 4.4.0-97.120~14.04.1
Running Kernel Version: 3.13.0-133.182
ERROR: running version does not match source package


** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

Title:
  linux-lts and linux-hwe autopkgtests fail due to version mismatch

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

Bug description:
  the autopkgtests for the kernel include 'ubuntu-regression-suite'
  which contains this test:

  sver=`dpkg-parsechangelog -SVersion`
  read x rver x &2
  exit 1
  fi

  
  However, when testing a -lts or -hwe kernel build, the running kernel will 
not match because the running kernel is the stock version while the 
building/testing kernel is the newer -lts/-hwe version.

  This failure results in autopkgtest errors for all other packages that
  invoke linux autopkgtests - for example, initramfs-tools.  This
  requires unnecessary work to investigate the autopkgtest errors every
  time, only to find it's a autopkgtest error.

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

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

[Kernel-packages] [Bug 1723223] [NEW] linux-lts and linux-hwe autopkgtests fail due to version mismatch

[Dan Streetman]

Public bug reported:

the autopkgtests for the kernel include 'ubuntu-regression-suite' which
contains this test:

sver=`dpkg-parsechangelog -SVersion`
read x rver x &2
exit 1
fi


However, when testing a -lts or -hwe kernel build, the running kernel will not 
match because the running kernel is the stock version while the 
building/testing kernel is the newer -lts/-hwe version.

This failure results in autopkgtest errors for all other packages that
invoke linux autopkgtests - for example, initramfs-tools.  This requires
unnecessary work to investigate the autopkgtest errors every time, only
to find it's a autopkgtest error.

** Affects: linux (Ubuntu)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 Status: Invalid

** Affects: linux (Ubuntu Trusty)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 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/1723223

Title:
  linux-lts and linux-hwe autopkgtests fail due to version mismatch

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

Bug description:
  the autopkgtests for the kernel include 'ubuntu-regression-suite'
  which contains this test:

  sver=`dpkg-parsechangelog -SVersion`
  read x rver x &2
  exit 1
  fi

  
  However, when testing a -lts or -hwe kernel build, the running kernel will 
not match because the running kernel is the stock version while the 
building/testing kernel is the newer -lts/-hwe version.

  This failure results in autopkgtest errors for all other packages that
  invoke linux autopkgtests - for example, initramfs-tools.  This
  requires unnecessary work to investigate the autopkgtest errors every
  time, only to find it's a autopkgtest error.

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

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

[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker

[Brad Figg]

** 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
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1722299
  phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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: 1722299
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1532267] Re: 168c:0036 [Aspire E5-573G] Bluetooth not recognized

[André Kugland]

I had a similar problem, I solved it by blacklisting acer-wmi and
updating the kernel to hwe.

https://askubuntu.com/questions/791785/qualcomm-atheros-bluetooth-4-0
-not-working-on-ubuntu-16-04/964350#964350

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

Title:
  168c:0036 [Aspire E5-573G] Bluetooth not recognized

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have installed Ubuntu 14.04 on my Acer Aspire E5-573G, and the
  bluetooth was not recognized, but wifi is working perfectly. This
  problem occurred from kernel 3.19 - 4.4-rc8.

  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
   Subsystem: Lite-On Communications Inc Device [11ad:0803]
   Kernel driver in use: ath9k

  The result of lsusb;
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 003: ID 1bcf:2c81 Sunplus Innovation Technology Inc.
  Bus 001 Device 005: ID 046d:c534 Logitech, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28~14.04.1
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  8 14:41:21 2016
  InstallationDate: Installed on 2015-12-25 (13 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-wily
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lmrodrigues   2174 F pulseaudio
   /dev/snd/controlC1:  lmrodrigues   2174 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=898c0089-7a66-4b09-b59b-0953113ce894
  InstallationDate: Installed on 2015-12-25 (15 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire E5-573G
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=37df17cf-666c-4aa5-b851-ef8e5f7ce3e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-23.28~14.04.1-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.144+ar3012
  Tags:  trusty
  Uname: Linux 4.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.31:bd09/25/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573G
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -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: In Progress => Fix Released

** 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
  -- swm properties --
  kernel-stable-master-bug: 1722299
  phase: Packaging
+ kernel-stable-phase-changed:Thursday, 12. October 2017 17:33 UTC
+ kernel-stable-phase:Uploaded

** 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
  -- swm properties --
  kernel-stable-master-bug: 1722299
- phase: Packaging
- kernel-stable-phase-changed:Thursday, 12. October 2017 17:33 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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 --
  kernel-stable-master-bug: 1722299
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1723033] Re: IP: bio_uncopy_user+0xc3/0x140

[Charlie]

Started after previous days update. Previous version were OK. Just
booted using 4.13.0-14-generic i686 but now get "cups-browsed crashed
with signal 7 in elf_machine_rel_relative()" reported as bug #1723033.

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

Title:
  IP: bio_uncopy_user+0xc3/0x140

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just booted up computer.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  charlie2413 F pulseaudio
  Date: Thu Oct 12 09:16:56 2017
  Failure: oops
  InstallationDate: Installed on 2017-07-28 (75 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170725.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: NOVATECH LTD PERSONAL COMPUTER
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=650586f6-4f8f-4d72-853f-15154b747716 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: IP: bio_uncopy_user+0xc3/0x140
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: xxx-xxx
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: PERSONAL COMPUTER
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

[Hey!]

I have some more things to add.

On 4.10, if you reboot or shut down as soon as you can, it works, but it
continues to make the bios screen freeze.

I don't know if is 16.04 or a >4.4 kernel that is causing this, but it's
still present on 4.10.

When the computer reboots, i see this two failed lines before the
computer reboots:

[ Failed ] failed unmounting /rofs 
[ Failed ] failed unmouting /cdrom.mount.

Then the computer reboots and the bios freezes.

If i press the F12 (boot device selector) and wait some time, i can
choose the liveusb, but the os gets stuck on the spash screen and i can
see this message:

ata1: softreset failed (device not ...) 
No medium found can't open /dev/sr0: 
No medium found can't open /dev/sr0: 
No medium found can't open /dev/sr0: 
No medium found can't open /dev/sr0: 
No medium found can't open /dev/sr0: 

I'm testing this on a live usb btw.

Any idea?

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

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

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

[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

[Mattia]

I just downloaded the source to the newest stable kernel from
kernel.org, manually added the line that fixes this bug with a text
editor and followed this guide to compile it:
https://wiki.ubuntu.com/KernelTeam/GitKernelBuild

It's way more fun this way and you'll have the freshest stable kernel!
I've been using this method since early august and it has been working
out fine. But once 17.10 comes out I suppose this won't be a problem
anymore..

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work.

  [Test Case]
  Touchpad doesn't work on the system.
  With the patch, touchpad works.

  [Regression Potential]
  Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to
  one device.

  ---

  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Launchpad Bug Tracker]

This bug was fixed in the package dkms - 2.3-3ubuntu3

---
dkms (2.3-3ubuntu3) artful; urgency=medium

  * 0014-remove-initrd-backup.patch: When removing a kernel also remove
related .old-dkms file from /boot after its been created not before.
(LP: #1515513)

 -- Brian Murray   Thu, 05 Oct 2017 13:10:42 -0700

** Changed in: dkms (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  New
Status in dkms source package in Zesty:
  Fix Committed
Status in initramfs-tools source package in Zesty:
  New
Status in dkms package in Debian:
  New

Bug description:
  [Impact]
  If a dkms package is installed which has REMAKE_INITRD or the same setting 
has be manually configured by a user then when a kernel is removed its possible 
for an ".old-dkms" file to be left in /boot with no associated kernel.

  [Test Case]
  On a system with two old kernels and one new kernel available in -updates:
  1) install r8168-dkms
  2) install the dkms module for the old kernel e.g. 'sudo dkms install -m 
r8168 -v 8.041.00 -k 4.4.0-31-generic'
  3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
  4) sudo apt autoremove
  5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot 
without a corresponding "initrd.img-4.4.0-31-generic"

  With the version of dkms in -proposed, the .old-dkms file will be
  removed when the kernel is auto removed.

  [Regression Potential]
  Somebody out there might expect the .old-dkms file to be kept, but that seems 
like an odd expectation.

  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: BugDistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: allSourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

[Brian Murray]

Hello Jamie, or anyone else affected,

Accepted libseccomp into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libseccomp/2.3.1-2.1ubuntu2~17.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed verification-needed-zesty

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

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

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

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [libseccomp Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the 

[Kernel-packages] [Bug 1723112] Re: Stpped printer. Ubuntu 16.04 upgrade 2

[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.14 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.14-rc4

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

Title:
  Stpped printer.  Ubuntu 16.04  upgrade 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed an new hp 8710 office jet on 10/5/2017 and downloaded
  third party hp drivers from 123.hp.com.  Every thing worked just fine.
  I unfortunately upgraded 16.04 to stay current and my printer quit
  printing with a status of stopped - missing cups filter.  I've
  unplugged, rebooted, deleted printer, tried to re-download printer
  drivers - nothing works.  The only printer settings status is printer
  is not configured.

  I think this is also related to: Sorry Ubuntu 16.04 has experienced
  internal errors, that keeps appearing. HP filters have been deleted
  out of /usr/lib/cups due to an 16.04 upgrade. Now third partly
  printer drivers can't be downloaded and installed. Need help!

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

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

[Kernel-packages] [Bug 1723107] Re: Sorry Ubuntu 16.04 has experienced an internal Error

[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.14 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.14-rc4

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

Title:
  Sorry Ubuntu 16.04 has experienced an internal Error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/i386 - linux/cups-pk-helper-mechanical-package
cups-pk-helper 0.2.5 ubuntu - problem-type crash
  I think this is also related to the 16.04 stopped printer problem.  HP 
filters have been deleted out of /usr/lib/cups due to an 16.04 upgrade.  
Now third partly printer drivers can't be downloaded and installed.  My printer 
worked fine two 16.04 upgrades ago. Now nothing!  Need help.

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

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

[Kernel-packages] [Bug 1723027] Re: package linux-headers-4.13.0-15-generic 4.13.0-15.16 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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


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

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

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

Title:
  package linux-headers-4.13.0-15-generic 4.13.0-15.16 failed to
  install/upgrade: subprocess installed post-installation script was
  killed by signal (Killed)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  `ubuntu-bug linux`

  > Problem in linux-image-4.13.0-12-generic
  > The problem cannot be reported:
  >
  > This is not an official Ubuntu package. Please remove any third party 
package and try again

  ```
  cat /proc/version_signature
  Ubuntu 4.13.0-12.13-generic 4.13.3
  ```

  This process hangs on a wait4.

  ```
  root  5998  0.0  0.0  19600  4592 pts/2S+   08:41   0:00 
/usr/bin/perl /var/lib/dpkg/info/linux-headers-4.13.0-15-generic.postinst 
configure
  sudo strace -p5998
  strace: Process 5998 attached
  wait4(5999, 
  ```

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-headers-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1797 F pulseaudio
richard2253 F pulseaudio
   /dev/snd/controlC1:  gdm1797 F pulseaudio
richard2253 F pulseaudio
  Date: Thu Oct 12 08:40:57 2017
  DpkgTerminalLog:
   Setting up linux-headers-4.13.0-15-generic (4.13.0-15.16) ...
   Examining /etc/kernel/header_postinst.d.
   run-parts: executing /etc/kernel/header_postinst.d/dkms 4.13.0-15-generic 
/boot/vmlinuz-4.13.0-15-generic
   dpkg: error processing package linux-headers-4.13.0-15-generic 
(--configure):
subprocess installed post-installation script was killed by signal (Killed)
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Killed)
  HibernationDevice: RESUME=UUID=caa58ce2-ce7c-4f7e-b884-97361ab085fc
  MachineType: Notebook P65xRP
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=e4d59a1f-d0d7-4072-ad5c-013a79cfc6e1 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.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu6
  SourcePackage: linux
  Title: package linux-headers-4.13.0-15-generic 4.13.0-15.16 failed to 
install/upgrade: subprocess installed post-installation script was killed by 
signal (Killed)
  UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago)
  dmi.bios.date: 10/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65xRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd10/05/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65xRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1723032] Re: Copying data from SATA SSD to NVMe SSD causes kernel bug

[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.14 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.14-rc4

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

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

** Tags added: kernel-da-key

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

Title:
  Copying data from SATA SSD to NVMe SSD causes kernel bug

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to move my Ubuntu Server installation to a new NVMe SSD
  (Samsung EVO 960 500GB) using dd:

  sudo dd if=/dev/sda3 of=/dev/nvme0n1p3 bs=1M conv=fsync
  status=progress

  The first two partitions, EFI System and the Linux root fs, copy fine
  but copying the third partition causes the dd command to hang after a
  few seconds. If I kill the dd command the whole system freezes.

  Running Ubuntu Desktop 17.4 live image on a USB-connected SD-card

  My SATA SSD is partitioned as follows:

  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: gpt
  Disk identifier: 75902613-8162-4C99-A7CF-1642374BEDBB

  DeviceStart   End   Sectors  Size Type
  /dev/sda1  2048   1050623   1048576  512M EFI System
  /dev/sda2   1050624  59643903  58593280   28G Linux filesystem
  /dev/sda3  59643904 250068991 190425088 90.8G Linux LVM

  dmesg output:

  [  140.327890] [ cut here ]
  [  140.327914] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/drivers/nvme/host/pci.c:566!
  [  140.327940] invalid opcode:  [#1] SMP
  [  140.327953] Modules linked in: bnep snd_hda_codec_hdmi intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass 
snd_hda_codec crct10dif_pclmul crc32_pclmul snd_hda_core snd_hwdep 
ghash_clmulni_intel snd_pcm pcbc aesni_intel snd_seq_midi snd_seq_midi_event 
aes_x86_64 snd_rawmidi crypto_simd glue_helper cryptd intel_cstate snd_seq 
intel_rapl_perf snd_seq_device input_leds joydev snd_timer serio_raw snd 
hci_uart soundcore btbcm btqca btintel bluetooth mei_me mei intel_lpss_acpi 
intel_lpss mac_hid acpi_pad shpchp intel_pch_thermal parport_pc ppdev lp 
parport ip_tables x_tables autofs4 aufs nls_utf8 isofs btrfs xor raid6_pq 
nls_iso8859_1 dm_mirror dm_region_hash dm_log uas usb_storage hid_generic 
usbhid i915 i2c_algo_bit
  [  140.328186]  drm_kms_helper syscopyarea e1000e psmouse ptp pps_core nvme 
sysfillrect sysimgblt nvme_core fb_sys_fops ahci drm libahci wmi i2c_hid 
pinctrl_sunrisepoint video pinctrl_intel hid fjes
  [  140.328243] CPU: 1 PID: 170 Comm: kworker/u4:3 Not tainted 
4.10.0-19-generic #21-Ubuntu
  [  140.328267] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.22.0 for D3417-B1x07/26/2017
  [  140.328302] Workqueue: writeback wb_workfn (flush-259:0)
  [  140.328320] task: 8a80a84eab00 task.stack: 968380aac000
  [  140.328341] RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme]
  [  140.328358] RSP: 0018:968380aaf670 EFLAGS: 00010286
  [  140.328375] RAX: 0078 RBX: f200 RCX: 
1000
  [  140.328397] RDX: 0010 RSI: 0200 RDI: 
0246
  [  140.328418] RBP: 968380aaf748 R08: 8a80a1d66000 R09: 
f200
  [  140.328440] R10: 1000 R11: 8a7fbcdf R12: 
a4dfa000
  [  140.328461] R13: 0002f400 R14: 8a80a1d66000 R15: 
0200
  [  140.328483] FS:  () GS:8a80ae50() 
knlGS:
  [  140.328508] CS:  0010 DS:  ES:  CR0: 80050033
  [  140.328526] CR2: 7f0422b5f2b5 CR3: 4ba09000 CR4: 
002406e0
  [  140.328547] Call Trace:
  [  140.328560]  blk_mq_try_issue_directly+0x7e/0x100
  [  140.328576]  blk_mq_make_request+0x3cf/0x4e0
  [  140.328592]  generic_make_request+0xf2/0x1d0
  [  140.328607]  submit_bio+0x73/0x150
  [  140.328619]  ? __percpu_counter_add+0x4f/0x60
  [  140.328635]  submit_bh_wbc+0x152/0x180
  [  140.328648]  __block_write_full_page+0x176/0x360
  [  140.328664]  ? I_BDEV+0x20/0x20
  [  140.328676]  ? I_BDEV+0x20/0x20
  [  140.328688]  block_write_full_page+0x13b/0x160
  [  140.328702]  

[Kernel-packages] [Bug 1723033] Re: IP: bio_uncopy_user+0xc3/0x140

[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.14 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.14-rc4

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

Title:
  IP: bio_uncopy_user+0xc3/0x140

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just booted up computer.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  charlie2413 F pulseaudio
  Date: Thu Oct 12 09:16:56 2017
  Failure: oops
  InstallationDate: Installed on 2017-07-28 (75 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170725.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: NOVATECH LTD PERSONAL COMPUTER
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=650586f6-4f8f-4d72-853f-15154b747716 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: IP: bio_uncopy_user+0xc3/0x140
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: xxx-xxx
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: PERSONAL COMPUTER
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

[Kernel-packages] [Bug 1723145] Re: Artful update to v4.13.6 stable release

[Seth Forshee]

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

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

Title:
  Artful update to v4.13.6 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.13.6 stable release shall be
  applied:

  imx-media-of: avoid uninitialized variable warning
  usb: dwc3: ep0: fix DMA starvation by assigning req->trb on ep0
  mlxsw: spectrum: Fix EEPROM access in case of SFP/SFP+
  net: bonding: Fix transmit load balancing in balance-alb mode if specified by 
sysfs
  openvswitch: Fix an error handling path in 'ovs_nla_init_match_and_action()'
  mlxsw: spectrum: Prevent mirred-related crash on removal
  net: bonding: fix tlb_dynamic_lb default value
  net_sched: gen_estimator: fix scaling error in bytes/packets samples
  net: sched: fix use-after-free in tcf_action_destroy and tcf_del_walker
  sctp: potential read out of bounds in sctp_ulpevent_type_enabled()
  tcp: update skb->skb_mstamp more carefully
  bpf/verifier: reject BPF_ALU64|BPF_END
  tcp: fix data delivery rate
  udpv6: Fix the checksum computation when HW checksum does not apply
  ip6_gre: skb_push ipv6hdr before packing the header in ip6gre_header
  net: phy: Fix mask value write on gmii2rgmii converter speed register
  ip6_tunnel: do not allow loading ip6_tunnel if ipv6 is disabled in cmdline
  net/sched: cls_matchall: fix crash when used with classful qdisc
  8139too: revisit napi_complete_done() usage
  bpf: do not disable/enable BH in bpf_map_free_id()
  tcp: fastopen: fix on syn-data transmit failure
  net: emac: Fix napi poll list corruption
  net: ipv6: fix regression of no RTM_DELADDR sent after DAD failure
  packet: hold bind lock when rebinding to fanout hook
  bpf: one perf event close won't free bpf program attached by another perf 
event
  net: change skb->mac_header when Generic XDP calls adjust_head
  isdn/i4l: fetch the ppp_write buffer in one shot
  net_sched: always reset qdisc backlog in qdisc_reset()
  net: stmmac: Cocci spatch "of_table"
  net: qcom/emac: specify the correct size when mapping a DMA buffer
  vti: fix use after free in vti_tunnel_xmit/vti6_tnl_xmit
  l2tp: fix race condition in l2tp_tunnel_delete
  tun: bail out from tun_get_user() if the skb is empty
  net: dsa: mv88e6xxx: Allow dsa and cpu ports in multiple vlans
  net: dsa: Fix network device registration order
  packet: in packet_do_bind, test fanout with bind_lock held
  packet: only test po->has_vnet_hdr once in packet_snd
  net: dsa: mv88e6xxx: lock mutex when freeing IRQs
  net: Set sk_prot_creator when cloning sockets to the right proto
  net/mlx5e: IPoIB, Fix access to invalid memory address
  netlink: do not proceed if dump's start() errs
  ip6_gre: ip6gre_tap device should keep dst
  ip6_tunnel: update mtu properly for ARPHRD_ETHER tunnel device in tx path
  IPv4: early demux can return an error code
  tipc: use only positive error codes in messages
  l2tp: fix l2tp_eth module loading
  socket, bpf: fix possible use after free
  net: rtnetlink: fix info leak in RTM_GETSTATS call
  bpf: fix bpf_tail_call() x64 JIT
  usb: gadget: core: fix ->udc_set_speed() logic
  USB: gadgetfs: Fix crash caused by inadequate synchronization
  USB: gadgetfs: fix copy_to_user while holding spinlock
  usb: gadget: udc: atmel: set vbus irqflags explicitly
  usb: gadget: udc: renesas_usb3: fix for no-data control transfer
  usb: gadget: udc: renesas_usb3: fix Pn_RAMMAP.Pn_MPKT value
  usb: gadget: udc: renesas_usb3: Fix return value of usb3_write_pipe()
  usb-storage: unusual_devs entry to fix write-access regression for Seagate 
external drives
  usb-storage: fix bogus hardware error messages for ATA pass-thru devices
  usb: renesas_usbhs: fix the BCLR setting condition for non-DCP pipe
  usb: renesas_usbhs: fix usbhsf_fifo_clear() for RX direction
  ALSA: usb-audio: Check out-of-bounds access by corrupted buffer descriptor
  usb: pci-quirks.c: Corrected timeout values used in handshake
  USB: cdc-wdm: ignore -EPIPE from GetEncapsulatedResponse
  USB: dummy-hcd: fix connection failures (wrong speed)
  USB: dummy-hcd: fix infinite-loop resubmission bug
  USB: dummy-hcd: Fix erroneous synchronization change
  USB: devio: Prevent 

[Kernel-packages] [Bug 1715866] Re: Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

[Pawel Grycz]

kernel-fixed-upstream

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

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality with frequent disconnections. All this makes equipments with
  ralink wifi cards unable to work under linux distros and there're
  thousands of them.

  Recently found modded drivers for RT3290 which installed without any
  issues and wifi worked after that like a charm, but after system
  reinstall I can't install theese modded drivers anymore and there're
  some issues during installation and loading kernel modules (maybe it's
  something with latest linux kernels)...

  Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
  cause it's a wrong piece of code and Ubuntu maintainers should fix
  this.

  BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is 
seriously critical.
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pawel  2113 F pulseaudio
   /dev/snd/controlC0:  pawel  2113 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-09-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUSTeK COMPUTER INC. X750JB
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  zesty
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X750JB.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X750JB
  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.:bvrX750JB.208:bd08/14/2013:svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X750JB
  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/1715866/+subscriptions

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

Re: [Kernel-packages] [Bug 1715866] Re: Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

[Pawel Grycz]

not sure where to add the tag "kernel-fixed-upstream" as with kernel 4.13.x
this issue disappeared. Only bluetooth module (also come within Ralink
RT3290 module) doesn't work and needs custom compile/installation to be
found and activated by the system.

2017-09-08 20:03 GMT+02:00 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.13 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.13
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => High
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> ** Tags added: kernel-da-key
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1715866
>
> Title:
>   Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
>   immediately but it doesn't work at all even it "connects" and says
>   connection established with good quality - it's poor and almost zero
>   quality with frequent disconnections. All this makes equipments with
>   ralink wifi cards unable to work under linux distros and there're
>   thousands of them.
>
>   Recently found modded drivers for RT3290 which installed without any
>   issues and wifi worked after that like a charm, but after system
>   reinstall I can't install theese modded drivers anymore and there're
>   some issues during installation and loading kernel modules (maybe it's
>   something with latest linux kernels)...
>
>   Anyway it's pointess to use RT2800pci driver for physical RT3290 chip
>   cause it's a wrong piece of code and Ubuntu maintainers should fix
>   this.
>
>   BTW Bluetooth RT3290 doesn't work at all but making RT3290 wifi works is
> seriously critical.
>   ---
>   ApportVersion: 2.20.4-0ubuntu4.5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  pawel  2113 F pulseaudio
>/dev/snd/controlC0:  pawel  2113 F pulseaudio
>   CurrentDesktop: Unity:Unity7
>   DistroRelease: Ubuntu 17.04
>   InstallationDate: Installed on 2017-09-08 (0 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
>   MachineType: ASUSTeK COMPUTER INC. X750JB
>   NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>   Package: linux (not installed)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed
> root=UUID=cb519ab1-5f5d-444e-9f92-b628ae93156e ro quiet splash
> vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
>   RelatedPackageVersions:
>linux-restricted-modules-4.10.0-33-generic N/A
>linux-backports-modules-4.10.0-33-generic  N/A
>linux-firmware 1.164.1
>   RfKill:
>0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>   Tags:  zesty
>   Uname: Linux 4.10.0-33-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 08/14/2013
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: X750JB.208
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: X750JB
>   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.:bvrX750JB.208:bd08/14/2013:
> svnASUSTeKCOMPUTERINC.:pnX750JB:pvr1.0:rvnASUSTeKCOMPUTERINC.:
> rnX750JB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>   dmi.product.name: X750JB
>   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/
> 1715866/+subscriptions
>

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

Title:
  Ralink wifi RT3290 on Ubuntu 17.04 critical driver issues

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ubuntu 17.04 is installed wifi Ralink RT3290 is recognized
  immediately but it doesn't work at all even it "connects" and says
  connection established with good quality - it's poor and almost zero
  quality 

[Kernel-packages] [Bug 1723145] Re: Artful update to v4.13.6 stable release

[Seth Forshee]

** Description changed:

  SRU Justification
  
  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The v4.13.6 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.
  
     git://git.kernel.org/
  
  TEST CASE: TBD
  
     The following patches from the v4.13.6 stable release shall be
  applied:
  
  imx-media-of: avoid uninitialized variable warning
  usb: dwc3: ep0: fix DMA starvation by assigning req->trb on ep0
  mlxsw: spectrum: Fix EEPROM access in case of SFP/SFP+
  net: bonding: Fix transmit load balancing in balance-alb mode if specified by 
sysfs
  openvswitch: Fix an error handling path in 'ovs_nla_init_match_and_action()'
  mlxsw: spectrum: Prevent mirred-related crash on removal
  net: bonding: fix tlb_dynamic_lb default value
  net_sched: gen_estimator: fix scaling error in bytes/packets samples
  net: sched: fix use-after-free in tcf_action_destroy and tcf_del_walker
  sctp: potential read out of bounds in sctp_ulpevent_type_enabled()
  tcp: update skb->skb_mstamp more carefully
  bpf/verifier: reject BPF_ALU64|BPF_END
  tcp: fix data delivery rate
  udpv6: Fix the checksum computation when HW checksum does not apply
  ip6_gre: skb_push ipv6hdr before packing the header in ip6gre_header
  net: phy: Fix mask value write on gmii2rgmii converter speed register
  ip6_tunnel: do not allow loading ip6_tunnel if ipv6 is disabled in cmdline
  net/sched: cls_matchall: fix crash when used with classful qdisc
  8139too: revisit napi_complete_done() usage
  bpf: do not disable/enable BH in bpf_map_free_id()
  tcp: fastopen: fix on syn-data transmit failure
  net: emac: Fix napi poll list corruption
  net: ipv6: fix regression of no RTM_DELADDR sent after DAD failure
  packet: hold bind lock when rebinding to fanout hook
  bpf: one perf event close won't free bpf program attached by another perf 
event
  net: change skb->mac_header when Generic XDP calls adjust_head
  isdn/i4l: fetch the ppp_write buffer in one shot
  net_sched: always reset qdisc backlog in qdisc_reset()
  net: stmmac: Cocci spatch "of_table"
  net: qcom/emac: specify the correct size when mapping a DMA buffer
  vti: fix use after free in vti_tunnel_xmit/vti6_tnl_xmit
  l2tp: fix race condition in l2tp_tunnel_delete
  tun: bail out from tun_get_user() if the skb is empty
  net: dsa: mv88e6xxx: Allow dsa and cpu ports in multiple vlans
  net: dsa: Fix network device registration order
  packet: in packet_do_bind, test fanout with bind_lock held
  packet: only test po->has_vnet_hdr once in packet_snd
  net: dsa: mv88e6xxx: lock mutex when freeing IRQs
  net: Set sk_prot_creator when cloning sockets to the right proto
  net/mlx5e: IPoIB, Fix access to invalid memory address
  netlink: do not proceed if dump's start() errs
  ip6_gre: ip6gre_tap device should keep dst
  ip6_tunnel: update mtu properly for ARPHRD_ETHER tunnel device in tx path
  IPv4: early demux can return an error code
  tipc: use only positive error codes in messages
  l2tp: fix l2tp_eth module loading
  socket, bpf: fix possible use after free
  net: rtnetlink: fix info leak in RTM_GETSTATS call
  bpf: fix bpf_tail_call() x64 JIT
  usb: gadget: core: fix ->udc_set_speed() logic
  USB: gadgetfs: Fix crash caused by inadequate synchronization
  USB: gadgetfs: fix copy_to_user while holding spinlock
  usb: gadget: udc: atmel: set vbus irqflags explicitly
  usb: gadget: udc: renesas_usb3: fix for no-data control transfer
  usb: gadget: udc: renesas_usb3: fix Pn_RAMMAP.Pn_MPKT value
  usb: gadget: udc: renesas_usb3: Fix return value of usb3_write_pipe()
  usb-storage: unusual_devs entry to fix write-access regression for Seagate 
external drives
  usb-storage: fix bogus hardware error messages for ATA pass-thru devices
  usb: renesas_usbhs: fix the BCLR setting condition for non-DCP pipe
  usb: renesas_usbhs: fix usbhsf_fifo_clear() for RX direction
  ALSA: usb-audio: Check out-of-bounds access by corrupted buffer descriptor
  usb: pci-quirks.c: Corrected timeout values used in handshake
  USB: cdc-wdm: ignore -EPIPE from GetEncapsulatedResponse
  USB: dummy-hcd: fix connection failures (wrong speed)
  USB: dummy-hcd: fix infinite-loop resubmission bug
  USB: dummy-hcd: Fix erroneous synchronization change
  USB: devio: Prevent integer overflow in proc_do_submiturb()
  USB: devio: Don't corrupt user memory
  USB: g_mass_storage: Fix deadlock when driver is unbound
  USB: uas: fix bug in handling of alternate settings
  USB: core: harden cdc_parse_cdc_header
  usb: Increase quirk delay for USB devices
  USB: fix out-of-bounds in usb_set_configuration
  usb: xhci: Free the right ring in xhci_add_endpoint()
  

[Kernel-packages] [Bug 1723127] Re: Intel i40e PF reset due to incorrect MDD detection (continues...)

[Dan Streetman]

> We'll test the regular hwe 4.10 also if you think that narrows the
bisect.

yes please it will help to look just between 4.4 and 4.10.  thanks!

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  Intel i40e PF reset due to incorrect MDD detection (continues...)

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

Bug description:
  This is a continuation from bug 1713553; a patch was added in that bug
  to attempt to fix this, and it may have helped reduce the issue but
  appears not to have fixed it, based on more reports.

  The issue is the i40e driver, when TSO is enabled, sometimes sees the
  NIC firmware issue a "MDD event" where MDD is "Malicious Driver
  Detection".  This is vaguely defined in the i40e spec, but with no way
  to tell what the NIC actually saw that it didn't like.  So, the driver
  can do nothing but print an error message and reset the PF (or VF).
  Unfortunately, this resets the interface, which causes an interruption
  in network traffic flow while the PF is resetting.

  See bug 1713553 for more details.

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

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

[Kernel-packages] [Bug 1723127] Re: Intel i40e PF reset due to incorrect MDD detection (continues...)

[Eric Desrochers]

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

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

Title:
  Intel i40e PF reset due to incorrect MDD detection (continues...)

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

Bug description:
  This is a continuation from bug 1713553; a patch was added in that bug
  to attempt to fix this, and it may have helped reduce the issue but
  appears not to have fixed it, based on more reports.

  The issue is the i40e driver, when TSO is enabled, sometimes sees the
  NIC firmware issue a "MDD event" where MDD is "Malicious Driver
  Detection".  This is vaguely defined in the i40e spec, but with no way
  to tell what the NIC actually saw that it didn't like.  So, the driver
  can do nothing but print an error message and reset the PF (or VF).
  Unfortunately, this resets the interface, which causes an interruption
  in network traffic flow while the PF is resetting.

  See bug 1713553 for more details.

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

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

[Kernel-packages] [Bug 1723127] Re: Intel i40e PF reset due to incorrect MDD detection (continues...)

[Björn Zettergren]

We've been using hwe-edge 4.11 for almost 24 hours without problems.
We'll test the regular hwe 4.10 also if you think that narrows the
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/1723127

Title:
  Intel i40e PF reset due to incorrect MDD detection (continues...)

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

Bug description:
  This is a continuation from bug 1713553; a patch was added in that bug
  to attempt to fix this, and it may have helped reduce the issue but
  appears not to have fixed it, based on more reports.

  The issue is the i40e driver, when TSO is enabled, sometimes sees the
  NIC firmware issue a "MDD event" where MDD is "Malicious Driver
  Detection".  This is vaguely defined in the i40e spec, but with no way
  to tell what the NIC actually saw that it didn't like.  So, the driver
  can do nothing but print an error message and reset the PF (or VF).
  Unfortunately, this resets the interface, which causes an interruption
  in network traffic flow while the PF is resetting.

  See bug 1713553 for more details.

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

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

[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

[rubo77]

I tried that like described here: https://askubuntu.com/a/963779/34298

And installing the latest mainline Kernel 14.4-rc4 will get the Touchpad
running, but it also adds a new bug: IP4 is not running with the new
Kernel on the Lenovo 720-15IKB:
https://unix.stackexchange.com/questions/397708/get-ip4-running-with-
kernel-4-14-rc4

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work.

  [Test Case]
  Touchpad doesn't work on the system.
  With the patch, touchpad works.

  [Regression Potential]
  Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to
  one device.

  ---

  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1723145] [NEW] Artful update to v4.13.6 stable release

[Seth Forshee]

Public bug reported:

SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.13.6 stable release shall be
applied:

imx-media-of: avoid uninitialized variable warning
usb: dwc3: ep0: fix DMA starvation by assigning req->trb on ep0
mlxsw: spectrum: Fix EEPROM access in case of SFP/SFP+
net: bonding: Fix transmit load balancing in balance-alb mode if specified by 
sysfs
openvswitch: Fix an error handling path in 'ovs_nla_init_match_and_action()'
mlxsw: spectrum: Prevent mirred-related crash on removal
net: bonding: fix tlb_dynamic_lb default value
net_sched: gen_estimator: fix scaling error in bytes/packets samples
net: sched: fix use-after-free in tcf_action_destroy and tcf_del_walker
sctp: potential read out of bounds in sctp_ulpevent_type_enabled()
tcp: update skb->skb_mstamp more carefully
bpf/verifier: reject BPF_ALU64|BPF_END
tcp: fix data delivery rate
udpv6: Fix the checksum computation when HW checksum does not apply
ip6_gre: skb_push ipv6hdr before packing the header in ip6gre_header
net: phy: Fix mask value write on gmii2rgmii converter speed register
ip6_tunnel: do not allow loading ip6_tunnel if ipv6 is disabled in cmdline
net/sched: cls_matchall: fix crash when used with classful qdisc
8139too: revisit napi_complete_done() usage
bpf: do not disable/enable BH in bpf_map_free_id()
tcp: fastopen: fix on syn-data transmit failure
net: emac: Fix napi poll list corruption
net: ipv6: fix regression of no RTM_DELADDR sent after DAD failure
packet: hold bind lock when rebinding to fanout hook
bpf: one perf event close won't free bpf program attached by another perf event
net: change skb->mac_header when Generic XDP calls adjust_head
isdn/i4l: fetch the ppp_write buffer in one shot
net_sched: always reset qdisc backlog in qdisc_reset()
net: stmmac: Cocci spatch "of_table"
net: qcom/emac: specify the correct size when mapping a DMA buffer
vti: fix use after free in vti_tunnel_xmit/vti6_tnl_xmit
l2tp: fix race condition in l2tp_tunnel_delete
tun: bail out from tun_get_user() if the skb is empty
net: dsa: mv88e6xxx: Allow dsa and cpu ports in multiple vlans
net: dsa: Fix network device registration order
packet: in packet_do_bind, test fanout with bind_lock held
packet: only test po->has_vnet_hdr once in packet_snd
net: dsa: mv88e6xxx: lock mutex when freeing IRQs
net: Set sk_prot_creator when cloning sockets to the right proto
net/mlx5e: IPoIB, Fix access to invalid memory address
netlink: do not proceed if dump's start() errs
ip6_gre: ip6gre_tap device should keep dst
ip6_tunnel: update mtu properly for ARPHRD_ETHER tunnel device in tx path
IPv4: early demux can return an error code
tipc: use only positive error codes in messages
l2tp: fix l2tp_eth module loading
socket, bpf: fix possible use after free
net: rtnetlink: fix info leak in RTM_GETSTATS call
bpf: fix bpf_tail_call() x64 JIT
usb: gadget: core: fix ->udc_set_speed() logic
USB: gadgetfs: Fix crash caused by inadequate synchronization
USB: gadgetfs: fix copy_to_user while holding spinlock
usb: gadget: udc: atmel: set vbus irqflags explicitly
usb: gadget: udc: renesas_usb3: fix for no-data control transfer
usb: gadget: udc: renesas_usb3: fix Pn_RAMMAP.Pn_MPKT value
usb: gadget: udc: renesas_usb3: Fix return value of usb3_write_pipe()
usb-storage: unusual_devs entry to fix write-access regression for Seagate 
external drives
usb-storage: fix bogus hardware error messages for ATA pass-thru devices
usb: renesas_usbhs: fix the BCLR setting condition for non-DCP pipe
usb: renesas_usbhs: fix usbhsf_fifo_clear() for RX direction
ALSA: usb-audio: Check out-of-bounds access by corrupted buffer descriptor
usb: pci-quirks.c: Corrected timeout values used in handshake
USB: cdc-wdm: ignore -EPIPE from GetEncapsulatedResponse
USB: dummy-hcd: fix connection failures (wrong speed)
USB: dummy-hcd: fix infinite-loop resubmission bug
USB: dummy-hcd: Fix erroneous synchronization change
USB: devio: Prevent integer overflow in proc_do_submiturb()
USB: devio: Don't corrupt user memory
USB: g_mass_storage: Fix deadlock when driver is unbound
USB: uas: fix bug in handling of alternate settings
USB: core: harden cdc_parse_cdc_header
usb: Increase quirk delay for USB devices
USB: fix out-of-bounds in usb_set_configuration
usb: xhci: Free the right ring in xhci_add_endpoint()
xhci: fix finding correct bus_state structure for USB 3.1 hosts
xhci: fix wrong endpoint ESIT value shown in tracing
usb: host: xhci-plat: allow sysdev to inherit from ACPI
xhci: Fix sleeping 

[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

[F. H.]

The simplest way is to install the latest linux mainline kernel on Ubuntu:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Just download and "dpkg -i" the corresponding .deb packages.

Further instructions how to install mainline kernels on Ubuntu:
https://wiki.ubuntu.com/Kernel/MainlineBuilds

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work.

  [Test Case]
  Touchpad doesn't work on the system.
  With the patch, touchpad works.

  [Regression Potential]
  Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to
  one device.

  ---

  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1723127] Re: Intel i40e PF reset due to incorrect MDD detection (continues...)

[Dan Streetman]

continuing conversation from previous (fix released) bug.

@bjozet, it would help a lot of you could test with the hwe 4.10 kernel
and let me know if that fails also, or if it seems to be fixed there.
If it works, I can review the changes and possibly find something,
and/or work with you on a 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/1723127

Title:
  Intel i40e PF reset due to incorrect MDD detection (continues...)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a continuation from bug 1713553; a patch was added in that bug
  to attempt to fix this, and it may have helped reduce the issue but
  appears not to have fixed it, based on more reports.

  The issue is the i40e driver, when TSO is enabled, sometimes sees the
  NIC firmware issue a "MDD event" where MDD is "Malicious Driver
  Detection".  This is vaguely defined in the i40e spec, but with no way
  to tell what the NIC actually saw that it didn't like.  So, the driver
  can do nothing but print an error message and reset the PF (or VF).
  Unfortunately, this resets the interface, which causes an interruption
  in network traffic flow while the PF is resetting.

  See bug 1713553 for more details.

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

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

[Kernel-packages] [Bug 1713553] Re: Intel i40e PF reset due to incorrect MDD detection

[Dan Streetman]

> however we're still experiencing problems with the newest kernel

well, I was afraid of that.  As this problem is the NIC firmware
complaining but not actually telling us what it's unhappy with, there's
a bit of trial-and-error here figuring out what exactly it's complaining
about.

Since this bug is already 'fix released', I opened a new bug 1723127 to
track continuing work on this, let's move the discussion over there.

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

Title:
  Intel i40e PF reset due to incorrect MDD detection

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

Bug description:
  [Impact]

  Using an Intel i40e network device, under heavy traffic load with
  TSO enabled, the device will spontaneously reset itself and issue errors
  similar to the following:

  Jun 14 14:09:51 hostname kernel: [4253913.851053] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:53 hostname kernel: [4253915.476283] i40e :05:00.1: TX 
driver issue detected, PF reset issued
  Jun 14 14:09:54 hostname kernel: [4253917.411264] i40e :05:00.1: TX 
driver issue detected, PF reset issued

   This causes a full reset of the PF, which causes an interruption
  in traffic flow.

  This was partially fixed by Xenial commit
  12f8cc59d5886b86372f45290166deca57a60d7a, however there is one
  additional upstream commit required to fully fix the issue:

  commit 841493a3f64395b60554afbcaa17f4350f90e764
  Author: Alexander Duyck 
  Date:   Tue Sep 6 18:05:04 2016 -0700

  i40e: Limit TX descriptor count in cases where frag size is
  greater than 16K

   This fix was never backported into the Xenial 4.4 kernel series, but
  is already present in the Xenial HWE (and Zesty) 4.10 kernel.

  [Testcase]

   In this case, the issue occurs at a customer site using i40e based
  Intel network cards with SR-IOV enabled. Under heavy load, the card will
  reset itself as described.

  [Regression Potential]

  As with any change to a network card driver, this may cause
  regressions with network I/O through i40e card(s).  However, this
  specific change only increases the likelyhood that any specific large
  TSO tx will need to be linearized, which will avoid the PF reset.
  Linearizing a TSO tx that did not need to be linearized will not cause
  any failures, it may only decrease performance slightly.  However this
  patch should only cause linearization when required to avoid the MDD
  detection and PF reset.

  [Other Info]

  The previous bug for this issue is bug 1700834.

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

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

[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

[rubo77]

can someone please add a link to a instruction for someone who has never
heard of "compile your kernel with the patch" that explains step by step
the commands, they have to enter on the console please?

Or someone who managed to do this already serves the patched 4.13 kernel
with a working touchpad?

We need a workaround for everyone here until this is solved.

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work.

  [Test Case]
  Touchpad doesn't work on the system.
  With the patch, touchpad works.

  [Regression Potential]
  Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to
  one device.

  ---

  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1723127] [NEW] Intel i40e PF reset due to incorrect MDD detection (continues...)

[Dan Streetman]

Public bug reported:

This is a continuation from bug 1713553; a patch was added in that bug
to attempt to fix this, and it may have helped reduce the issue but
appears not to have fixed it, based on more reports.

The issue is the i40e driver, when TSO is enabled, sometimes sees the
NIC firmware issue a "MDD event" where MDD is "Malicious Driver
Detection".  This is vaguely defined in the i40e spec, but with no way
to tell what the NIC actually saw that it didn't like.  So, the driver
can do nothing but print an error message and reset the PF (or VF).
Unfortunately, this resets the interface, which causes an interruption
in network traffic flow while the PF is resetting.

See bug 1713553 for more details.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  Intel i40e PF reset due to incorrect MDD detection (continues...)

Status in linux package in Ubuntu:
  In Progress

Bug description:
  This is a continuation from bug 1713553; a patch was added in that bug
  to attempt to fix this, and it may have helped reduce the issue but
  appears not to have fixed it, based on more reports.

  The issue is the i40e driver, when TSO is enabled, sometimes sees the
  NIC firmware issue a "MDD event" where MDD is "Malicious Driver
  Detection".  This is vaguely defined in the i40e spec, but with no way
  to tell what the NIC actually saw that it didn't like.  So, the driver
  can do nothing but print an error message and reset the PF (or VF).
  Unfortunately, this resets the interface, which causes an interruption
  in network traffic flow while the PF is resetting.

  See bug 1713553 for more details.

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

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1723107

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

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

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

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

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

Title:
  Sorry Ubuntu 16.04 has experienced an internal Error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/i386 - linux/cups-pk-helper-mechanical-package
cups-pk-helper 0.2.5 ubuntu - problem-type crash
  I think this is also related to the 16.04 stopped printer problem.  HP 
filters have been deleted out of /usr/lib/cups due to an 16.04 upgrade.  
Now third partly printer drivers can't be downloaded and installed.  My printer 
worked fine two 16.04 upgrades ago. Now nothing!  Need help.

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

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

[Kernel-packages] [Bug 1722838] Re: No sound and Microsd Card reader not working on Asus e200ha

[Steven6817]

Kernel-Bug-Exists-Upstream

Sound card is recognized but still no sound, sdcard reader recognizes
only smaller sd cards but doesn't work on 64 GB sandisk 64 card

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

Title:
  No sound and Microsd Card reader not working on Asus e200ha

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed both Ubuntu 17.04 and 16.04 and neither sound or MicroSD card 
reader are working.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/2400/fd/17: Stale file handle
   Cannot stat file /proc/2400/fd/18: Stale file handle
   Cannot stat file /proc/2529/fd/11: Stale file handle
   Cannot stat file /proc/2529/fd/12: Stale file handle
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 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 0781:5406 SanDisk Corp. Cruzer Micro U3
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.303:bd12/21/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/2400/fd/17: Stale file handle
   Cannot stat file /proc/2400/fd/18: Stale file handle
   Cannot stat file /proc/2529/fd/11: Stale file handle
   Cannot stat file /proc/2529/fd/12: Stale file handle
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 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 0781:5406 SanDisk Corp. Cruzer Micro U3
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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: 

[Kernel-packages] [Bug 1722838] Re: No sound and Microsd Card reader not working on Asus e200ha

[Steven6817]

kernel 4.14-rc4 installed sorry forgot to add to last post

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

Title:
  No sound and Microsd Card reader not working on Asus e200ha

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed both Ubuntu 17.04 and 16.04 and neither sound or MicroSD card 
reader are working.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/2400/fd/17: Stale file handle
   Cannot stat file /proc/2400/fd/18: Stale file handle
   Cannot stat file /proc/2529/fd/11: Stale file handle
   Cannot stat file /proc/2529/fd/12: Stale file handle
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 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 0781:5406 SanDisk Corp. Cruzer Micro U3
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.303:bd12/21/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/2400/fd/17: Stale file handle
   Cannot stat file /proc/2400/fd/18: Stale file handle
   Cannot stat file /proc/2529/fd/11: Stale file handle
   Cannot stat file /proc/2529/fd/12: Stale file handle
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu 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 0781:5406 SanDisk Corp. Cruzer Micro U3
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  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
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.303:bd12/21/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: 

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1723112

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

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

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

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

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

Title:
  Stpped printer.  Ubuntu 16.04  upgrade 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed an new hp 8710 office jet on 10/5/2017 and downloaded
  third party hp drivers from 123.hp.com.  Every thing worked just fine.
  I unfortunately upgraded 16.04 to stay current and my printer quit
  printing with a status of stopped - missing cups filter.  I've
  unplugged, rebooted, deleted printer, tried to re-download printer
  drivers - nothing works.  The only printer settings status is printer
  is not configured.

  I think this is also related to: Sorry Ubuntu 16.04 has experienced
  internal errors, that keeps appearing. HP filters have been deleted
  out of /usr/lib/cups due to an 16.04 upgrade. Now third partly
  printer drivers can't be downloaded and installed. Need help!

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

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

[Kernel-packages] [Bug 1723112] [NEW] Stpped printer. Ubuntu 16.04 upgrade 2

[Paul Garff]

Public bug reported:

I installed an new hp 8710 office jet on 10/5/2017 and downloaded third
party hp drivers from 123.hp.com.  Every thing worked just fine.  I
unfortunately upgraded 16.04 to stay current and my printer quit
printing with a status of stopped - missing cups filter.  I've
unplugged, rebooted, deleted printer, tried to re-download printer
drivers - nothing works.  The only printer settings status is printer is
not configured.

I think this is also related to: Sorry Ubuntu 16.04 has experienced
internal errors, that keeps appearing. HP filters have been deleted out
of /usr/lib/cups due to an 16.04 upgrade. Now third partly printer
drivers can't be downloaded and installed. Need help!

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


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

Title:
  Stpped printer.  Ubuntu 16.04  upgrade 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed an new hp 8710 office jet on 10/5/2017 and downloaded
  third party hp drivers from 123.hp.com.  Every thing worked just fine.
  I unfortunately upgraded 16.04 to stay current and my printer quit
  printing with a status of stopped - missing cups filter.  I've
  unplugged, rebooted, deleted printer, tried to re-download printer
  drivers - nothing works.  The only printer settings status is printer
  is not configured.

  I think this is also related to: Sorry Ubuntu 16.04 has experienced
  internal errors, that keeps appearing. HP filters have been deleted
  out of /usr/lib/cups due to an 16.04 upgrade. Now third partly
  printer drivers can't be downloaded and installed. Need help!

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

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

[Kernel-packages] [Bug 1723107] [NEW] Sorry Ubuntu 16.04 has experienced an internal Error

[Paul Garff]

Public bug reported:

/usr/lib/i386 - linux/cups-pk-helper-mechanical-package
  cups-pk-helper 0.2.5 ubuntu - problem-type crash
I think this is also related to the 16.04 stopped printer problem.  HP filters 
have been deleted out of /usr/lib/cups due to an 16.04 upgrade.  Now third 
partly printer drivers can't be downloaded and installed.  My printer worked 
fine two 16.04 upgrades ago. Now nothing!  Need help.

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

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

Title:
  Sorry Ubuntu 16.04 has experienced an internal Error

Status in linux package in Ubuntu:
  New

Bug description:
  /usr/lib/i386 - linux/cups-pk-helper-mechanical-package
cups-pk-helper 0.2.5 ubuntu - problem-type crash
  I think this is also related to the 16.04 stopped printer problem.  HP 
filters have been deleted out of /usr/lib/cups due to an 16.04 upgrade.  
Now third partly printer drivers can't be downloaded and installed.  My printer 
worked fine two 16.04 upgrades ago. Now nothing!  Need help.

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

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

[Kernel-packages] [Bug 1715368] Re: Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03 'kernel-fixed-upstream'

[Murali Krishna]

Hi Joseph,

Attached is the output of lspci -vvvnn command. This is taken on
4.13.0-041300-generic which had bnxt_en 1.7.0 driver.


** Attachment added: "attached output of lspci -vvvnn command"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715368/+attachment/4968559/+files/lspci-vvvnn_Kernel413.log

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

Title:
  Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03
  'kernel-fixed-upstream'

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

Bug description:
  Broadcom NXE controller Cumulus devices ID's are missing in 16.04.03.
  CuW B1 device IDs are missing with Ubuntu 16.04.03 inbox bnxt_en 
driver(0.1.24) 

  Below is the modinfo output of Ubuntu 16.04.03 inbox bnxt_en driver.

  root@ubuntu160403:~# modinfo bnxt_en 
  filename: 
/lib/modules/4.4.0-87-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko
 
  version: 0.1.24 
  description: Broadcom BCM573xx network driver 
  license: GPL 
  srcversion: 0110469E9118262B301CA46 
  alias: pci:v14E4d16D3sv*sd*bc*sc*i* 
  alias: pci:v14E4d16CBsv*sd*bc*sc*i* 
  alias: pci:v14E4d16D2sv*sd*bc*sc*i* 
  alias: pci:v14E4d16D1sv*sd*bc*sc*i* 
  alias: pci:v14E4d16CAsv*sd*bc*sc*i* 
  alias: pci:v14E4d16C9sv*sd*bc*sc*i* 
  depends: vxlan 
  intree: Y 
  vermagic: 4.4.0-87-generic SMP mod_unload modversions 

  OS Details: 
  root@ubuntu160403:~# cat /etc/issue 
  Ubuntu 16.04.3 LTS \n \l 

  root@ubuntu160403:~# uname -a 
  Linux ubuntu160403 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1722829] Re: Ubuntu constant reboots right after grub AMD A8 6600k A78M-E35

[mirko.guarn...@gmail.com]

The solution was to set the kernel parameter acpi=off in the grub
config.

Unfortunately I cannot access the PC anymore to try out different
kernels. Feel free to close this bug and keep the suggested workaround
here for documentation.

In case more info are needed i might get remo

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

Title:
  Ubuntu constant reboots right after grub AMD A8 6600k A78M-E35

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This might be related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1309578

  Ubuntu 16 and 17 keeps rebooting right after the grub. After 3-4 try, it 
boots fine.
  In rescue mode it boots fine.

  Currently runninng: Ubuntu 17.04 kernel 4.10.0-37-generic #41-Ubuntu
  But the problem happened also on older versions

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-37-generic 4.10.0-37.41
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ilde   1825 F pulseaudio
   /dev/snd/controlC0:  ilde   1825 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Oct 11 16:46:41 2017
  HibernationDevice: RESUME=UUID=73bb71f4-a13c-4fa7-a644-8b35f851507f
  InstallationDate: Installed on 2014-10-16 (1091 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=19e19189-f440-4da2-aa98-e92beef6300a ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-10-11 (0 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78M-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA78M-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Steve Roberts]

Re: turn off APST completely

Tricky...

So I have been running with:
BOOT_IMAGE=/vmlinuz-4.13.0-8-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0

for the last month or so with no issues

I suppose APST is about reducing power consumption, but I am not clear
how much it saves in my (desktop) case the biggest reduction in
power consumption likely comes from being able to suspend the system as
a whole, so being able to suspend/resume likely outweighs the benefit of
apst, on the other hand for someone with an always on system, or someone
that prefers to hibernate or shutdown, having apst enabled could be
beneficial...

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: 

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Kai-Heng Feng]

bplaa.yai,

Can you file a new bug?
SM/PM951 is an OEM version, which means it's already inside the laptop when you 
unbox it.
That means we can make specific workaround for the laptop/NVMe combination.

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  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-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh 

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

[Ubuntu Kernel Bot]

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

Title:
  package linux-image-extra-4.4.0-97-generic (not installed) failed to
  install/upgrade: no se pudieron copiar los datos extraídos de
  './lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko'
  a '/lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko
  .dpkg-new': fin de fichero o de flujo inesperado

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 Failed to start Load Kernel Modules

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-97-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mb3a   4246 F pulseaudio
  Date: Wed Oct 11 05:25:51 2017
  ErrorMessage: no se pudieron copiar los datos extraídos de 
'./lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko' a 
'/lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko.dpkg-new': 
fin de fichero o de flujo inesperado
  HibernationDevice: RESUME=UUID=97a84546-8ca6-45e5-bfaa-b5027517a7ed
  InstallationDate: Installed on 2017-06-16 (117 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: Intel Corporation Intel powered classmate PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=4a4d9d14-eaf4-430e-8cfd-dfa7729b2ba7 ro persistent 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.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-97-generic (not installed) failed to 
install/upgrade: no se pudieron copiar los datos extraídos de 
'./lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko' a 
'/lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko.dpkg-new': 
fin de fichero o de flujo inesperado
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2014
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: MPSNB10L.10D.0017.2014.0820.2030
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Clamshell
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrMPSNB10L.10D.0017.2014.0820.2030:bd08/20/2014:svnIntelCorporation:pnIntelpoweredclassmatePC:pvrClamshell:rvnIntelCorporation:rnIntelpoweredclassmatePC:rvrClamshell:cvnIntelCorporation:ct9:cvr0.1:
  dmi.product.name: Intel powered classmate PC
  dmi.product.version: Clamshell
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1723044] [NEW] package linux-image-extra-4.4.0-97-generic (not installed) failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/modules/4.4.0-97-generic

[David Asuaje]

Public bug reported:

Ubuntu 16.04 Failed to start Load Kernel Modules

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-97-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mb3a   4246 F pulseaudio
Date: Wed Oct 11 05:25:51 2017
ErrorMessage: no se pudieron copiar los datos extraídos de 
'./lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko' a 
'/lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko.dpkg-new': 
fin de fichero o de flujo inesperado
HibernationDevice: RESUME=UUID=97a84546-8ca6-45e5-bfaa-b5027517a7ed
InstallationDate: Installed on 2017-06-16 (117 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2)
MachineType: Intel Corporation Intel powered classmate PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=4a4d9d14-eaf4-430e-8cfd-dfa7729b2ba7 ro persistent 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.12
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-extra-4.4.0-97-generic (not installed) failed to 
install/upgrade: no se pudieron copiar los datos extraídos de 
'./lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko' a 
'/lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko.dpkg-new': 
fin de fichero o de flujo inesperado
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2014
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: MPSNB10L.10D.0017.2014.0820.2030
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Intel powered classmate PC
dmi.board.vendor: Intel Corporation
dmi.board.version: Clamshell
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrMPSNB10L.10D.0017.2014.0820.2030:bd08/20/2014:svnIntelCorporation:pnIntelpoweredclassmatePC:pvrClamshell:rvnIntelCorporation:rnIntelpoweredclassmatePC:rvrClamshell:cvnIntelCorporation:ct9:cvr0.1:
dmi.product.name: Intel powered classmate PC
dmi.product.version: Clamshell
dmi.sys.vendor: Intel Corporation

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


** Tags: apport-package i386 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/1723044

Title:
  package linux-image-extra-4.4.0-97-generic (not installed) failed to
  install/upgrade: no se pudieron copiar los datos extraídos de
  './lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko'
  a '/lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko
  .dpkg-new': fin de fichero o de flujo inesperado

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 Failed to start Load Kernel Modules

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-97-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mb3a   4246 F pulseaudio
  Date: Wed Oct 11 05:25:51 2017
  ErrorMessage: no se pudieron copiar los datos extraídos de 
'./lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko' a 
'/lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko.dpkg-new': 
fin de fichero o de flujo inesperado
  HibernationDevice: RESUME=UUID=97a84546-8ca6-45e5-bfaa-b5027517a7ed
  InstallationDate: Installed on 2017-06-16 (117 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: Intel Corporation Intel powered classmate PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=4a4d9d14-eaf4-430e-8cfd-dfa7729b2ba7 ro persistent 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.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-extra-4.4.0-97-generic (not installed) failed to 
install/upgrade: no se pudieron copiar los datos extraídos de 
'./lib/modules/4.4.0-97-generic/kernel/drivers/tty/serial/arc_uart.ko' a 

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[-]

FWIW, I'm also affected by this issue, but on a completely different
system (Razer Blade Stealth, Samsung PM951, Fedora 26 - kernel 4.13.4),
so I don't think specifically targeting Asus Prime B350m-A + Samsung 960
EVO would do it.

As the OP, I was having frequent random SSD disconnects (the issue
appeared in late August), and thought I was affected by bug 1678184.

Using nvme_core.default_ps_max_latency_us=6000 allows the system to be
stable again as long as it's awake, but still I sometimes have the issue
when the system is awoken from sleep mode.

Please let me know if providing additional infos would help.

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home 

[Kernel-packages] [Bug 1722737] Re: BUG: unable to handle kernel NULL pointer dereference at 00000004

[Charlie]

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

I won't be able to get to this before the weekend due to other
commitments.

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at 0004

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just booted up computer.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  charlie2368 F pulseaudio
  Date: Wed Oct 11 09:13:30 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location EIP: bio_uncopy_user+0xc3/0x140 SS:ESP: 0068:f4593d0c
  Failure: oops
  InstallationDate: Installed on 2017-07-28 (74 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170725.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: NOVATECH LTD PERSONAL COMPUTER
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=650586f6-4f8f-4d72-853f-15154b747716 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 0004
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: xxx-xxx
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: PERSONAL COMPUTER
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

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

[Ubuntu Kernel Bot]

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

Title:
  package linux-headers-4.13.0-15-generic 4.13.0-15.16 failed to
  install/upgrade: subprocess installed post-installation script was
  killed by signal (Killed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  `ubuntu-bug linux`

  > Problem in linux-image-4.13.0-12-generic
  > The problem cannot be reported:
  >
  > This is not an official Ubuntu package. Please remove any third party 
package and try again

  ```
  cat /proc/version_signature
  Ubuntu 4.13.0-12.13-generic 4.13.3
  ```

  This process hangs on a wait4.

  ```
  root  5998  0.0  0.0  19600  4592 pts/2S+   08:41   0:00 
/usr/bin/perl /var/lib/dpkg/info/linux-headers-4.13.0-15-generic.postinst 
configure
  sudo strace -p5998
  strace: Process 5998 attached
  wait4(5999, 
  ```

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-headers-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1797 F pulseaudio
richard2253 F pulseaudio
   /dev/snd/controlC1:  gdm1797 F pulseaudio
richard2253 F pulseaudio
  Date: Thu Oct 12 08:40:57 2017
  DpkgTerminalLog:
   Setting up linux-headers-4.13.0-15-generic (4.13.0-15.16) ...
   Examining /etc/kernel/header_postinst.d.
   run-parts: executing /etc/kernel/header_postinst.d/dkms 4.13.0-15-generic 
/boot/vmlinuz-4.13.0-15-generic
   dpkg: error processing package linux-headers-4.13.0-15-generic 
(--configure):
subprocess installed post-installation script was killed by signal (Killed)
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Killed)
  HibernationDevice: RESUME=UUID=caa58ce2-ce7c-4f7e-b884-97361ab085fc
  MachineType: Notebook P65xRP
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=e4d59a1f-d0d7-4072-ad5c-013a79cfc6e1 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.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu6
  SourcePackage: linux
  Title: package linux-headers-4.13.0-15-generic 4.13.0-15.16 failed to 
install/upgrade: subprocess installed post-installation script was killed by 
signal (Killed)
  UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago)
  dmi.bios.date: 10/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65xRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd10/05/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65xRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

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

[Ubuntu Kernel Bot]

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

Title:
  Copying data from SATA SSD to NVMe SSD causes kernel bug

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to move my Ubuntu Server installation to a new NVMe SSD
  (Samsung EVO 960 500GB) using dd:

  sudo dd if=/dev/sda3 of=/dev/nvme0n1p3 bs=1M conv=fsync
  status=progress

  The first two partitions, EFI System and the Linux root fs, copy fine
  but copying the third partition causes the dd command to hang after a
  few seconds. If I kill the dd command the whole system freezes.

  Running Ubuntu Desktop 17.4 live image on a USB-connected SD-card

  My SATA SSD is partitioned as follows:

  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: gpt
  Disk identifier: 75902613-8162-4C99-A7CF-1642374BEDBB

  DeviceStart   End   Sectors  Size Type
  /dev/sda1  2048   1050623   1048576  512M EFI System
  /dev/sda2   1050624  59643903  58593280   28G Linux filesystem
  /dev/sda3  59643904 250068991 190425088 90.8G Linux LVM

  dmesg output:

  [  140.327890] [ cut here ]
  [  140.327914] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/drivers/nvme/host/pci.c:566!
  [  140.327940] invalid opcode:  [#1] SMP
  [  140.327953] Modules linked in: bnep snd_hda_codec_hdmi intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass 
snd_hda_codec crct10dif_pclmul crc32_pclmul snd_hda_core snd_hwdep 
ghash_clmulni_intel snd_pcm pcbc aesni_intel snd_seq_midi snd_seq_midi_event 
aes_x86_64 snd_rawmidi crypto_simd glue_helper cryptd intel_cstate snd_seq 
intel_rapl_perf snd_seq_device input_leds joydev snd_timer serio_raw snd 
hci_uart soundcore btbcm btqca btintel bluetooth mei_me mei intel_lpss_acpi 
intel_lpss mac_hid acpi_pad shpchp intel_pch_thermal parport_pc ppdev lp 
parport ip_tables x_tables autofs4 aufs nls_utf8 isofs btrfs xor raid6_pq 
nls_iso8859_1 dm_mirror dm_region_hash dm_log uas usb_storage hid_generic 
usbhid i915 i2c_algo_bit
  [  140.328186]  drm_kms_helper syscopyarea e1000e psmouse ptp pps_core nvme 
sysfillrect sysimgblt nvme_core fb_sys_fops ahci drm libahci wmi i2c_hid 
pinctrl_sunrisepoint video pinctrl_intel hid fjes
  [  140.328243] CPU: 1 PID: 170 Comm: kworker/u4:3 Not tainted 
4.10.0-19-generic #21-Ubuntu
  [  140.328267] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.22.0 for D3417-B1x07/26/2017
  [  140.328302] Workqueue: writeback wb_workfn (flush-259:0)
  [  140.328320] task: 8a80a84eab00 task.stack: 968380aac000
  [  140.328341] RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme]
  [  140.328358] RSP: 0018:968380aaf670 EFLAGS: 00010286
  [  140.328375] RAX: 0078 RBX: f200 RCX: 
1000
  [  140.328397] RDX: 0010 RSI: 0200 RDI: 
0246
  [  140.328418] RBP: 968380aaf748 R08: 8a80a1d66000 R09: 
f200
  [  140.328440] R10: 1000 R11: 8a7fbcdf R12: 
a4dfa000
  [  140.328461] R13: 0002f400 R14: 8a80a1d66000 R15: 
0200
  [  140.328483] FS:  () GS:8a80ae50() 
knlGS:
  [  140.328508] CS:  0010 DS:  ES:  CR0: 80050033
  [  140.328526] CR2: 7f0422b5f2b5 CR3: 4ba09000 CR4: 
002406e0
  [  140.328547] Call Trace:
  [  140.328560]  blk_mq_try_issue_directly+0x7e/0x100
  [  140.328576]  blk_mq_make_request+0x3cf/0x4e0
  [  140.328592]  generic_make_request+0xf2/0x1d0
  [  140.328607]  submit_bio+0x73/0x150
  [  140.328619]  ? __percpu_counter_add+0x4f/0x60
  [  140.328635]  submit_bh_wbc+0x152/0x180
  [  140.328648]  __block_write_full_page+0x176/0x360
  [  140.328664]  ? I_BDEV+0x20/0x20
  [  140.328676]  ? I_BDEV+0x20/0x20
  [  140.328688]  block_write_full_page+0x13b/0x160
  [  140.328702]  blkdev_writepage+0x18/0x20
  [  140.328716]  __writepage+0x13/0x30
  [  140.328728]  write_cache_pages+0x205/0x530
  [  140.328742]  ? wb_position_ratio+0x1f0/0x1f0
  [  140.328757]  generic_writepages+0x56/0x90
  [  140.328771]  ? delayacct_end+0x56/0x60
  [  140.328784]  ? __delayacct_blkio_end+0x30/0x50
  [  140.328799]  blkdev_writepages+0x2f/0x40
  [  140.328813]  do_writepages+0x1e/0x30
  [  140.328826]  __writeback_single_inode+0x45/0x320
  [  140.328842]  ? wake_up_q+0x80/0x80
  [  140.328855]  writeback_sb_inodes+0x266/0x5f0
  [  140.328870]  __writeback_inodes_wb+0x92/0xc0
  [  140.328884]  wb_writeback+0x268/0x300
  [  140.328897]  wb_workfn+0x234/0x410
  [  140.328910]  process_one_work+0x1fc/0x4b0
  [  140.328924]  

[Kernel-packages] [Bug 1722740] Re: IP: bio_uncopy_user+0xc3/0x140

[Charlie]

I won't be able to get to this before the weekend due to other
commitments.

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

Title:
  IP: bio_uncopy_user+0xc3/0x140

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just performed daily update.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  charlie2368 F pulseaudio
  Date: Wed Oct 11 09:30:48 2017
  Failure: oops
  InstallationDate: Installed on 2017-07-28 (74 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170725.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: NOVATECH LTD PERSONAL COMPUTER
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=650586f6-4f8f-4d72-853f-15154b747716 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: IP: bio_uncopy_user+0xc3/0x140
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: xxx-xxx
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: PERSONAL COMPUTER
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

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

[Ubuntu Kernel Bot]

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

Title:
  IP: bio_uncopy_user+0xc3/0x140

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just booted up computer.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  charlie2413 F pulseaudio
  Date: Thu Oct 12 09:16:56 2017
  Failure: oops
  InstallationDate: Installed on 2017-07-28 (75 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170725.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: NOVATECH LTD PERSONAL COMPUTER
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=650586f6-4f8f-4d72-853f-15154b747716 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: IP: bio_uncopy_user+0xc3/0x140
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: xxx-xxx
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: PERSONAL COMPUTER
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

[Kernel-packages] [Bug 1723033] [NEW] IP: bio_uncopy_user+0xc3/0x140

[Charlie]

Public bug reported:

Just booted up computer.

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-15-generic 4.13.0-15.16
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic i686
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  charlie2413 F pulseaudio
Date: Thu Oct 12 09:16:56 2017
Failure: oops
InstallationDate: Installed on 2017-07-28 (75 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170725.1)
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: NOVATECH LTD PERSONAL COMPUTER
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=650586f6-4f8f-4d72-853f-15154b747716 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: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: IP: bio_uncopy_user+0xc3/0x140
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-DS2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: xxx-xxx
dmi.chassis.type: 3
dmi.chassis.vendor: NOVATECH LTD
dmi.chassis.version: V1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
dmi.product.family: AMI PLATFORM
dmi.product.name: PERSONAL COMPUTER
dmi.product.version: V1.0
dmi.sys.vendor: NOVATECH LTD

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


** Tags: apport-kerneloops artful i386 kernel-oops

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

Title:
  IP: bio_uncopy_user+0xc3/0x140

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just booted up computer.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  charlie2413 F pulseaudio
  Date: Thu Oct 12 09:16:56 2017
  Failure: oops
  InstallationDate: Installed on 2017-07-28 (75 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170725.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: NOVATECH LTD PERSONAL COMPUTER
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic 
root=UUID=650586f6-4f8f-4d72-853f-15154b747716 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: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: IP: bio_uncopy_user+0xc3/0x140
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: xxx-xxx
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: PERSONAL COMPUTER
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD

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

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

[Kernel-packages] [Bug 1723032] [NEW] Copying data from SATA SSD to NVMe SSD causes kernel bug

[Alex]

Public bug reported:

I'm trying to move my Ubuntu Server installation to a new NVMe SSD
(Samsung EVO 960 500GB) using dd:

sudo dd if=/dev/sda3 of=/dev/nvme0n1p3 bs=1M conv=fsync status=progress

The first two partitions, EFI System and the Linux root fs, copy fine
but copying the third partition causes the dd command to hang after a
few seconds. If I kill the dd command the whole system freezes.

Running Ubuntu Desktop 17.4 live image on a USB-connected SD-card

My SATA SSD is partitioned as follows:

Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 75902613-8162-4C99-A7CF-1642374BEDBB

DeviceStart   End   Sectors  Size Type
/dev/sda1  2048   1050623   1048576  512M EFI System
/dev/sda2   1050624  59643903  58593280   28G Linux filesystem
/dev/sda3  59643904 250068991 190425088 90.8G Linux LVM

dmesg output:

[  140.327890] [ cut here ]
[  140.327914] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/drivers/nvme/host/pci.c:566!
[  140.327940] invalid opcode:  [#1] SMP
[  140.327953] Modules linked in: bnep snd_hda_codec_hdmi intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel irqbypass 
snd_hda_codec crct10dif_pclmul crc32_pclmul snd_hda_core snd_hwdep 
ghash_clmulni_intel snd_pcm pcbc aesni_intel snd_seq_midi snd_seq_midi_event 
aes_x86_64 snd_rawmidi crypto_simd glue_helper cryptd intel_cstate snd_seq 
intel_rapl_perf snd_seq_device input_leds joydev snd_timer serio_raw snd 
hci_uart soundcore btbcm btqca btintel bluetooth mei_me mei intel_lpss_acpi 
intel_lpss mac_hid acpi_pad shpchp intel_pch_thermal parport_pc ppdev lp 
parport ip_tables x_tables autofs4 aufs nls_utf8 isofs btrfs xor raid6_pq 
nls_iso8859_1 dm_mirror dm_region_hash dm_log uas usb_storage hid_generic 
usbhid i915 i2c_algo_bit
[  140.328186]  drm_kms_helper syscopyarea e1000e psmouse ptp pps_core nvme 
sysfillrect sysimgblt nvme_core fb_sys_fops ahci drm libahci wmi i2c_hid 
pinctrl_sunrisepoint video pinctrl_intel hid fjes
[  140.328243] CPU: 1 PID: 170 Comm: kworker/u4:3 Not tainted 4.10.0-19-generic 
#21-Ubuntu
[  140.328267] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.22.0 
for D3417-B1x07/26/2017
[  140.328302] Workqueue: writeback wb_workfn (flush-259:0)
[  140.328320] task: 8a80a84eab00 task.stack: 968380aac000
[  140.328341] RIP: 0010:nvme_queue_rq+0x746/0x8e0 [nvme]
[  140.328358] RSP: 0018:968380aaf670 EFLAGS: 00010286
[  140.328375] RAX: 0078 RBX: f200 RCX: 1000
[  140.328397] RDX: 0010 RSI: 0200 RDI: 0246
[  140.328418] RBP: 968380aaf748 R08: 8a80a1d66000 R09: f200
[  140.328440] R10: 1000 R11: 8a7fbcdf R12: a4dfa000
[  140.328461] R13: 0002f400 R14: 8a80a1d66000 R15: 0200
[  140.328483] FS:  () GS:8a80ae50() 
knlGS:
[  140.328508] CS:  0010 DS:  ES:  CR0: 80050033
[  140.328526] CR2: 7f0422b5f2b5 CR3: 4ba09000 CR4: 002406e0
[  140.328547] Call Trace:
[  140.328560]  blk_mq_try_issue_directly+0x7e/0x100
[  140.328576]  blk_mq_make_request+0x3cf/0x4e0
[  140.328592]  generic_make_request+0xf2/0x1d0
[  140.328607]  submit_bio+0x73/0x150
[  140.328619]  ? __percpu_counter_add+0x4f/0x60
[  140.328635]  submit_bh_wbc+0x152/0x180
[  140.328648]  __block_write_full_page+0x176/0x360
[  140.328664]  ? I_BDEV+0x20/0x20
[  140.328676]  ? I_BDEV+0x20/0x20
[  140.328688]  block_write_full_page+0x13b/0x160
[  140.328702]  blkdev_writepage+0x18/0x20
[  140.328716]  __writepage+0x13/0x30
[  140.328728]  write_cache_pages+0x205/0x530
[  140.328742]  ? wb_position_ratio+0x1f0/0x1f0
[  140.328757]  generic_writepages+0x56/0x90
[  140.328771]  ? delayacct_end+0x56/0x60
[  140.328784]  ? __delayacct_blkio_end+0x30/0x50
[  140.328799]  blkdev_writepages+0x2f/0x40
[  140.328813]  do_writepages+0x1e/0x30
[  140.328826]  __writeback_single_inode+0x45/0x320
[  140.328842]  ? wake_up_q+0x80/0x80
[  140.328855]  writeback_sb_inodes+0x266/0x5f0
[  140.328870]  __writeback_inodes_wb+0x92/0xc0
[  140.328884]  wb_writeback+0x268/0x300
[  140.328897]  wb_workfn+0x234/0x410
[  140.328910]  process_one_work+0x1fc/0x4b0
[  140.328924]  worker_thread+0x4b/0x500
[  140.328938]  kthread+0x101/0x140
[  140.328949]  ? process_one_work+0x4b0/0x4b0
[  140.328964]  ? kthread_create_on_node+0x60/0x60
[  140.328980]  ret_from_fork+0x2c/0x40
[  140.328992] Code: 51 63 8b ec 8b 95 48 ff ff ff 48 89 85 60 ff ff ff 4c 8b 
50 10 44 8b 48 18 8b 8d 50 ff ff ff 44 8b 9d 58 ff ff ff e9 dc fc ff ff <0f> 0b 
49 8b 76 68 48 8b 7d 80 e8 1b 07 8a ec 83 e8 01 74 58 41 
[  140.329073] RIP: nvme_queue_rq+0x746/0x8e0 [nvme] RSP: 968380aaf670
[  140.342445] ---[ 

[Kernel-packages] [Bug 1723027] [NEW] package linux-headers-4.13.0-15-generic 4.13.0-15.16 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)

[Richard Paul]

Public bug reported:

`ubuntu-bug linux`

> Problem in linux-image-4.13.0-12-generic
> The problem cannot be reported:
>
> This is not an official Ubuntu package. Please remove any third party package 
> and try again

```
cat /proc/version_signature
Ubuntu 4.13.0-12.13-generic 4.13.3
```

This process hangs on a wait4.

```
root  5998  0.0  0.0  19600  4592 pts/2S+   08:41   0:00 /usr/bin/perl 
/var/lib/dpkg/info/linux-headers-4.13.0-15-generic.postinst configure
sudo strace -p5998
strace: Process 5998 attached
wait4(5999, 
```

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-headers-4.13.0-15-generic 4.13.0-15.16
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu2
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1797 F pulseaudio
  richard2253 F pulseaudio
 /dev/snd/controlC1:  gdm1797 F pulseaudio
  richard2253 F pulseaudio
Date: Thu Oct 12 08:40:57 2017
DpkgTerminalLog:
 Setting up linux-headers-4.13.0-15-generic (4.13.0-15.16) ...
 Examining /etc/kernel/header_postinst.d.
 run-parts: executing /etc/kernel/header_postinst.d/dkms 4.13.0-15-generic 
/boot/vmlinuz-4.13.0-15-generic
 dpkg: error processing package linux-headers-4.13.0-15-generic 
(--configure):
  subprocess installed post-installation script was killed by signal (Killed)
ErrorMessage: subprocess installed post-installation script was killed by 
signal (Killed)
HibernationDevice: RESUME=UUID=caa58ce2-ce7c-4f7e-b884-97361ab085fc
MachineType: Notebook P65xRP
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=e4d59a1f-d0d7-4072-ad5c-013a79cfc6e1 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.
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu6
SourcePackage: linux
Title: package linux-headers-4.13.0-15-generic 4.13.0-15.16 failed to 
install/upgrade: subprocess installed post-installation script was killed by 
signal (Killed)
UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago)
dmi.bios.date: 10/05/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.05
dmi.board.asset.tag: Tag 12345
dmi.board.name: P65xRP
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd10/05/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: P65xRP
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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


** Tags: amd64 apport-package artful

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1723027/+attachment/4968339/+files/lspci-vnvn.log

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

Title:
  package linux-headers-4.13.0-15-generic 4.13.0-15.16 failed to
  install/upgrade: subprocess installed post-installation script was
  killed by signal (Killed)

Status in linux package in Ubuntu:
  New

Bug description:
  `ubuntu-bug linux`

  > Problem in linux-image-4.13.0-12-generic
  > The problem cannot be reported:
  >
  > This is not an official Ubuntu package. Please remove any third party 
package and try again

  ```
  cat /proc/version_signature
  Ubuntu 4.13.0-12.13-generic 4.13.3
  ```

  This process hangs on a wait4.

  ```
  root  5998  0.0  0.0  19600  4592 pts/2S+   08:41   0:00 
/usr/bin/perl /var/lib/dpkg/info/linux-headers-4.13.0-15-generic.postinst 
configure
  sudo strace -p5998
  strace: Process 5998 attached
  wait4(5999, 
  ```

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-headers-4.13.0-15-generic 4.13.0-15.16
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1797 F pulseaudio
richard2253 F pulseaudio
   /dev/snd/controlC1:  gdm1797 F pulseaudio
richard2253 F pulseaudio
  Date: 

[Kernel-packages] [Bug 1721352] Re: fanatic: nc_receive might return too slow

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-fan - 0.12.6

---
ubuntu-fan (0.12.6) artful; urgency=medium

  * fanatic: Add short success delay to nc_send (LP: #1721352)
  * fanatic: Catch test preparation steps failing (LP: #1718548)
  * fanatic: Add DNS checks to local-test preparation (LP: #1718548)

ubuntu-fan (0.12.5) artful; urgency=medium

  * DEP8: Fix LXD default interface detection (LP: #1718548)
  * fanctl: return error on fail_up (LP: #1719644)

 -- Stefan Bader   Fri, 06 Oct 2017 12:15:38
+0200

** Changed in: ubuntu-fan (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  fanatic: nc_receive might return too slow

Status in ubuntu-fan package in Ubuntu:
  Fix Released

Bug description:
  SRU justification:

  Impact: When running the test-local-(lxd|docker) tests, the long data
  test is sending two pieces of data. In some rare cases it was observed
  that the second send was succeeding while the receive side was not
  completely closed down after getting the first part. This broke the
  test sequence and ended in both master/slave being stuck in waiting
  for data.

  Fix: Adding a short delay after each successful send avoids this
  issue. While being on this, also fixing the direction of the repeat
  counter (was counting up instead of down).

  Testcase: running the dep8 tests for the ubuntu-fan package.

  Regression risk: low (and limited to test functionality)

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

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

[Kernel-packages] [Bug 1719644] Re: fanctl does not exit with an error when an up step fails

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-fan - 0.12.6

---
ubuntu-fan (0.12.6) artful; urgency=medium

  * fanatic: Add short success delay to nc_send (LP: #1721352)
  * fanatic: Catch test preparation steps failing (LP: #1718548)
  * fanatic: Add DNS checks to local-test preparation (LP: #1718548)

ubuntu-fan (0.12.5) artful; urgency=medium

  * DEP8: Fix LXD default interface detection (LP: #1718548)
  * fanctl: return error on fail_up (LP: #1719644)

 -- Stefan Bader   Fri, 06 Oct 2017 12:15:38
+0200

** Changed in: ubuntu-fan (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  fanctl does not exit with an error when an up step fails

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  New

Bug description:
  SRU Justification:

  Impact:
  When running cmd_up there are a few failure points which call fail_up to 
unwind but then do not exit with failure. This also has effect on running 
"fanatic enable-fan" which itself runs fanctl.

  Fix:
  Force the fail_up function to do a hard stop by adding an "exit 1" statement.

  Testcase: TBD

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

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

[Kernel-packages] [Bug 1718548] Re: ubuntu-fan autopkgtests are broken against systemd-resolved

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-fan - 0.12.6

---
ubuntu-fan (0.12.6) artful; urgency=medium

  * fanatic: Add short success delay to nc_send (LP: #1721352)
  * fanatic: Catch test preparation steps failing (LP: #1718548)
  * fanatic: Add DNS checks to local-test preparation (LP: #1718548)

ubuntu-fan (0.12.5) artful; urgency=medium

  * DEP8: Fix LXD default interface detection (LP: #1718548)
  * fanctl: return error on fail_up (LP: #1719644)

 -- Stefan Bader   Fri, 06 Oct 2017 12:15:38
+0200

** Changed in: ubuntu-fan (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  ubuntu-fan autopkgtests are broken against systemd-resolved

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  New
Status in ubuntu-fan source package in Zesty:
  New

Bug description:
  Now that 17.10 has migrated to netplan+systemd-networkd+systemd-
  resolved by default, ubuntu-fan autopkgtests are failing; at least one
  reason for this failure is wrong detection of the default network
  interface because autopkgtest environments appear for some reason to
  be getting multiple default routes:

  autopkgtest [20:14:59]: test lxd: [---
  Error: either "dev" is duplicate, or "ens2" is a garbage.
  II: Auto-init LXD...
  LXD has been successfully configured.
  II: Creating Fan Bridge...
  /usr/sbin/fanatic: .0.0/16: unknown underlay network format
  FAIL: Error on enable-fan
  autopkgtest [20:15:10]: test lxd: ---]

  
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/amd64/u/ubuntu-
  fan/20170916_203221_4f037@/log.gz)

  The other part failure appears to be a race with systemd-resolved in
  setting up the network inside of docker containers:

  autopkgtest [17:25:39]: test docker: [---
  Running in the Canonical CI environment
  II: Auto-create Fan Bridge...
  configuring fan underlay:10.220.0.0/16 overlay:250.0.0.0/8
  II: Create docker Fan Network...
  configuring docker for underlay:10.220.0.0/16 overlay:250.0.0.0/8 (fan-250 
250.4
  6.84.0/24)
  1c8a03aa50ab88b997c3b3aee88bfa6933b14368f1594db4a800c2ae8d62074f
  II: Test docker...
  local docker test: pulling container images ...
  Using default tag: latest
  latest: Pulling from library/ubuntu
  d5c6f90da05d: Pulling fs layer
  [...]
  2b8db33536d4: Pull complete
  Digest: 
sha256:2b9285d3e340ae9d4297f83fed6a9563493945935fc787e98cc32a69f5687641
  Status: Downloaded newer image for ubuntu:latest
  local docker test: creating test container ...
  5cbdd232b71bc0738f27f1fa3eae4360716bfe3f8cea976874bf6309b1843169
   slave: installing ping ...
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
  [...]
  E: Unable to locate package iputils-ping
   slave: installing nc ...
  E: Unable to locate package netcat-openbsd
  test master: ping test (250.46.84.2) ...
  test slave: ping test (250.46.84.1) ...
  test slave: ping test ... FAIL
  --- transcript start ---
  /bin/sh: 108: ping: not found
  --- transcript end ---
  test slave: short data test (250.46.84.2 -> 250.46.84.1) ...
  test master: ping test ... PASS
  test master: short data test (250.46.84.1 -> 250.46.84.2) ...
  autopkgtest [20:12:19]: ERROR: timed out on command [...]

  I've reproduced this problem locally and prepared a partial patch
  based on a similar fix to the docker.io package's autopkgtests - but
  so far this only fixes races in the lxd test, not in the docker test,
  so it needs further investigation.

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

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

[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)

[Kai-Heng Feng]

The number from iperf3 does show big difference between Windows 10 and
Linux.

Use speedtest.net to measure the speed, the gap is mainly on the upload
speed.

Ubuntu w/ Linux v4.14-rc4, latest linux-firmware.git,
cubic [1]:
Ping: 5 ms
Download: 82.29 Mbps
Upload: 59.94 Mbps

bbr [2]:
Ping: 4 ms
Download: 83.51 Mbps
Upload: 54.92 Mbps

Windows 10 [3]:
Ping: 3ms
Download: 84.08 Mbps
Upload: 76.56 Mbps

[1]: http://beta.speedtest.net/result/6699920423
[2]: http://beta.speedtest.net/result/6699960328
[3]: http://beta.speedtest.net/result/6699924242

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

Title:
  Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
  1535)

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

Bug description:
  Update (2017-05-20):
  Kalle Valo suggested a hack which increased client -> AP TCP performance - so 
it does not look like a firmware issue as I thought originally, rather an 
ath10k driver issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11
  https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom)
  Tested here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17

  Update: added some forensics in the paste (a long read):
  http://paste.ubuntu.com/24118478/

  -

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535

  Original message:
  --
  I experience a very poor 802.11ac performance of a QCA6174 Wireless card 
(Killer Wireless 1535).

  This is a dev version of Zesty with a recently released 4.10 kernel:

  uname -r
  4.10.0-9-generic

  dpkg -l linux-firmware | grep ii
  ii  linux-firmware 1.163all  Firmware for Linux kernel drivers

  lspci -vvv:

  ...
  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: ath10k_pci
  Kernel modules: ath10k_pci

  -

  Testing wireless speed with RT-87U 802.11ac router shows that the
  speed is only 27.3 megabits per second which is very low for an
  802.11ac card:

  iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  32.6 MBytes  27.3 Mbits/sec

  

  For comparison, on the same network (from the same distance to the
  router) I have the following result with an Intel's card (on a 4.8
  kernel, different laptop):

  UX32LN:~$ lspci | grep 7260
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  UX32LN:~$ iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001
  [ ID] Interval Transfer Bandwidth
  [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec
  administrator@UX32LN:~$ lsp
  lspci lspcmcia lspgpot

  200 Mbps is much better.

  ---

  Back to the problematic card:

  Booted 16.04.2 with the rolling HWE kernel 4.8:

  journalctl -k | grep -i ath
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( 
-> 0002)
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch 
firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 
debugfs 1 tracing 1 dfs 0 testmode 0
  Mar 04 

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

[NancyHsu]

The bug didn't happened on test kernel 4.1.0-3.
commit: ae827479a0a7a645ea96e68f5391fa71ad1e8c65

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

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

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

[Kernel-packages] [Bug 1722536] Re: Displays not properly recognized after upgrading kernel to 4.10.0-37-generic

[Kai-Heng Feng]

Also, please apport-collet under 4.10.0-37-generic.

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

Title:
  Displays not properly recognized after upgrading kernel to
  4.10.0-37-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a multi-monitor setup and after upgrading kernel to
  4.10.0-37-generic, the displays weren't properly recognized. Only 1
  monitor appears on display config and it's limited to 1024x768
  resolution. Reverting kernel to 4.10.0-35-generic solves the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  danilo 1261 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Oct 10 10:31:47 2017
  InstallationDate: Installed on 2017-09-25 (15 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.

   enp0s25   no wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   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 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: POSITIVO POS-PIQ57BQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=4d0acbb7-f921-4364-8c42-4a83a19fadd6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/28/2010
  dmi.bios.vendor: Desenvolvida para Positivo Informatica SA
  dmi.bios.version: 0110
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: POS-PIQ57BQ
  dmi.board.vendor: Positivo Informatica SA
  dmi.board.version: POSITIVO
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: POSITIVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidaparaPositivoInformaticaSA:bvr0110:bd12/28/2010:svnPOSITIVO:pnPOS-PIQ57BQ:pvr0110_POS:rvnPositivoInformaticaSA:rnPOS-PIQ57BQ:rvrPOSITIVO:cvnPOSITIVO:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: POS-PIQ57BQ
  dmi.product.version: 0110_POS
  dmi.sys.vendor: POSITIVO

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

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

[Kernel-packages] [Bug 1722536] Re: Displays not properly recognized after upgrading kernel to 4.10.0-37-generic

[Kai-Heng Feng]

Can you try 4.10.0-36?

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

Title:
  Displays not properly recognized after upgrading kernel to
  4.10.0-37-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a multi-monitor setup and after upgrading kernel to
  4.10.0-37-generic, the displays weren't properly recognized. Only 1
  monitor appears on display config and it's limited to 1024x768
  resolution. Reverting kernel to 4.10.0-35-generic solves the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  danilo 1261 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Oct 10 10:31:47 2017
  InstallationDate: Installed on 2017-09-25 (15 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.

   enp0s25   no wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   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 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: POSITIVO POS-PIQ57BQ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=4d0acbb7-f921-4364-8c42-4a83a19fadd6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/28/2010
  dmi.bios.vendor: Desenvolvida para Positivo Informatica SA
  dmi.bios.version: 0110
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: POS-PIQ57BQ
  dmi.board.vendor: Positivo Informatica SA
  dmi.board.version: POSITIVO
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: POSITIVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnDesenvolvidaparaPositivoInformaticaSA:bvr0110:bd12/28/2010:svnPOSITIVO:pnPOS-PIQ57BQ:pvr0110_POS:rvnPositivoInformaticaSA:rnPOS-PIQ57BQ:rvrPOSITIVO:cvnPOSITIVO:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: POS-PIQ57BQ
  dmi.product.version: 0110_POS
  dmi.sys.vendor: POSITIVO

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

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