[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[iBART]

For me, touchpad is not working at all: no movements, no clicks.

** Attachment added: "dmesg_kai_heng_feng_kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244/+attachment/5009906/+files/dmesg_kai_heng_feng_kernel

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

-- 
Mailing list: https://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 159356] Re: System freeze on high memory usage

[yas]

Hi SwaJime, you need to run 'sudo su' first and then the free sequence.
Echoing the value to drop_caches requiere super user permissions. HTH

2017-11-15 19:38 GMT+01:00 SwaJime <159...@bugs.launchpad.net>:

> yas, when I try that, I get "bash: /proc/sys/vm/drop_caches: Permission
> denied" on Ubuntu 16.04
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/159356
>
> Title:
>   System freeze on high memory usage
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I run a batch matlab job server here at my lab, running Dapper 6.06 (for
> the LTS). One of the users has submitted a very memory-consuming job, which
> successfully crashes the server. Upon closer inspection, the crash happens
> like this:
>   1. I run matlab with the given file (as an ordinary, unpriveleged user)
>   2. RAM usage quickly fills up
>   3. Once the RAM meter hits 100%, the system freezes: All SSH connections
> freeze up, and while switching VTs directly on the machine works, no new
> processes run - so one can't log in, or do anything if he is logged in.
> (Sometimes typing doesn't work at all)
>
>   Note that the swap - while 7 gigs of it are available - is never used.
>   (The machine has 7 gigs of RAM as well)
>
>   I've tried the same on my Gutsy 32-bit box, and there was no system
>   freezeup - matlab simply notified that the system was out of memory.
>   However, it did this once memory was 100% in use - and still, swap
>   didn't get used at all! (Though it is mounted correctly and shows up
>   in "top" and "free").
>
>   So first thing's first - I'd like to eliminate the crash issue. I
>   suppose I could switch the server to 32-bit, but I think that would be
>   a performance loss, considering that it does a lot of heavy
>   computation. There is no reason, however, that this should happen on a
>   64-bit machine anyway. Why does it?
>
>   WORKAROUND: Enabling DMA in the BIOS
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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/159356

Title:
  System freeze on high memory usage

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gigs of it are available - is never used.
  (The machine has 7 gigs of RAM as well)

  I've tried the same on my Gutsy 32-bit box, and there was no system
  freezeup - matlab simply notified that the system was out of memory.
  However, it did this once memory was 100% in use - and still, swap
  didn't get used at all! (Though it is mounted correctly and shows up
  in "top" and "free").

  So first thing's first - I'd like to eliminate the crash issue. I
  suppose I could switch the server to 32-bit, but I think that would be
  a performance loss, considering that it does a lot of heavy
  computation. There is no reason, however, that this should happen on a
  64-bit machine anyway. Why does it?

  WORKAROUND: Enabling DMA in the BIOS

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

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

[Kernel-packages] [Bug 1542743] Re: Bluetooth: Patch file not found ar3k/AthrBT_0x00000200.dfu

[jean-marc]

The latest patch does work when you realize that the skb_put function
has recently changed from (unsigned char*) to (void *) ( see
https://patchwork.ozlabs.org/patch/776580/ for fix).

The lines where appears "*skb_put" need to be changed to "*(u8
*)skb_put". This was enough for me to get my bluetooth adapter to work
(MSI GS60 6QC). This may not be the best way but I am not a competent
programmer

Thanks for the package !

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

Title:
  Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Since some Versions of Linux Kernel and Ubuntu Releases this problem
  exists.

  I am now running ubuntu 16.04 prerelease and still have the same
  problem.

  Bluetooth does not work with the atheros device on  msi gt 72 2qd
  notebook.

  WORKAROUND FOR [0CF3:3004] DEVICE ONLY with kernel 4.4:

  sudo apt install dkms
  wget 
https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542743-dkms_0.1_all.deb
  sudo dpkg -i btusb-lp1542743-dkms_0.1_all.deb

  FOR KERNEL 4.8 A WORKAROUND DKMS DEB IS

  https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files
  /btusb-lp1542743-dkms_0.2~4.8_all.deb

  dmesg | grep Bluetooth:
  [2.655360] Bluetooth: Core ver 2.21
  [2.655373] Bluetooth: HCI device and connection manager initialized
  [2.655377] Bluetooth: HCI socket layer initialized
  [2.655379] Bluetooth: L2CAP socket layer initialized
  [2.655385] Bluetooth: SCO socket layer initialized
  [6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.612794] Bluetooth: BNEP filters: protocol multicast
  [6.612798] Bluetooth: BNEP socket layer initialized
  [9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
  [9.016882] Bluetooth: Loading patch file failed

  hwinfo | grep Bluetooth:
  <6>[6.612790] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    <6>[6.612794] Bluetooth: BNEP filters: protocol multicast
    <6>[6.612798] Bluetooth: BNEP socket layer initialized
    <3>[9.016880] Bluetooth: Patch file not found ar3k/AthrBT_0x0200.dfu
    <3>[9.016882] Bluetooth: Loading patch file failed
  60: USB 00.0: 11500 Bluetooth Device
    Model: "Atheros AR3012 Bluetooth 4.0"
    Device: usb 0x3004 "AR3012 Bluetooth 4.0"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.36-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  7 00:38:04 2016
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2015-10-24 (105 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. GT72 2QD
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=f7880b23-39b5-423a-bdbf-62b111783450 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-02-02 (4 days ago)
  dmi.bios.date: 12/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10I
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10I:bd12/19/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QD:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QD
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:

  rfkill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

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

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

[Kernel-packages] [Bug 1724796] Re: Picture is heavily malformed

[Dario]

How would that help?
Card is working properly with OS drivers when they are loaded by Xorg DM or 
Xorg DE. Problem is only present during boot or if drivers are not loaded via 
Xorg (e.g. DM and DE are Wayland), and after Xorg loads drivers then Wayland 
also functions properly.

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

Title:
  Picture is heavily malformed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On boot screen with disk decrypt password and gdm are heavily deformed
  (check attachment). After login wayland session is also deformed, then
  if I logout and login to Xorg, picture is fine. After that if I logout
  and login back to Wayland session picture is also fine.

  GDM -> https://imgur.com/a/MhHbd
  Disk decrypt -> https://imgur.com/a/UP0rL

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 12:29:31 2017
  DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] 
[1682:c580]
  InstallationDate: Installed on 2017-08-25 (54 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Kai-Heng Feng]

So does the kernel in comment #35 work or not?

If not, does increase the msleep() value work for you guys?

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1730864] Re: Shutdown crashing when connected to AC adapter

[Kai-Heng Feng]

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu

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

Title:
  Shutdown crashing when connected to AC adapter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello there,

  I'm using Ubuntu 17.10 (fully updated) and my system is crashing at
  shutdown when connected to an AC adapter.

  The error is:

  Nov  6 22:16:49 rene-Inspiron-5447 kernel: [  248.294280] [drm:atom_op_jump 
[amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting
  Nov  6 22:16:49 rene-Inspiron-5447 kernel: [  248.294336] 
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck 
executing 75A8 (len 272, WS 0, PS 4) @ 0x75F1
  Nov  6 22:16:49 rene-Inspiron-5447 kernel: [  248.294384] 
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck 
executing 640C (len 68, WS 0, PS 8) @ 0x6430]

  This behavior is only happening when my laptop is charging. When
  running on battery I got a clean shutdown/reboot.

  Already tried to run the latest kernel package (from Mainline) and the
  problem is exactly the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rene   1249 F pulseaudio
   /dev/snd/controlC0:  rene   1249 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Nov  8 01:00:51 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0f3b9237-1086-430d-be15-043b9ca00fd2
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. Inspiron 5447
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1237aa76-9a2f-4a06-8552-526f124914ff ro quiet splash 
acpi_backlight=intel_backlight
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0MHP6R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5447:pvrA10:rvnDellInc.:rn0MHP6R:rvrA00:cvnDellInc.:ct8:cvrA10:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5447
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1726061] Re: Inspiron 5565 suspend issues after 17.10 upgrade

[Kai-Heng Feng]

I think it's not a userspace issue. A solution/workaround should come
from kernel or BIOS/EC.

First thing first, let's confirm all sources in "wakeup" are not culprit
here.

# echo EHC1 > /proc/acpi/wakeup
# echo XHC0 > /proc/acpi/wakeup
# systemctl suspend
... and see if this issue continues to happen.

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

Title:
  Inspiron 5565 suspend issues after 17.10 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Inspiron 5565, 17.10 seems to work fairly well, unless I try to
  suspend. Suspend shuts off the display but doesn't seem to actually
  shut off the CPU -- fans still run. When I move the mouse the display
  comes back on but upon entering my password sometimes the session
  crashes and I am dumped back to the login screen; sometimes the
  session is still there but wifi is either disabled (all wifi-related
  menu items gone) or visible (with question mark) but non-functional.
  In any case once I have suspended I cannot shut down or reboot any way
  other than the hard way, by holding the power button for several
  seconds. Doesn't seem to matter whether I am using X or Wayland.

  Suspend works mostly fine if I choose the 4.10 kernel from GRUB...
  although I am prompted for login more times than necessary on resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron  2489 F pulseaudio
   /dev/snd/controlC1:  aaron  2489 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 12:22:13 2017
  HibernationDevice: RESUME=UUID=3cc55560-1886-446c-8d60-15136ee14d32
  InstallationDate: Installed on 2016-12-25 (301 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Inspiron 5565
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed 
root=UUID=c30eb880-24e4-41af-9203-feff0ab69c8c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 07/20/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.2
  dmi.board.name: 0RVKF9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.0.2
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.2:bd07/20/2016:svnDellInc.:pnInspiron5565:pvr1.0.2:rvnDellInc.:rn0RVKF9:rvrA00:cvnDellInc.:ct10:cvr1.0.2:
  dmi.product.name: Inspiron 5565
  dmi.product.version: 1.0.2
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1724796] Re: Picture is heavily malformed

[Kai-Heng Feng]

RX580 is quite new. The easiest way to make your card work is to use
AMDGPU-PRO.

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

Title:
  Picture is heavily malformed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On boot screen with disk decrypt password and gdm are heavily deformed
  (check attachment). After login wayland session is also deformed, then
  if I logout and login to Xorg, picture is fine. After that if I logout
  and login back to Wayland session picture is also fine.

  GDM -> https://imgur.com/a/MhHbd
  Disk decrypt -> https://imgur.com/a/UP0rL

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 12:29:31 2017
  DistUpgraded: 2017-10-19 11:49:45,543 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Ellesmere [Radeon RX 470/480/570/580] 
[1682:c580]
  InstallationDate: Installed on 2017-08-25 (54 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=UUID=23900d78-4c59-4f7b-a317-4dd19bd68a7e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.2.2-0~z~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.2-0~z~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1730069] Re: kernel 4.10 fails to boot on AMD E-350D APU

[Kai-Heng Feng]

Huge thanks!
 
Please file an upstream bug at https://bugzilla.kernel.org/
Product: EFI
Component: Boot

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

Title:
  kernel 4.10 fails to boot on AMD E-350D APU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8
  motherboard). This has always worked fine until the kernel was
  upgraded to 4.10 as part of the regular system upgrades. Since then
  the machine wont boot, there are no errors, the screen just stays
  blank. If I boot using a previous kernel (such as 4.8.0-58-generic)
  then it all works fine.

  As of the 7th of Nov 2017, all the linux kernels above 4.8 that I have
  tried have failed, currently this includes:

  linux-image-4.10.0-30-generic
  linux-image-4.10.0-32-generic
  linux-image-4.10.0-33-generic
  linux-image-4.10.0-38-generic
  linux-image-4.13.0-16-generic

  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pim1369 F pulseaudio
   /dev/snd/controlC0:  pim1369 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=46570214-98e0-4bad-9e3c-51fd31c04b18
  InstallationDate: Installed on 2017-03-11 (238 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=screen
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed 
root=UUID=25808329-ef64-4a67-960f-6140c5610dd4 ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.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.8.0-58-generic N/A
   linux-backports-modules-4.8.0-58-generic  N/A
   linux-firmware1.157.13
  RfKill:

  Tags:  xenial
  Uname: Linux 4.8.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 01/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: E350N WIN8
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnE350NWIN8:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1732034] Re: Microphone headset isn't detected with Intel Skull Canyon NUC

[Kai-Heng Feng]

- Download the deb files in the URL
- Install them via `dpkg -i *.deb`
- Reboot into the newly installed kernel.

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

Title:
  Microphone headset isn't detected with Intel Skull Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've also tested this machine with two separate USB Microphone
  adapters, and they do the same thing really. Super-low volume on the
  mic. I can only see a bit of a spike if I tap the mic hard.

  I can confirm the Headset/Microphone selection screen pops up when
  plugging the headset in.

  This workaround works after a reboot:

  https://communities.intel.com/thread/108361

  > # Add to /etc/modprobe.d/alsa-base.conf
  > options snd-hda-intel model=dell-headset-multi

  I'm using this headset https://www.amazon.co.uk/HyperX-Stinger-Gaming-
  Headset-
  
Mobile/dp/B01LRX2DSA/ref=sr_1_2?ie=UTF8&qid=1510612581&sr=8-2&ppw=fresh&keywords=hyperx+gaming+headphones

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrewvos   1395 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 22:30:33 2017
  InstallationDate: Installed on 2017-11-10 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b7992a74-c44e-44cc-be68-f658972e448f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0050.2017.0831.1924
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0050.2017.0831.1924:bd08/31/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Kernel-packages] [Bug 1729051] Re: dkms mkdeb fails: Can't find package

[martin]

Yes, that file is the same. What's different is
https://github.com/dell/dkms/blob/master/dkms. The dkms script that's
distributed with Debian/Ubuntu looks for DEBIAN_BUILD_ARCH in the
control file.

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

Title:
  dkms mkdeb fails: Can't find package

Status in dkms package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  For some reason, the Debian version of dkms mkdeb tries to generate a
  .deb package with the current arch as a suffix in its name, instead of
  'all'. However, since the control file wasn't properly set up, the
  .deb file will have the 'all' suffix and dkms mkdeb will fail.

  This bug is also present in Ubuntu. I added a patch to the original
  Debian bug report, here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558

  but since the original bug report was made about a year ago and nobody
  cared, I'm hoping that someone will at least fix this for Ubuntu.

  The patch looks like this:

  --- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:40:41.690069116 -0300
  +++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:41:12.137973994 -0300
  @@ -6,6 +6,6 @@
   Standards-Version: 3.8.1

   Package: DEBIAN_PACKAGE-dkms
  -Architecture: all
  +Architecture: DEBIAN_BUILD_ARCH
   Depends: dkms (>= 1.95), ${misc:Depends}
   Description: DEBIAN_PACKAGE driver in DKMS format.

  I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.

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

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

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

[PJSingh5000]

If I implement the work-around in comment #17 and use kernel 4.13.12, my
bluetooth mouse connects automatically when I reboot.

Unfortunately, the work-around seems to still be required for kernel
4.13.12.

Let me know if there is anything else I can do to 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/1729389

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1732568] 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/1732568

Title:
  [ASUSTeK Computer Inc. N55SF] hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  asdfasdf

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   furkan16312 F...m pulseaudio
   /dev/snd/controlC0:  gdm1166 F pulseaudio
furkan16312 F pulseaudio
  Date: Tue Nov 14 15:40:53 2017
  DuplicateSignature: hibernate/resume:ASUSTeK Computer Inc. N55SF:N55SF.207
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=2342e5a4-757e-4272-8f09-83da2f709745
  InstallationDate: Installed on 2017-11-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterpreterPath: /usr/bin/python3.6
  MachineType: ASUSTeK Computer Inc. N55SF
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=62e32f5e-91c0-4dba-b66e-ad6145724175 ro 
resume=UUID=2342e5a4-757e-4272-8f09-83da2f709745 quiet splash
  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-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  Title: [ASUSTeK Computer Inc. N55SF] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/29/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N55SF.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N55SF
  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.:bvrN55SF.207:bd08/29/2011:svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N55SF
  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/1732568/+subscriptions

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

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

[PJSingh5000]

Hummm... doesn't look good...

Before installing 4.13.12, I reverted the change in comment #17.

$ uname -r
4.13.12-041312-generic


I see these errors in the logs:

bluetoothhd : Failed to add UUID: Not Powered (0x0f)

...and...

Bluetooth: hci0 command 0x0c52 tx timeout


Also, bluetooth is turned off in the gnome-shell topbar. If I try to open go to 
Blue Tooth settings from the gnome shell top bar, I get an error that system 
settings can not be opened; I have an option to Force Quit or Wait.  Wait 
doesn't produce results.

$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

Going into directly system settings first, and then selecting Bluetooth
from the left panel shows that Bluetooth is turned off.  If I activate
it, nothing shows up in the list of devices.  If I navigate away from
this in System Settings, and return, again Bluetooth shows as
deactivated, but rfkill list does show that it is no longer soft
blocked.

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

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

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

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

[Kernel-packages] [Bug 1732568] Re: [ASUSTeK Computer Inc. N55SF] hibernate/resume failure

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  [ASUSTeK Computer Inc. N55SF] hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  asdfasdf

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   furkan16312 F...m pulseaudio
   /dev/snd/controlC0:  gdm1166 F pulseaudio
furkan16312 F pulseaudio
  Date: Tue Nov 14 15:40:53 2017
  DuplicateSignature: hibernate/resume:ASUSTeK Computer Inc. N55SF:N55SF.207
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=2342e5a4-757e-4272-8f09-83da2f709745
  InstallationDate: Installed on 2017-11-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterpreterPath: /usr/bin/python3.6
  MachineType: ASUSTeK Computer Inc. N55SF
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=62e32f5e-91c0-4dba-b66e-ad6145724175 ro 
resume=UUID=2342e5a4-757e-4272-8f09-83da2f709745 quiet splash
  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-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  Title: [ASUSTeK Computer Inc. N55SF] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/29/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N55SF.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N55SF
  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.:bvrN55SF.207:bd08/29/2011:svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N55SF
  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/1732568/+subscriptions

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

[Kernel-packages] [Bug 1732568] [NEW] [ASUSTeK Computer Inc. N55SF] hibernate/resume failure

[Furkan keskin]

Public bug reported:

asdfasdf

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   furkan16312 F...m pulseaudio
 /dev/snd/controlC0:  gdm1166 F pulseaudio
  furkan16312 F pulseaudio
Date: Tue Nov 14 15:40:53 2017
DuplicateSignature: hibernate/resume:ASUSTeK Computer Inc. N55SF:N55SF.207
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
HibernationDevice: RESUME=UUID=2342e5a4-757e-4272-8f09-83da2f709745
InstallationDate: Installed on 2017-11-07 (8 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InterpreterPath: /usr/bin/python3.6
MachineType: ASUSTeK Computer Inc. N55SF
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcFB:
 0 nouveaufb
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=62e32f5e-91c0-4dba-b66e-ad6145724175 ro 
resume=UUID=2342e5a4-757e-4272-8f09-83da2f709745 quiet splash
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-0ubuntu2
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic  N/A
 linux-firmware 1.169
SourcePackage: linux
Title: [ASUSTeK Computer Inc. N55SF] hibernate/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 08/29/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N55SF.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N55SF
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.:bvrN55SF.207:bd08/29/2011:svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N55SF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: amd64 apport-kerneloops artful hibernate resume

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

Title:
  [ASUSTeK Computer Inc. N55SF] hibernate/resume failure

Status in linux package in Ubuntu:
  New

Bug description:
  asdfasdf

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   furkan16312 F...m pulseaudio
   /dev/snd/controlC0:  gdm1166 F pulseaudio
furkan16312 F pulseaudio
  Date: Tue Nov 14 15:40:53 2017
  DuplicateSignature: hibernate/resume:ASUSTeK Computer Inc. N55SF:N55SF.207
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=2342e5a4-757e-4272-8f09-83da2f709745
  InstallationDate: Installed on 2017-11-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterpreterPath: /usr/bin/python3.6
  MachineType: ASUSTeK Computer Inc. N55SF
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=62e32f5e-91c0-4dba-b66e-ad6145724175 ro 
resume=UUID=2342e5a4-757e-4272-8f09-83da2f709745 quiet splash
  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-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] f

Re: [Kernel-packages] [Bug 1729051] Re: dkms mkdeb fails: Can't find package

[Brian Murray]

It looks the same to me.

https://github.com/dell/dkms/blob/master/template-dkms-
mkdeb/debian/control

On Thu, Nov 16, 2017 at 12:49:01AM -, martin wrote:
> I haven't because this is a Debian/Ubuntu-specific bug. IIRC
> Debian/Ubuntu's file is different from vanilla dkms'.
> 
> 2017-11-15 18:56 GMT-03:00 Brian Murray :
> > Have you submitted it to the upstream developers of dkms on github?  The
> > file is included there and the project can be found here:
> >
> > https://github.com/dell/dkms
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1729051
> >
> > Title:
> >   dkms mkdeb fails: Can't find package
> >
> > Status in dkms package in Ubuntu:
> >   Confirmed
> > Status in dkms package in Debian:
> >   New
> >
> > Bug description:
> >   For some reason, the Debian version of dkms mkdeb tries to generate a
> >   .deb package with the current arch as a suffix in its name, instead of
> >   'all'. However, since the control file wasn't properly set up, the
> >   .deb file will have the 'all' suffix and dkms mkdeb will fail.
> >
> >   This bug is also present in Ubuntu. I added a patch to the original
> >   Debian bug report, here:
> >
> >   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558
> >
> >   but since the original bug report was made about a year ago and nobody
> >   cared, I'm hoping that someone will at least fix this for Ubuntu.
> >
> >   The patch looks like this:
> >
> >   --- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
> > 14:40:41.690069116 -0300
> >   +++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
> > 14:41:12.137973994 -0300
> >   @@ -6,6 +6,6 @@
> >Standards-Version: 3.8.1
> >
> >Package: DEBIAN_PACKAGE-dkms
> >   -Architecture: all
> >   +Architecture: DEBIAN_BUILD_ARCH
> >Depends: dkms (>= 1.95), ${misc:Depends}
> >Description: DEBIAN_PACKAGE driver in DKMS format.
> >
> >   I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1729051/+subscriptions
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729051
> 
> Title:
>   dkms mkdeb fails: Can't find package
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1729051/+subscriptions
> 
--
Brian Murray
Ubuntu Bug Master

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

Title:
  dkms mkdeb fails: Can't find package

Status in dkms package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  For some reason, the Debian version of dkms mkdeb tries to generate a
  .deb package with the current arch as a suffix in its name, instead of
  'all'. However, since the control file wasn't properly set up, the
  .deb file will have the 'all' suffix and dkms mkdeb will fail.

  This bug is also present in Ubuntu. I added a patch to the original
  Debian bug report, here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558

  but since the original bug report was made about a year ago and nobody
  cared, I'm hoping that someone will at least fix this for Ubuntu.

  The patch looks like this:

  --- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:40:41.690069116 -0300
  +++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:41:12.137973994 -0300
  @@ -6,6 +6,6 @@
   Standards-Version: 3.8.1

   Package: DEBIAN_PACKAGE-dkms
  -Architecture: all
  +Architecture: DEBIAN_BUILD_ARCH
   Depends: dkms (>= 1.95), ${misc:Depends}
   Description: DEBIAN_PACKAGE driver in DKMS format.

  I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.

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

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

[Kernel-packages] [Bug 1731822] Re: system can't detect external microphone with the codec alc274

[Hui Wang]

** Description changed:

- Steps:
- 1. install and boot into OS
- 2. connect an external microphone to system
+ After installing the latest artful kernel (Ubuntu-4.13.0-16.19), and
+ boot up the system with this kernel, we plug a headset to the headset
+ jack, then open the gnome-sound-setting, but we can not see the headset
+ microphone in it, there is only one internal microphone in it, as a
+ result we can't record the sound with the headset microphone.
  
- Expected results: system could detect external microphone
+ This Dell machine has audio codec alc274, it needs to apply a fixup like
+ ALC269_FIXUP_DELL1_MIC_NO_PRESENCE.
  
- Actual results: system can't detect external microphone
+ After applying this fixup in the kernel driver, the headset mic can be
+ detected and works 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/1731822

Title:
  system can't detect external microphone with the codec alc274

Status in HWE Next:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After installing the latest artful kernel (Ubuntu-4.13.0-16.19), and
  boot up the system with this kernel, we plug a headset to the headset
  jack, then open the gnome-sound-setting, but we can not see the
  headset microphone in it, there is only one internal microphone in it,
  as a result we can't record the sound with the headset microphone.

  This Dell machine has audio codec alc274, it needs to apply a fixup
  like ALC269_FIXUP_DELL1_MIC_NO_PRESENCE.

  After applying this fixup in the kernel driver, the headset mic can be
  detected and works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1731822/+subscriptions

-- 
Mailing list: https://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 1729051] Re: dkms mkdeb fails: Can't find package

[martin]

I haven't because this is a Debian/Ubuntu-specific bug. IIRC
Debian/Ubuntu's file is different from vanilla dkms'.

2017-11-15 18:56 GMT-03:00 Brian Murray :
> Have you submitted it to the upstream developers of dkms on github?  The
> file is included there and the project can be found here:
>
> https://github.com/dell/dkms
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1729051
>
> Title:
>   dkms mkdeb fails: Can't find package
>
> Status in dkms package in Ubuntu:
>   Confirmed
> Status in dkms package in Debian:
>   New
>
> Bug description:
>   For some reason, the Debian version of dkms mkdeb tries to generate a
>   .deb package with the current arch as a suffix in its name, instead of
>   'all'. However, since the control file wasn't properly set up, the
>   .deb file will have the 'all' suffix and dkms mkdeb will fail.
>
>   This bug is also present in Ubuntu. I added a patch to the original
>   Debian bug report, here:
>
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558
>
>   but since the original bug report was made about a year ago and nobody
>   cared, I'm hoping that someone will at least fix this for Ubuntu.
>
>   The patch looks like this:
>
>   --- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
> 14:40:41.690069116 -0300
>   +++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
> 14:41:12.137973994 -0300
>   @@ -6,6 +6,6 @@
>Standards-Version: 3.8.1
>
>Package: DEBIAN_PACKAGE-dkms
>   -Architecture: all
>   +Architecture: DEBIAN_BUILD_ARCH
>Depends: dkms (>= 1.95), ${misc:Depends}
>Description: DEBIAN_PACKAGE driver in DKMS format.
>
>   I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1729051/+subscriptions

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

Title:
  dkms mkdeb fails: Can't find package

Status in dkms package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  For some reason, the Debian version of dkms mkdeb tries to generate a
  .deb package with the current arch as a suffix in its name, instead of
  'all'. However, since the control file wasn't properly set up, the
  .deb file will have the 'all' suffix and dkms mkdeb will fail.

  This bug is also present in Ubuntu. I added a patch to the original
  Debian bug report, here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558

  but since the original bug report was made about a year ago and nobody
  cared, I'm hoping that someone will at least fix this for Ubuntu.

  The patch looks like this:

  --- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:40:41.690069116 -0300
  +++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:41:12.137973994 -0300
  @@ -6,6 +6,6 @@
   Standards-Version: 3.8.1

   Package: DEBIAN_PACKAGE-dkms
  -Architecture: all
  +Architecture: DEBIAN_BUILD_ARCH
   Depends: dkms (>= 1.95), ${misc:Depends}
   Description: DEBIAN_PACKAGE driver in DKMS format.

  I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.

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

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

[Kernel-packages] [Bug 1732535] Re: linux-aws: 4.4.0-1041.50 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.4.0-1041.50 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
  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/1732535

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

Bug description:
  This bug is for tracking the 4.4.0-1041.50 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
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1732535] Re: linux-aws: 4.4.0-1041.50 -proposed tracker

[Brad Figg]

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

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

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

Title:
  linux-aws: 4.4.0-1041.50 -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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-1041.50 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 --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1732535] Re: linux-aws: 4.4.0-1041.50 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the 4.4.0-1041.50 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Wednesday, 15. November 2017 21:01 UTC
- 
  -- swm properties --
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Wednesday, 15. November 2017 22:30 UTC

** Description changed:

  This bug is for tracking the 4.4.0-1041.50 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 --
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 15. November 2017 22:30 UTC
+ 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/1732535

Title:
  linux-aws: 4.4.0-1041.50 -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:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  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 Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.4.0-1041.50 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 --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1729051] Re: dkms mkdeb fails: Can't find package

[Brian Murray]

Have you submitted it to the upstream developers of dkms on github?  The
file is included there and the project can be found here:

https://github.com/dell/dkms

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

Title:
  dkms mkdeb fails: Can't find package

Status in dkms package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  For some reason, the Debian version of dkms mkdeb tries to generate a
  .deb package with the current arch as a suffix in its name, instead of
  'all'. However, since the control file wasn't properly set up, the
  .deb file will have the 'all' suffix and dkms mkdeb will fail.

  This bug is also present in Ubuntu. I added a patch to the original
  Debian bug report, here:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558

  but since the original bug report was made about a year ago and nobody
  cared, I'm hoping that someone will at least fix this for Ubuntu.

  The patch looks like this:

  --- a/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:40:41.690069116 -0300
  +++ b/etc/dkms/template-dkms-mkdeb/debian/control 2017-10-31 
14:41:12.137973994 -0300
  @@ -6,6 +6,6 @@
   Standards-Version: 3.8.1

   Package: DEBIAN_PACKAGE-dkms
  -Architecture: all
  +Architecture: DEBIAN_BUILD_ARCH
   Depends: dkms (>= 1.95), ${misc:Depends}
   Description: DEBIAN_PACKAGE driver in DKMS format.

  I'm using Ubuntu 17.10. dkms version is 2.3-3ubuntu3.

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

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

[Kernel-packages] [Bug 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issue

[bugproxy]

--- Comment From gwal...@br.ibm.com 2017-11-15 16:50 EDT---
The test on Zesty worked fine with the proposed kernel 4.10.0-40-generic.

Both releases worked with aligntest for CI Vector Load and stress-ng
focused on CPU.

** Tags removed: verification-needed-zesty
** Tags added: verification-done-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/1721070

Title:
  powerpc/64s: Add workaround for P9 vector CI load issue

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  
  == SRU Justification ==
  POWER9 DD2.1 and earlier has an issue where some cache inhibited
  vector load will return bad data. The fix is two part, one
  firmware/microcode part triggers HMI interrupts when hitting such
  loads, the other part is commit 5080332c2c89 from linux-next which then
  emulates the instructions in Linux.

  The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
  lxvh8x.

  Commit ccd3cd361341 is needed as a prereq for Artful.
  Commits a3d96f70c147 and ccd3cd361341 are needed as prereqs for Zesty.

  == Fixes ==
  a3d96f70c147 ("powerpc/64s: Fix system reset vs general interrupt reentrancy")
  ccd3cd361341 ("powerpc/mce: Move 64-bit machine check code into mce.c")
  5080332c2c89 ("powerpc/64s: Add workaround for P9 vector CI load issue")

  == Regression Potential ==
  These commits are specific to powerpc.  They required some back porting but
   have been tested by IBM.


  -- Problem Description --

  When an instruction triggers the HMI, all threads in the core will be
  sent to the HMI handler, not just the one running the vector load.

  In general, these spurious HMIs are detected by the emulation code and
  we just return back to the running process. Unfortunately, if a
  spurious interrupt occurs on a vector load that's to normal memory we
  have no way to detect that it's spurious (unless we walk the page
  tables, which is very expensive). In this case we emulate the load but
  we need do so using a vector load itself to ensure 128bit atomicity is
  preserved.

  Some additional debugfs emulated instruction counters are added also.

  In order to solve this bug, we need to cherry pick the following patch

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=5080332c2c893118dbc18755f35c8b0131cf0fc4

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

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

[Kernel-packages] [Bug 1730069] Re: kernel 4.10 fails to boot on AMD E-350D APU

[Patrick Mackinlay]

I have found the broken commit, its
9479c7cebfb568f8b8b424be7f1cac120e9eea95

The git bisect process ended with:

Bisecting: 0 revisions left to test after this (roughly 0 steps)
[9479c7cebfb568f8b8b424be7f1cac120e9eea95] efi: Refactor 
efi_memmap_init_early() into arch-neutral code

That revisions kernel fails, the one before that,
ab72a27da4c6c19b0e3d6d7556fdd4afb581c8ac, works.

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

Title:
  kernel 4.10 fails to boot on AMD E-350D APU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8
  motherboard). This has always worked fine until the kernel was
  upgraded to 4.10 as part of the regular system upgrades. Since then
  the machine wont boot, there are no errors, the screen just stays
  blank. If I boot using a previous kernel (such as 4.8.0-58-generic)
  then it all works fine.

  As of the 7th of Nov 2017, all the linux kernels above 4.8 that I have
  tried have failed, currently this includes:

  linux-image-4.10.0-30-generic
  linux-image-4.10.0-32-generic
  linux-image-4.10.0-33-generic
  linux-image-4.10.0-38-generic
  linux-image-4.13.0-16-generic

  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pim1369 F pulseaudio
   /dev/snd/controlC0:  pim1369 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=46570214-98e0-4bad-9e3c-51fd31c04b18
  InstallationDate: Installed on 2017-03-11 (238 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=screen
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed 
root=UUID=25808329-ef64-4a67-960f-6140c5610dd4 ro quiet splash
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.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.8.0-58-generic N/A
   linux-backports-modules-4.8.0-58-generic  N/A
   linux-firmware1.157.13
  RfKill:

  Tags:  xenial
  Uname: Linux 4.8.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 01/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: E350N WIN8
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnE350NWIN8:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1728958] Re: linux-aws: -proposed tracker

[Kamal Mostafa]

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

** This bug is no longer a duplicate of bug 1729280
   linux-aws: 4.4.0-1040.49 -proposed tracker
** This bug has been marked a duplicate of bug 1732535
   linux-aws: 4.4.0-1041.50 -proposed tracker

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 Xenial:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1728945
  phase: Packaging

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

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

[Kernel-packages] [Bug 1729280] Re: linux-aws: 4.4.0-1040.49 -proposed tracker

[Kamal Mostafa]

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

** This bug has been marked a duplicate of bug 1732535
   linux-aws: 4.4.0-1041.50 -proposed tracker

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

Title:
  linux-aws: 4.4.0-1040.49 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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: 1731264
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[bugproxy]

--- Comment From gwal...@br.ibm.com 2017-11-15 16:44 EDT---
[SRU Justification]
This feature provides the latest core and nest PMU events which it comes with 
the skiboot on Power P9 Arch.

Those patches are available on mainline kernel tree in
tags/powerpc-4.14-1~314 .

The commit is a clean cherry pick in Artful.

[Testcase]
1 - Verify if the perf has the PMU events available via the latest version of 
skiboot.
# perf list | grep core_imc
# perf list | grep nest_
# perf list | grep thread_imc

2 - Test couple of them like that:
# ./perf stat -e nest_mcs0/PM_MCS_UP_128B_DATA_XFER_MC2/ -a -A sleep 5

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

Title:
  Power8 Nest PMU Instrumentation support

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  New

Bug description:
  This is a bug for Canonical awareness that we want to have the
  following patches included in 15.10.

  They are still under development/review:

  https://patchwork.ozlabs.org/patch/482968/
  https://patchwork.ozlabs.org/patch/482969/
  https://patchwork.ozlabs.org/patch/482970/
  https://patchwork.ozlabs.org/patch/482971/
  https://patchwork.ozlabs.org/patch/482972/
  https://patchwork.ozlabs.org/patch/482973/
  https://patchwork.ozlabs.org/patch/482974/

  Patches under review.

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

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

[Kernel-packages] [Bug 1732535] Re: linux-aws: 4.4.0-1041.50 -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the 4.4.0-1041.50 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Wednesday, 15. November 2017 21:01 UTC

** Description changed:

  This bug is for tracking the 4.4.0-1041.50 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 15. November 2017 21:01 UTC
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux-aws: 4.4.0-1041.50 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow 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 Xenial:
  Confirmed

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

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

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 15. November 2017 21:01 UTC

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1732535] [NEW] linux-aws: 4.4.0-1041.50 -proposed tracker

[Kamal Mostafa]

Public bug reported:

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

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

kernel-stable-phase:Packaging
kernel-stable-phase-changed:Wednesday, 15. November 2017 21:01 UTC

-- swm properties --
phase: Packaging

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-aws (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live xenial

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

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

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: U

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Brad]

It looks like this fix will be included in Kernel 4.15

Hans de Goede (1):
  HID: i2c-hid: Add no-irq-after-reset quirk for 0911:5288 device

https://lkml.org/lkml/2017/11/15/168
http://lkml.iu.edu/hypermail/linux/kernel/1711.1/05553.html

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1728908] Re: a300_[pfp|pm4].fw clashes when installing linux-firmware

[Seth Forshee]

What we have is scenario #9 from
https://wiki.debian.org/PackageTransition, which means linux-firmware-
snapdragon needs a "Breaks: linux-firmware (<= ...)" and linux-firmware
needs "Breaks: linux-firmware-snapdragon (<= ...) Replaces: linux-
firmware-snapdragon (<= ...)".

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

Title:
  a300_[pfp|pm4].fw clashes when installing linux-firmware

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware-snapdragon package in Ubuntu:
  In Progress
Status in linux-firmware source package in Xenial:
  In Progress
Status in linux-firmware-snapdragon source package in Xenial:
  In Progress
Status in linux-firmware source package in Artful:
  In Progress
Status in linux-firmware-snapdragon source package in Artful:
  In Progress

Bug description:
  [Impact]

  Starting with linux-firmware 1.157.13, two files (a300_[pfp|pm4].fw)
  that were previously part of linux-firmware-snapdragon 1.2-0ubuntu1,
  are now integrated in the linux-firmware package itself, resulting in
  a file clash when these two packages are installed together:

  ..
  Selecting previously unselected package linux-firmware-snapdragon.
  Preparing to unpack .../linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb ...
  Unpacking linux-firmware-snapdragon (1.2-0ubuntu1) ...
  dpkg: error processing archive
  /var/cache/apt/archives/linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb
  (--unpack):
   trying to overwrite '/lib/firmware/a300_pm4.fw', which is also in
  package linux-firmware 1.157.13
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Selecting previously unselected package linux-image-snapdragon.
  Preparing to unpack .../linux-image-snapdragon_4.4.0.1077.69_arm64.deb ...
  Unpacking linux-image-snapdragon (4.4.0.1077.69) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  make: *** [all] Error 100
  ...

  This problem is particularly evident when a new snapdragon kernel snap
  is assembled, since the the building process breaks (and no kernel
  snap is generated):

  https://launchpadlibrarian.net/343287945
  /buildlog_snap_ubuntu_xenial_arm64_snapdragon-kernel-
  test_BUILDING.txt.gz

  To fix the problem i removed the two files from linux-firmware-
  snapdragon 1.3-0ubuntu1 and pushed this new version to my ppa:

  https://launchpad.net/~p-pisati/+archive/ubuntu/embedded/+packages
  linux-firmware-snapdragon - 1.3-0ubuntu1

  [Test case]

  Try to build a snapdragon kernel snap using Xenial/updates - with
  linux-firmware 1.157.13 and linux-firmware-snapdragon 1.2-0ubuntu1 it
  won't complete, while with linux-firmware-snapdragon 1.3-0ubuntu1 it
  will successfully complete.

  [Regression risk]

  The files imported in linux-firmware are the same files we
  shipped in linux-firmware-snapdragon:

  $ md5sum /lib/firmware/qcom/a300_pfp.fw
  25aa81977303142bdc4490efad16138b  /lib/firmware/qcom/a300_pfp.fw
  $ md5sum /lib/firmware/qcom/a300_pm4.fw
  d657cacd951742d9bbbe74224347cffe  /lib/firmware/qcom/a300_pm4.fw

  $ md5sum dragon410c-firmware.orig/lib/a300_pfp.fw
  25aa81977303142bdc4490efad16138b  dragon410c-firmware.orig/lib/a300_pfp.fw
  $ md5sum dragon410c-firmware.orig/lib/a300_pm4.fw
  d657cacd951742d9bbbe74224347cffe  dragon410c-firmware.orig/lib/a300_pm4.fw

  so the regression risk is very low.

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Brad]

>From another user with the same August BIOS as mine said that the patched 
>kernel provided by @kaihengfeng fixed the problem for him:
http://people.canonical.com/~khfeng/lp1728244/
 

https://techtablets.com/forum/topic/how-to-install-antergos-linux-on-
the-ezbook-3-pro-v4/#post-74901

"It is 17.10 Ubuntu from the official download site, isorespined
(Linuxium), then kernel changed  (yesterday did it) from the link above.
Ubuntu installed few weeks ago, but had touchpad problem until kernel
change

4.13.0.17 is working (from your link above)  4.14-rc7 was not ok
(maybe patch was not included at all, god knows who compiled the
kernel)!!! Since yesterday all boot was normal, touchpad is working, no
freezing issue. Maybe sometimes this 100ms waiting time is not enough.
This waiting time includes in the patch.

After some debuging this it seems that this touchpad simply never sends
an interrupt after a reset as expected by the i2c hid driver. This commit
adds a quirk for this device, making i2c_hid_command sleep 100ms after
a reset instead of waiting for an irq, fixing i2c-hid failing to bind to
this touchpad.”

Maybe this 100ms is not enough sometimes, this was the reason, why your
touchpad not worked once. (Just a tip)"

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1732512] Re: xen hibernation support for linux-aws

[Kamal Mostafa]

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

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

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

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

** Changed in: linux-aws (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: linux-aws (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  xen hibernation support for linux-aws

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

Bug description:
  linux-aws needs multiple commits from mainline and Amazon Linux to
  support xen hibernation:

  UBUNTU: aws: [Config] disable SUSPEND
  UBUNTU: aws: [Config] disable XEN_FBDEV_FRONTEND,
  xen: move xen_setup_runstate_info and get_runstate_snapshot to
  (cherry picked from commit 4ccefbe597392d2914cf7ad904e33c734972681d)
  xen/time: use READ_ONCE
  (cherry picked from commit 2dd887e32175b624375570a0361083eb2cd64a07)
  xen: add steal_clock support on x86
  (back-ported from commit ecb23dc6f2eff0ce64dd60351a81f376f13b12cc)
  xen: support runqueue steal time on xen
  (cherry picked from commit 6ba286ad845799b135e5af73d1fbc838fa79f709)
  x86/xen: use xen_vcpu_id mapping for HYPERVISOR_vcpu_op
  (cherry picked from commit ad5475f9faf5186b7f59de2c6481ee3e211f1ed7)
  xen: add static initialization of steal_clock op to xen_time_ops
  (cherry picked from commit d34c30cc1fa80f509500ff192ea6bc7d30671061)
  x86/xen: update cpuid.h from Xen-4.7
  (cherry picked from commit de2f5537b397249e91cafcbed4de64a24818542e)
  x86/acpi: store ACPI ids from MADT for future usage
  (cherry picked from commit 3e9e57fad3d8530aa30787f861c710f598ddc4e7)
  xen: introduce xen_vcpu_id mapping
  (back-ported from commit 88e957d6e47f1232ad15b21e54a44f1147ea8c1b)
  xen: update xen headers
  (cherry picked from commit 7ba8dba95cb227eb6c270b1aa77f942e45f5e47c)
  xen: change the type of xen_vcpu_id to uint32_t
  (cherry picked from commit 55467dea2967259f21f4f854fc99d39cc5fea60e)
  xen/blkfront: separate per ring information out of device info
  (cherry picked from commit 81f351615772365d46ceeac3e50c9dd4e8f9dc89)
  xen/blkfront: pseudo support for multi hardware queues/rings
  (cherry picked from commit 3df0e5059908b8fdba351c4b5dd77caadd95a949)
  xen/blkfront: split per device io_lock
  (cherry picked from commit 11659569f7202d0cb6553e81f9b8aa04dfeb94ce)
  xen/blkfront: negotiate number of queues/rings to be used with
  (cherry picked from commit 28d949bcc28bbc2d206f9c3f69b892575e81c040)
  xen/blkfront: Cleanup of comments, fix unaligned variables, and
  (cherry picked from commit 6f03a7ff89485f0a7a559bf5c7631d2986c4ecfa)
  xen/blkfront: Remove duplicate setting of ->xbdev.
  (cherry picked from commit 75f070b3967b0c3bf0e1bc43411b06bab6c2c2cd)
  xen/blkfront: make persistent grants pool per-queue
  (cherry picked from commit 73716df7da4f60dd2d59a9302227d0394f1b8fcc)
  xen/blkfront: correct setting for xen_blkif_max_ring_order
  (cherry picked from commit 45fc82642e54018740a25444d1165901501b601b)
  xen/blkfront: realloc ring info in blkif_resume
  (cherry picked from commit 3db70a853202c252a8ebefa71ccb088ad149cdd2)
  blk-mq: dynamic h/w context count
  (back-ported from commit 868f2f0b72068a097508b6e8870a8950fd8eb7ef)
  xen-blkfront: save uncompleted reqs in blkfront_resume()
  (cherry picked from commit 7b427a59538a98161321aa46c13f4ea81b43f4eb)
  xen-blkfront: fix places not updated after introducing 64KB page
  (cherry picked from commit 6c647b0eb01cd7326dca093590f5e123e3c68b9c)
  blk-mq: mark request queue as mq asap
  (cherry picked from commit 66841672161efb9e3be4a1dbd9755020bb1d86b7)
  blk-mq: Fix NULL pointer updating nr_requests
  (cherry picked from commit e9137d4b93078b6a9965acfb18a2a2ad91cf8405)
  xen-blkfront: fix resume issues after a migration
  (cherry picked from commit 2a6f71ad99cabe436e70c3f5fcf58072cb3bc07f)
  xen-blkfront: introduce blkif_set_queue_limits()
  (back-ported from commit 172335ada40ce26806e514c83a504b45c14a4139)
  xen/pvhvm: run xen_vcpu_setup() for the boot CPU
  (cherry picked from commit ee42d665d3f5db975caf87baf101a57235ddb566)
  UBUNTU: SAUCE: [aws] xen/manage: keep track of the on-going suspend
  UBUNTU: SAUCE: [aws] xen/manage: introduce helper function to know
  UBUNTU: SAUCE: [aws] xenbus: add freeze/thaw/restore callbacks
  UBUNTU: SAUCE: [aws] x86/xen: decouple shared_info mapping from
  UBUNTU: SAUCE: [aws] x86/xen: add system core suspend and resume
  UBUNTU: SAU

[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode

[James D.]

Haha, ok ok.  Recreated it in 16.04 by applying pressure to the trackpad
with my palm.  It seems better now on both versions but I do suspect a
hw issue.  Dell is coming out to replace it under warranty.  Hoping it's
not a design flaw that impacts all touchpads ,, or maybe they have a
newer revision of trackpad because of this issue.  that'd be nice.

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

Title:
  XPS 13 9360 trackpad locks into scroll mode

Status in Dell Sputnik:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I'm running Linux on a Dell XPS 13 (9360) laptop.

  I find that upwards of 10 times per day, my trackpad gets stuck in
  "scrolling" mode. Moving the trackpad won't move the X windows
  pointer, but will send scrolling events to the foreground window.

  When the trackpad is locked in this mode, the touchscreen will still
  let me move the mouse cursor, as will an external mouse.

  On Ubuntu 16.04 freshly restored from the Dell recovery image, I find
  that it's often difficult to get the trackpad to recover.

  I do find that the issue happens less frequently on Dell's build of
  Ubuntu 16.04 than on other linux distributions and versions, but it
  still happens enough to significantly impact my ability to do
  productive work.

  The issue does not occur when running Windows 10 on the same device.

  I suspect that the issue may be related to palm detection or
  misdetecting the user's palm as a gesture to enable scrolling mode,
  but have no proof for this.

  It seems that I'm often able to reproduce the issue by brushing the
  trackpad with my right palm.

  On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx
  4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64
  x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I
  am able to get the trackpad to recover, simply by clicking the
  trackpad:

  /usr/share/X11/xorg.conf.d/99-libinput.conf:

  Section "InputClass"
  Identifier "libinput touchpad catchall"
  Driver "libinput"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Option "Tapping" "True"
  Option "DisableWhileTyping" "True"
  Option "NaturalScrolling" "False"
  Option "AccelProfile" "adaptive"
  Option "AccelSpeed" "0.05"
  Option "MiddleEmulation" "True"
  Option "ScrollMethod" "twofinger"
  # Option "ClickMethod" "clickfinger"
  Option "ClickMethod" "buttonareas"
  EndSection

  
  In my experience, the problem manifests using both the Xorg synaptics driver 
and the Xorg libinput driver.

  root@szx:/etc/modprobe.d# xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech M570   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ DLL075B:01 06CB:76AF Touchpad   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=14   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]
  root@szx:/etc/modprobe.d#

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions

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

[Kernel-packages] [Bug 1723837] Re: Mouse buttons do not work upon resume from suspend.

[Don Paradis]

Unable to post logs because the system is no longer installed. Note that
this problem only happens on Ubuntu MATE. It does not happen in standard
issue Ubuntu 17.10.

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

Title:
  Mouse buttons do not work upon resume from suspend.

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mouse buttons do not work upon resume from suspend. Ctrl-Alt-F1 and
  then Ctrl-Alt-F7 restores mouse button functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1723837/+subscriptions

-- 
Mailing list: https://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 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

[Ian Bruntlett]

Hi,

On 14 November 2017 at 07:22, Kai-Heng Feng 
wrote:

> Sorry for the late reply, please try this kernel,
>
> http://people.canonical.com/~khfeng/lp1724639-2/


No problem. These are the files I downloaded:-
total 58M
-rw-rw-r-- 1 ian ian 936K Nov 15 18:37
linux-firmware-image-4.12.0_4.12.0-4_i386.deb
-rw-rw-r-- 1 ian ian  11M Nov 15 18:37
linux-headers-4.12.0_4.12.0-4_i386.deb
-rw-rw-r-- 1 ian ian  46M Nov 15 18:37 linux-image-4.12.0_4.12.0-4_i386.deb

To work out which kernel was being installed I did:-
dpkg-deb -c linux-image-4.12.0_4.12.0-4_i386.deb

Looks like kernel '4.12' is being installed.

Booted system with kernel 4.12. The graphics problem did _not_ occur.
Did uname -a. Got:-
Linux hawking 4.12.0 #4 SMP Fri Nov 10 04:04:10 EST 2017 i686 i686 i686
GNU/Linux

IDEA. Given that setting the GRUB environment variable
GRUB_GFXPAYLOAD_LINUX to text solves the problem, could this be happening:-
* That GRUB is doing something different with its handling of graphics
* That the Kernel's graphic driver is taking advantage of some graphics
mode setting that GRUB was doing before, but now no longer does?

HTH :)


Ian

-- 
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page -
https://sites.google.com/site/ianbruntlett/home/free-software

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

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

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

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1728908] Re: a300_[pfp|pm4].fw clashes when installing linux-firmware

[Seth Forshee]

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: linux-firmware (Ubuntu Artful)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

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

** Changed in: linux-firmware-snapdragon (Ubuntu)
 Assignee: (unassigned) => Paolo Pisati (p-pisati)

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

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

** Changed in: linux-firmware-snapdragon (Ubuntu Xenial)
 Assignee: (unassigned) => Paolo Pisati (p-pisati)

** Changed in: linux-firmware-snapdragon (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: linux-firmware-snapdragon (Ubuntu Artful)
   Status: New => In Progress

** Changed in: linux-firmware-snapdragon (Ubuntu Artful)
 Assignee: (unassigned) => Paolo Pisati (p-pisati)

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

Title:
  a300_[pfp|pm4].fw clashes when installing linux-firmware

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware-snapdragon package in Ubuntu:
  In Progress
Status in linux-firmware source package in Xenial:
  In Progress
Status in linux-firmware-snapdragon source package in Xenial:
  In Progress
Status in linux-firmware source package in Artful:
  In Progress
Status in linux-firmware-snapdragon source package in Artful:
  In Progress

Bug description:
  [Impact]

  Starting with linux-firmware 1.157.13, two files (a300_[pfp|pm4].fw)
  that were previously part of linux-firmware-snapdragon 1.2-0ubuntu1,
  are now integrated in the linux-firmware package itself, resulting in
  a file clash when these two packages are installed together:

  ..
  Selecting previously unselected package linux-firmware-snapdragon.
  Preparing to unpack .../linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb ...
  Unpacking linux-firmware-snapdragon (1.2-0ubuntu1) ...
  dpkg: error processing archive
  /var/cache/apt/archives/linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb
  (--unpack):
   trying to overwrite '/lib/firmware/a300_pm4.fw', which is also in
  package linux-firmware 1.157.13
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Selecting previously unselected package linux-image-snapdragon.
  Preparing to unpack .../linux-image-snapdragon_4.4.0.1077.69_arm64.deb ...
  Unpacking linux-image-snapdragon (4.4.0.1077.69) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/linux-firmware-snapdragon_1.2-0ubuntu1_arm64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  make: *** [all] Error 100
  ...

  This problem is particularly evident when a new snapdragon kernel snap
  is assembled, since the the building process breaks (and no kernel
  snap is generated):

  https://launchpadlibrarian.net/343287945
  /buildlog_snap_ubuntu_xenial_arm64_snapdragon-kernel-
  test_BUILDING.txt.gz

  To fix the problem i removed the two files from linux-firmware-
  snapdragon 1.3-0ubuntu1 and pushed this new version to my ppa:

  https://launchpad.net/~p-pisati/+archive/ubuntu/embedded/+packages
  linux-firmware-snapdragon - 1.3-0ubuntu1

  [Test case]

  Try to build a snapdragon kernel snap using Xenial/updates - with
  linux-firmware 1.157.13 and linux-firmware-snapdragon 1.2-0ubuntu1 it
  won't complete, while with linux-firmware-snapdragon 1.3-0ubuntu1 it
  will successfully complete.

  [Regression risk]

  The files imported in linux-firmware are the same files we
  shipped in linux-firmware-snapdragon:

  $ md5sum /lib/firmware/qcom/a300_pfp.fw
  25aa81977303142bdc4490efad16138b  /lib/f

[Kernel-packages] [Bug 1726818] Re: vagrant artful64 box filesystem too small

[Yasuo Honda]

Hi, I am getting the same problem.

> Which suggests adding 'noxsave' to the kernel command line as a
workaround.

I have been looking for how to set 'noxsave' kernel boot parameter using 
Vagrant but 
unable to find it. Does anyone know how to configure it?

Thank you.

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

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After building a new vagrant instance using the ubuntu/artful64 box
  (v20171023.1.0), the size of the filesystem seems to be much too
  small. Here's the output of `df -h` on the newly built instance:

  vagrant@ubuntu-artful:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev991M 0  991M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   2.2G  2.1G   85M  97% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  182G   28G  87% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  For comparison, here is the same from the latest zesty64 box:

  ubuntu@ubuntu-zesty:~$ df -h
  Filesystem  Size  Used Avail Use% Mounted on
  udev992M 0  992M   0% /dev
  tmpfs   200M  3.2M  197M   2% /run
  /dev/sda1   9.7G  2.5G  7.3G  26% /
  tmpfs   999M 0  999M   0% /dev/shm
  tmpfs   5.0M 0  5.0M   0% /run/lock
  tmpfs   999M 0  999M   0% /sys/fs/cgroup
  vagrant 210G  183G   28G  88% /vagrant
  tmpfs   200M 0  200M   0% /run/user/1000

  
  With artful64, the size of /dev/sda1 is reported as 2.2G, which results in 
97% of disk usage immediately after building, even though the disk size is 10G, 
as reported by the fdisk:

  
  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  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: dos
  Disk identifier: 0x4ad77c39

  Device Boot Start  End  Sectors Size Id Type
  /dev/sda1  * 2048 20971486 20969439  10G 83 Linux

  
  Disk /dev/sdb: 10 MiB, 10485760 bytes, 20480 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes

  
  Almost any additional installation results in a "No space left on device" 
error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1726818/+subscriptions

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

[Kernel-packages] [Bug 1732512] Re: xen hibernation support for linux-aws

[Kamal Mostafa]

A test kernel with the indicated patch set has received positive smoke
test results from Amazon and myself:

git://git.launchpad.net/~kamalmostafa/ubuntu/+source/linux/+git/linux-
aws hib

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

Title:
  xen hibernation support for linux-aws

Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  linux-aws needs multiple commits from mainline and Amazon Linux to
  support xen hibernation:

  UBUNTU: aws: [Config] disable SUSPEND
  UBUNTU: aws: [Config] disable XEN_FBDEV_FRONTEND,
  xen: move xen_setup_runstate_info and get_runstate_snapshot to
  (cherry picked from commit 4ccefbe597392d2914cf7ad904e33c734972681d)
  xen/time: use READ_ONCE
  (cherry picked from commit 2dd887e32175b624375570a0361083eb2cd64a07)
  xen: add steal_clock support on x86
  (back-ported from commit ecb23dc6f2eff0ce64dd60351a81f376f13b12cc)
  xen: support runqueue steal time on xen
  (cherry picked from commit 6ba286ad845799b135e5af73d1fbc838fa79f709)
  x86/xen: use xen_vcpu_id mapping for HYPERVISOR_vcpu_op
  (cherry picked from commit ad5475f9faf5186b7f59de2c6481ee3e211f1ed7)
  xen: add static initialization of steal_clock op to xen_time_ops
  (cherry picked from commit d34c30cc1fa80f509500ff192ea6bc7d30671061)
  x86/xen: update cpuid.h from Xen-4.7
  (cherry picked from commit de2f5537b397249e91cafcbed4de64a24818542e)
  x86/acpi: store ACPI ids from MADT for future usage
  (cherry picked from commit 3e9e57fad3d8530aa30787f861c710f598ddc4e7)
  xen: introduce xen_vcpu_id mapping
  (back-ported from commit 88e957d6e47f1232ad15b21e54a44f1147ea8c1b)
  xen: update xen headers
  (cherry picked from commit 7ba8dba95cb227eb6c270b1aa77f942e45f5e47c)
  xen: change the type of xen_vcpu_id to uint32_t
  (cherry picked from commit 55467dea2967259f21f4f854fc99d39cc5fea60e)
  xen/blkfront: separate per ring information out of device info
  (cherry picked from commit 81f351615772365d46ceeac3e50c9dd4e8f9dc89)
  xen/blkfront: pseudo support for multi hardware queues/rings
  (cherry picked from commit 3df0e5059908b8fdba351c4b5dd77caadd95a949)
  xen/blkfront: split per device io_lock
  (cherry picked from commit 11659569f7202d0cb6553e81f9b8aa04dfeb94ce)
  xen/blkfront: negotiate number of queues/rings to be used with
  (cherry picked from commit 28d949bcc28bbc2d206f9c3f69b892575e81c040)
  xen/blkfront: Cleanup of comments, fix unaligned variables, and
  (cherry picked from commit 6f03a7ff89485f0a7a559bf5c7631d2986c4ecfa)
  xen/blkfront: Remove duplicate setting of ->xbdev.
  (cherry picked from commit 75f070b3967b0c3bf0e1bc43411b06bab6c2c2cd)
  xen/blkfront: make persistent grants pool per-queue
  (cherry picked from commit 73716df7da4f60dd2d59a9302227d0394f1b8fcc)
  xen/blkfront: correct setting for xen_blkif_max_ring_order
  (cherry picked from commit 45fc82642e54018740a25444d1165901501b601b)
  xen/blkfront: realloc ring info in blkif_resume
  (cherry picked from commit 3db70a853202c252a8ebefa71ccb088ad149cdd2)
  blk-mq: dynamic h/w context count
  (back-ported from commit 868f2f0b72068a097508b6e8870a8950fd8eb7ef)
  xen-blkfront: save uncompleted reqs in blkfront_resume()
  (cherry picked from commit 7b427a59538a98161321aa46c13f4ea81b43f4eb)
  xen-blkfront: fix places not updated after introducing 64KB page
  (cherry picked from commit 6c647b0eb01cd7326dca093590f5e123e3c68b9c)
  blk-mq: mark request queue as mq asap
  (cherry picked from commit 66841672161efb9e3be4a1dbd9755020bb1d86b7)
  blk-mq: Fix NULL pointer updating nr_requests
  (cherry picked from commit e9137d4b93078b6a9965acfb18a2a2ad91cf8405)
  xen-blkfront: fix resume issues after a migration
  (cherry picked from commit 2a6f71ad99cabe436e70c3f5fcf58072cb3bc07f)
  xen-blkfront: introduce blkif_set_queue_limits()
  (back-ported from commit 172335ada40ce26806e514c83a504b45c14a4139)
  xen/pvhvm: run xen_vcpu_setup() for the boot CPU
  (cherry picked from commit ee42d665d3f5db975caf87baf101a57235ddb566)
  UBUNTU: SAUCE: [aws] xen/manage: keep track of the on-going suspend
  UBUNTU: SAUCE: [aws] xen/manage: introduce helper function to know
  UBUNTU: SAUCE: [aws] xenbus: add freeze/thaw/restore callbacks
  UBUNTU: SAUCE: [aws] x86/xen: decouple shared_info mapping from
  UBUNTU: SAUCE: [aws] x86/xen: add system core suspend and resume
  UBUNTU: SAUCE: [aws] xen/time: introduce
  UBUNTU: SAUCE: [aws] x86/xen: save and restore steal clock
  UBUNTU: SAUCE: [aws] xen/events: add xen_shutdown_pirqs helper
  UBUNTU: SAUCE: [aws] x86/xen: close event channels for PIRQs in
  UBUNTU: SAUCE: [aws] xen-netfront: add callbacks for PM suspend and
  UBUNTU: SAUCE: [aws] xen-blkfront: add callbacks for PM suspend and
  UBUNTU: SAUCE: [aws] x86/xen: handle CPU_UP_PREPARE_FROZEN for PM
  UBUNTU: SAUCE: [aws] xen-netfront: 

[Kernel-packages] [Bug 159356] Re: System freeze on high memory usage

[SwaJime]

yas, when I try that, I get "bash: /proc/sys/vm/drop_caches: Permission
denied" on Ubuntu 16.04

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

Title:
  System freeze on high memory usage

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I run a batch matlab job server here at my lab, running Dapper 6.06 (for the 
LTS). One of the users has submitted a very memory-consuming job, which 
successfully crashes the server. Upon closer inspection, the crash happens like 
this:
  1. I run matlab with the given file (as an ordinary, unpriveleged user)
  2. RAM usage quickly fills up
  3. Once the RAM meter hits 100%, the system freezes: All SSH connections 
freeze up, and while switching VTs directly on the machine works, no new 
processes run - so one can't log in, or do anything if he is logged in. 
(Sometimes typing doesn't work at all)

  Note that the swap - while 7 gigs of it are available - is never used.
  (The machine has 7 gigs of RAM as well)

  I've tried the same on my Gutsy 32-bit box, and there was no system
  freezeup - matlab simply notified that the system was out of memory.
  However, it did this once memory was 100% in use - and still, swap
  didn't get used at all! (Though it is mounted correctly and shows up
  in "top" and "free").

  So first thing's first - I'd like to eliminate the crash issue. I
  suppose I could switch the server to 32-bit, but I think that would be
  a performance loss, considering that it does a lot of heavy
  computation. There is no reason, however, that this should happen on a
  64-bit machine anyway. Why does it?

  WORKAROUND: Enabling DMA in the BIOS

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

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

[Kernel-packages] [Bug 1732512] [NEW] xen hibernation support for linux-aws

[Kamal Mostafa]

Public bug reported:

linux-aws needs multiple commits from mainline and Amazon Linux to
support xen hibernation:

UBUNTU: aws: [Config] disable SUSPEND
UBUNTU: aws: [Config] disable XEN_FBDEV_FRONTEND,
xen: move xen_setup_runstate_info and get_runstate_snapshot to
(cherry picked from commit 4ccefbe597392d2914cf7ad904e33c734972681d)
xen/time: use READ_ONCE
(cherry picked from commit 2dd887e32175b624375570a0361083eb2cd64a07)
xen: add steal_clock support on x86
(back-ported from commit ecb23dc6f2eff0ce64dd60351a81f376f13b12cc)
xen: support runqueue steal time on xen
(cherry picked from commit 6ba286ad845799b135e5af73d1fbc838fa79f709)
x86/xen: use xen_vcpu_id mapping for HYPERVISOR_vcpu_op
(cherry picked from commit ad5475f9faf5186b7f59de2c6481ee3e211f1ed7)
xen: add static initialization of steal_clock op to xen_time_ops
(cherry picked from commit d34c30cc1fa80f509500ff192ea6bc7d30671061)
x86/xen: update cpuid.h from Xen-4.7
(cherry picked from commit de2f5537b397249e91cafcbed4de64a24818542e)
x86/acpi: store ACPI ids from MADT for future usage
(cherry picked from commit 3e9e57fad3d8530aa30787f861c710f598ddc4e7)
xen: introduce xen_vcpu_id mapping
(back-ported from commit 88e957d6e47f1232ad15b21e54a44f1147ea8c1b)
xen: update xen headers
(cherry picked from commit 7ba8dba95cb227eb6c270b1aa77f942e45f5e47c)
xen: change the type of xen_vcpu_id to uint32_t
(cherry picked from commit 55467dea2967259f21f4f854fc99d39cc5fea60e)
xen/blkfront: separate per ring information out of device info
(cherry picked from commit 81f351615772365d46ceeac3e50c9dd4e8f9dc89)
xen/blkfront: pseudo support for multi hardware queues/rings
(cherry picked from commit 3df0e5059908b8fdba351c4b5dd77caadd95a949)
xen/blkfront: split per device io_lock
(cherry picked from commit 11659569f7202d0cb6553e81f9b8aa04dfeb94ce)
xen/blkfront: negotiate number of queues/rings to be used with
(cherry picked from commit 28d949bcc28bbc2d206f9c3f69b892575e81c040)
xen/blkfront: Cleanup of comments, fix unaligned variables, and
(cherry picked from commit 6f03a7ff89485f0a7a559bf5c7631d2986c4ecfa)
xen/blkfront: Remove duplicate setting of ->xbdev.
(cherry picked from commit 75f070b3967b0c3bf0e1bc43411b06bab6c2c2cd)
xen/blkfront: make persistent grants pool per-queue
(cherry picked from commit 73716df7da4f60dd2d59a9302227d0394f1b8fcc)
xen/blkfront: correct setting for xen_blkif_max_ring_order
(cherry picked from commit 45fc82642e54018740a25444d1165901501b601b)
xen/blkfront: realloc ring info in blkif_resume
(cherry picked from commit 3db70a853202c252a8ebefa71ccb088ad149cdd2)
blk-mq: dynamic h/w context count
(back-ported from commit 868f2f0b72068a097508b6e8870a8950fd8eb7ef)
xen-blkfront: save uncompleted reqs in blkfront_resume()
(cherry picked from commit 7b427a59538a98161321aa46c13f4ea81b43f4eb)
xen-blkfront: fix places not updated after introducing 64KB page
(cherry picked from commit 6c647b0eb01cd7326dca093590f5e123e3c68b9c)
blk-mq: mark request queue as mq asap
(cherry picked from commit 66841672161efb9e3be4a1dbd9755020bb1d86b7)
blk-mq: Fix NULL pointer updating nr_requests
(cherry picked from commit e9137d4b93078b6a9965acfb18a2a2ad91cf8405)
xen-blkfront: fix resume issues after a migration
(cherry picked from commit 2a6f71ad99cabe436e70c3f5fcf58072cb3bc07f)
xen-blkfront: introduce blkif_set_queue_limits()
(back-ported from commit 172335ada40ce26806e514c83a504b45c14a4139)
xen/pvhvm: run xen_vcpu_setup() for the boot CPU
(cherry picked from commit ee42d665d3f5db975caf87baf101a57235ddb566)
UBUNTU: SAUCE: [aws] xen/manage: keep track of the on-going suspend
UBUNTU: SAUCE: [aws] xen/manage: introduce helper function to know
UBUNTU: SAUCE: [aws] xenbus: add freeze/thaw/restore callbacks
UBUNTU: SAUCE: [aws] x86/xen: decouple shared_info mapping from
UBUNTU: SAUCE: [aws] x86/xen: add system core suspend and resume
UBUNTU: SAUCE: [aws] xen/time: introduce
UBUNTU: SAUCE: [aws] x86/xen: save and restore steal clock
UBUNTU: SAUCE: [aws] xen/events: add xen_shutdown_pirqs helper
UBUNTU: SAUCE: [aws] x86/xen: close event channels for PIRQs in
UBUNTU: SAUCE: [aws] xen-netfront: add callbacks for PM suspend and
UBUNTU: SAUCE: [aws] xen-blkfront: add callbacks for PM suspend and
UBUNTU: SAUCE: [aws] x86/xen: handle CPU_UP_PREPARE_FROZEN for PM
UBUNTU: SAUCE: [aws] xen-netfront: add longer default freeze timeout
UBUNTU: SAUCE: [aws] PM / hibernate: update the resume offset on

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

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

Title:
  xen hibernation support for linux-aws

Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  linux-aws needs multiple commits from mainline and Amazon Linux to
  support xe

[Kernel-packages] [Bug 159968] RE

[Kennedyshead]

Check 
[Bug 159968] Re: ButtonPress and ButtonRelease of button 4 are generated by 
left click of synaptic touch pad

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

Title:
  ButtonPress and ButtonRelease of button 4 are generated by left click
  of synaptic touch pad

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have Xnote C1 which has synaptic touchpad with two buttons - left
  and right button.  Left button acts like scroll down button and right
  button acts like scroll button of mouse.  screen is scrolled down on
  pressing left button and  is scrolled up on pressing right button.

  xev prints the following message when click left button:

  ButtonPress event, serial 31, synthetic NO, window 0x381,
  root 0x1a5, subw 0x0, time 180885017, (53,85), root:(872,643),
  state 0x0, button 4, same_screen YES

  ButtonPress event, serial 31, synthetic NO, window 0x381,
  root 0x1a5, subw 0x0, time 180885092, (53,85), root:(872,643),
  state 0x800, button 1, same_screen YES

  ButtonRelease event, serial 31, synthetic NO, window 0x381,
  root 0x1a5, subw 0x0, time 180885153, (53,85), root:(872,643),
  state 0x900, button 1, same_screen YES

  ButtonRelease event, serial 31, synthetic NO, window 0x381,
  root 0x1a5, subw 0x0, time 180885153, (53,85), root:(872,643),
  state 0x800, button 4, same_screen YES

  
  the following message comes from /proc/bus/input/devices:

  I: Bus=0017 Vendor=0001 Product=0001 Version=0100
  N: Name="Macintosh mouse button emulation"
  P: Phys=
  S: Sysfs=/class/input/input0
  U: Uniq=
  H: Handlers=mouse0 event0 
  B: EV=7
  B: KEY=7 0 0 0 0
  B: REL=3

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/class/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: EV=120013
  B: KEY=40200 3802078f840d001 fedfffef fbfe
  B: MSC=10
  B: LED=7

  I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
  N: Name="SynPS/2 Synaptics TouchPad"
  P: Phys=isa0060/serio2/input0
  S: Sysfs=/class/input/input2
  U: Uniq=
  H: Handlers=mouse1 event2 
  B: EV=b
  B: KEY=6420 70003 0 0 0 0
  B: ABS=1103

  I: Bus=0019 Vendor= Product=0002 Version=
  N: Name="Power Button (FF)"
  P: Phys=button_power/button/input0
  S: Sysfs=/class/input/input3
  U: Uniq=
  H: Handlers=kbd event3 
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/class/input/input4
  U: Uniq=
  H: Handlers=event4 
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button (CM)"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/class/input/input5
  U: Uniq=
  H: Handlers=kbd event5 
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button (CM)"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/class/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: EV=3
  B: KEY=4000 0 0

  synaptic touchpad is configured like the bellow in /etc/X11/xorg.conf:

  Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "ZAxisMapping"  "4 5"
Option  "Emulate3Buttons"   "true"
  EndSection

  Section "InputDevice"
Identifier  "Synaptics Touchpad"
Driver  "synaptics"
Option  "SendCoreEvents""true"
Option  "Device""/dev/psaux"
Option  "Protocol"  "auto-dev"
Option  "HorizEdgeScroll"   "0"
Option  "SHMConfig" "on"
  EndSection

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

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

[Kernel-packages] [Bug 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Khaled El Mously (kmously) => Thadeu Lima de Souza Cascardo 
(cascardo)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Khaled El Mously (kmously) => Thadeu Lima de Souza Cascardo 
(cascardo)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Khaled El Mously (kmously) => Thadeu Lima de Souza Cascardo 
(cascardo)

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1731266
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase-changed:Wednesday, 15. November 2017 18:01 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
  
  backports: 1731266
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Promoted to proposed
+ phase: Uploaded
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase-changed:Wednesday, 15. November 2017 18:01 UTC
- kernel-stable-phase:Uploaded

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

Title:
  linux: 4.4.0-101.124 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: 1731266
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1731264] Re: linux: 4.4.0-101.124 -proposed tracker

[Khaled El Mously]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Khaled El Mously 
(kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Khaled El Mously 
(kmously)

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Khaled El Mously 
(kmously)

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

Title:
  linux: 4.4.0-101.124 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: 1731266
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel

[Sebastian Thürrschmidt]

@gernophil: If by a "new kernel release" you mean Linux 4.14, you won't
see that in artful. That's not how kernel updates are done in Ubuntu.
For more details see https://wiki.ubuntu.com/Kernel/FAQ.

Back to the bug in question. I have an Acer Aspire E5-573 32DN laptop
with a Qualcomm Atheros QCA9377 wireless adapter that suffers from the
symptoms described in here. It runs fine with the 4.13.10-041310
mainline kernel, as suggested above.

I also tried the kernel packages from -proposed (4.13.0-17.20) but those
wouldn't even boot right. Did anybody else have more success?

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

Title:
  Shutdown hangs / no standby - possible Wifi-bug in the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Shutdown-process hangs. After about two minutes the following
  message is displayed:

  Oct 17 18:47:06 Kahlan kernel: [  363.170588] INFO: task kworker/u8:2:186 
blocked for more than 120 seconds.
  Oct 17 18:47:06 Kahlan kernel: [  363.170592]   Tainted: P   OE   
4.13.0-12-generic #13-Ubuntu
  Oct 17 18:47:06 Kahlan kernel: [  363.170593] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.

  Two Minutes later this message is displayed:
  Oct 17 18:49:07 Kahlan kernel: [  484.008650] INFO: task kworker/u8:2:186 
blocked for more than 120 seconds.
  Oct 17 18:49:07 Kahlan kernel: [  484.008659]   Tainted: P   OE   
4.13.0-12-generic #13-Ubuntu
  Oct 17 18:49:07 Kahlan kernel: [  484.008662] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.

  This message repeates itself. If I am lucky, my laptop shuts down
  after some time.

  Also standby does not work. I think my wifi-adapter causes this
  problem.

  With Ubuntu 17.04 or Suse 42.3 I cannot reproduce this problem. I
  found a bug report in the Arch Bug System
  (https://bugs.archlinux.org/task/55872

  In my laptop I have also a Qualcomm Atheros Adapter. Perhaps the
  linuxkernel has a bug?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Oct 17 19:08:32 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-12-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0962]
  InstallationDate: Installed on 2017-10-07 (10 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Acer Aspire VN7-571G
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=d5a4b134-b39a-4764-99bd-208c9e504fa8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.family: Broadwell System
  dmi.product.name: Aspire VN7-571G
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1723837] 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 1723837

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

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

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

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

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

Title:
  Mouse buttons do not work upon resume from suspend.

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Mouse buttons do not work upon resume from suspend. Ctrl-Alt-F1 and
  then Ctrl-Alt-F7 restores mouse button functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1723837/+subscriptions

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

[Kernel-packages] [Bug 1723837] Re: Mouse buttons do not work upon resume from suspend.

[Martin Wimpress]

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

** Changed in: ubuntu-mate
   Status: Incomplete => Invalid

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

Title:
  Mouse buttons do not work upon resume from suspend.

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  Mouse buttons do not work upon resume from suspend. Ctrl-Alt-F1 and
  then Ctrl-Alt-F7 restores mouse button functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1723837/+subscriptions

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

[Kernel-packages] [Bug 1728565] 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 1728565

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

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

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

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

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

Title:
  Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I upgraded my NC10 netbook from Ubuntu Mate 16.04 to 17.04 (which worked 
okay) and then to 17.10. When starting up and automatically logging in I can 
see the right hand quarter of the screen but the left three quarters are mostly 
black with multicolour icons repeated across the top 3mm, a light grey bar 
below this  8mm high with a darker grey interruption just over half way across 
and two small horizontal white lines directly below this. The mouse pointer is 
displayed where ever it is positioned and the right hand menus work as 
expected. The computer is unusable in this condition.
  Dropping to a terminal with Ctrl+Alt+F1 has the same screen corruption and 
the prompt is spread across multiple lines as a series of dots and dashes - 
completely unreadable. It seems the video driver is not working for this 
machine in this release. The previous release showed it was using the standard 
Intel open source drivers. Issue persists when PC rebooted. Power up shows 
Samsung boot screen then light grey screen with small dark grey border then the 
corruption described above grey background and green pattern (probably the boot 
image corrupted then clearing to corruption over black background then to the 
state described, i.e. mostly black with a bit of desk top and some corrupted 
stuff at top.

  I can probably ssh in to this machine to grab logs as required so
  please let me know what I can do to help debug and get my laptop back
  working.

  Computer is a Samsung NP-NC10 with 1GB RAM and Intel Atom CPU.
  (Sorry I didn't find time to test the beta!!!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1728565/+subscriptions

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

[Kernel-packages] [Bug 1553687] Re: Lenovo Y700-17ISK Boot Error: Failure writing sector 0x21c8800 to 'hd0'

[Launchpad Bug Tracker]

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

** Changed in: grub2 (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/1553687

Title:
  Lenovo Y700-17ISK Boot Error: Failure writing sector 0x21c8800 to
  'hd0'

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Boot Error:
  failure writing sector 0x21c8800 to 'hd0'
  press any key to continue...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:11:22 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1728565] Re: Desktop (screen) corrupted after upgrade to 17.10

[Martin Wimpress]

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

** Changed in: ubuntu-mate
   Status: New => 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/1728565

Title:
  Desktop (screen) corrupted after upgrade to 17.10

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  I upgraded my NC10 netbook from Ubuntu Mate 16.04 to 17.04 (which worked 
okay) and then to 17.10. When starting up and automatically logging in I can 
see the right hand quarter of the screen but the left three quarters are mostly 
black with multicolour icons repeated across the top 3mm, a light grey bar 
below this  8mm high with a darker grey interruption just over half way across 
and two small horizontal white lines directly below this. The mouse pointer is 
displayed where ever it is positioned and the right hand menus work as 
expected. The computer is unusable in this condition.
  Dropping to a terminal with Ctrl+Alt+F1 has the same screen corruption and 
the prompt is spread across multiple lines as a series of dots and dashes - 
completely unreadable. It seems the video driver is not working for this 
machine in this release. The previous release showed it was using the standard 
Intel open source drivers. Issue persists when PC rebooted. Power up shows 
Samsung boot screen then light grey screen with small dark grey border then the 
corruption described above grey background and green pattern (probably the boot 
image corrupted then clearing to corruption over black background then to the 
state described, i.e. mostly black with a bit of desk top and some corrupted 
stuff at top.

  I can probably ssh in to this machine to grab logs as required so
  please let me know what I can do to help debug and get my laptop back
  working.

  Computer is a Samsung NP-NC10 with 1GB RAM and Intel Atom CPU.
  (Sorry I didn't find time to test the beta!!!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1728565/+subscriptions

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

[Kernel-packages] [Bug 1721365] Re: Allow drivers to use Relaxed Ordering on capable root ports

[dann frazier]

** Summary changed:

- ixgbe/PCIe: Allow drivers to use Relaxed Ordering on capable root ports
+ Allow drivers to use Relaxed Ordering on capable root ports

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

Title:
  Allow drivers to use Relaxed Ordering on capable root ports

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

Bug description:
  [Impact]
  A signficant performance gain can be achieved with the iperf benchmark by 
allowing the ixgbe driver to take advantage of PCIe Relaxed Ordering, as 
observed on the HiSilicon D05 system.

  [Test Case]
  Setup two servers with dual-port PCIe ixgbe cards, connected back-to-back.

  = server =
  taskset -c 0-15 iperf -s -B 192.168.80.11 &
  taskset -c 16-31 iperf -s -B 192.168.90.11 &

  = client =
  taskset -c 0-15 iperf -c 192.168.80.11 -i 3 -t 600 -P 8 &
  taskset -c 16-31 iperf -c 192.168.90.11 -i 3 -t 600 -P 8 &

  Without these patches, we observe an aggregate performance of 8.54
  Gbit/sec. With these patches, we observe an aggregate performance of
  18.82 Gbit/sec.

  [Regression Risk]
  The following risk assessment applies to both artful and zesty - but note 
that the bulk of these changes are *already in artful*. The proposed SRU for 
artful would just allow an additional driver to take advantage of it. For 
zesty, an SRU would need to both introduce this feature and enable it for both 
the cxgb4 and ixgbe drivers.

  The patchset is careful to only enable Relaxed Ordering if advertised
  up through the root port. However, it is possible that enabling RO on
  hardware that supports it could actually regress performance, or that
  there is hw out there that advertises RO, but has bugs in the
  implementation. The patch series includes quirks for HW where RO is
  advertised but known to have issues[*] - but this list maybe
  incomplete. This would only impact devices w/ drivers that take
  advantage of RO - currently cxgb4 and (not yet upstream) ixgbe.

  Also, there is a possibility of a crash caused by a coding error. One
  such issue has already been found and fixed upstream [**], and is part
  of this series.

  The risk of both of these regressions is reduced by the fact that this
  code is upstream, and has therefore gotten a lot more testing that has
  not resulted in regressions reports.

  [*]
  commit 077fa19c5dfa06a6ae04fb1661680940ff837612
  Author: dingtianhong 
  Date:   Tue Aug 15 11:23:25 2017 +0800

  PCI: Disable Relaxed Ordering Attributes for AMD A110
  commit 87e09cdec4dae08acdb4aa49beb793c19d73e73e
  Author: dingtianhong 
  Date:   Tue Aug 15 11:23:24 2017 +0800

  PCI: Disable Relaxed Ordering for some Intel processors

  [**]
  commit 0e405232871d67bf1b238d56b6b3d500e69ebbf3
  Author: dingtianhong 
  Date:   Tue Aug 15 23:24:48 2017 +0800

  PCI: fix oops when try to find Root Port for a PCI device

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

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

[Kernel-packages] [Bug 1729573] Re: netplan breaks Xen VIF driver

[Launchpad Bug Tracker]

This bug was fixed in the package nplan - 0.32

---
nplan (0.32) bionic; urgency=medium

  * src/nm.c: better handle the UUID generation; the order of iterating
through interaces may affect things here. Also make sure the tests catch
a null UUID.

 -- Mathieu Trudel-Lapierre   Tue, 14 Nov 2017
08:53:51 -0500

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

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

Title:
  netplan breaks Xen VIF driver

Status in linux package in Ubuntu:
  Won't Fix
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in nplan source package in Xenial:
  New
Status in linux source package in Zesty:
  Won't Fix
Status in nplan source package in Zesty:
  New
Status in linux source package in Artful:
  Won't Fix
Status in nplan source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Won't Fix
Status in nplan source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Some network interfaces on a Xen guest are broken by new behavior
  introduced by netplan.  On a Xen guest instance, when netplan is run
  to 'apply' its configuration, under certain circumstances netplan will
  try to "reset" the interface by unbinding and then re-binding the
  interface driver from the interface, by using the sysfs "bind" and
  "unbind" functions of the driver.  Normally, this results in the
  interface being released and then fully re-initialized by the driver.

  However the Xen VIF driver breaks when this is done.  The internal Xen
  backend state of the interface remains in 'closed' state after the
  driver re-connects to the interface, and attempts to open and use the
  interface result in a kernel Oops in the Xen VIF driver.

  To users, it appears that the interface is unusable because it has an
  all 0 mac address; but if the mac is manually set and the interface
  brought up the driver Oopses as mentioned above.

  This problem makes booting painful because of very long timeouts
  waiting for all network interfaces to start, and affected Xen VIF
  interfaces will of course never complete startup.

  [Fix]

  No fix yet.  Upstream kernel does not appear fixed.

  [Test Case]

  Create a guest instance under a Xen hypervisor (e.g. an AWS instance)
  that has Ubuntu Artful 17.10 installed.  Use only a single interface
  at first when creating it.  Then once it is ready, attach a second
  network interface to the instance.  From inside the instance,
  configure the new interface in netplan (i.e. add a /etc/netplan/
  config for it).  Make sure the new interface is down (netplan does not
  appear to unbind/bind interfaces that are up), and then run:

  $ sudo netplan apply

  or for debug,

  $ sudo netplan --debug apply

  this will unbind and re-bind the second interface, which will then
  have all-0 mac, and will be unusable, as described above.

  [Regression Potential]

  Changes to the Xen VIF driver can result in unusable network
  interfaces, or problems while using Xen VIF interfaces.

  [Other Info]

  Problem appears to exist upstream also.

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

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

[Kernel-packages] [Bug 1732463] Re: linux 4.14.0-7.9 ADT test failure with linux 4.14.0-7.9

[Seth Forshee]

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

Title:
  linux 4.14.0-7.9 ADT test failure with linux 4.14.0-7.9

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/l/linux/20171114_222341_0da97@/log.gz

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

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

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

[dann frazier]

** Also affects: cloud-archive
   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/1710019

Title:
  support GICv3 ITS save/restore & migration

Status in Ubuntu Cloud Archive:
  New
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  In Progress
Status in qemu source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in qemu source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]
  The kernel changes are restricted to ARM, minimizing the regression risk on 
other architectures. Other than one minor offset adjustment, all patches are 
clean cherry-picks from upstream. Tested on Cavium ThunderX and Qualcomm 
Centriq.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1710019/+subscriptions

-- 
Mailing list: https://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 1718548] Re: ubuntu-fan autopkgtests are broken against systemd-resolved

[Steve Langasek]

On Wed, Nov 15, 2017 at 09:32:18AM -, Stefan Bader wrote:
> @Steve, we try to get the code base of Fan synced across releases (one
> part of the reasons is that docker and lxd may backport things at any
> time, the other part is to avoid having to maintain subtly different
> code bases). The changes I attributed to this bug are an additional exit
> in an awk script which is verified by the tests still working. The other
> part is adding tests and print statements for DNS configuration (host
> and container side) which can be verified by looking at the test logs.

> As for the docker tests failing, we probably should move that to its
own bug. Right now this only happens in the CI environment and I cannot
see much that the Fan testing could do:

The bottom line here is that an SRU with failing autopkgtests is not
releasable.  The CI infrastructure is the *primary target* for autopkgtests.
If you are not going to support these autopkgtests in the CI infrastructure,
they should be disabled, not left failing.

>From my perspective the failing docker.io tests aren't a different bug, they
started failing at the same time according to
.

-- 
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:
  Triaged
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed

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 1713751] Re: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel

[Michael Pardee]

There were no shutdown issues with 4.13.0-16-generic in 20 shutdowns -
very promising.  I am switching back to 4.10.0-33 now to make sure the
problem still occurs and nothing else has changed.

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

Title:
  soft lockup / stall on CPU when shutting down with hwe 4.10 kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  In Progress

Bug description:
  Instead of normal complete shutdowns we're getting soft lockup
  failures. This started when 16.04 hwe packages switched to the 4.10
  kernel about a month ago. I help manage a few hundred machines
  spanning several different sites and several different hardware models
  and they're all experiencing this intermittently, approximately 5% get
  stuck on shutdown each day.

  Here is an example of what is on the screen after it happens, the
  machine is unresponsive and requires a hard reset.  I can't see
  anything in syslog or dmesg that differs when this happens, I think
  all logging has stopped at this point in the shutdown.

  [54566.220003] ? (t=6450529 jiffies g=141935 c=141934 q=1288)
  [54592.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
(systemd:1)
  [54620.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
(systemd:1)
  [54648.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
(systemd:1)
  [54676.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
(systemd:1)
  [54704.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
(systemd:1)
  [54732.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
(systemd:1)
  [54746.232003] INFO: rcu_sched self-detected stall on CPU
  [54746.232003] ?1-...: (6495431 ticks this GP) idle=5c7/141/0 
softirq=218389/218389 fqs=3247712

  This repeats every ~ 22 seconds, sometimes it is stuck for 23s instead of 22: 
  ... NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! 

  
  Reverting to 4.8.0-58 avoids the problem. I believe the problem has been 
present with every hwe 4.10 kernel package through the current 
linux-image-4.10.0-33-generic.  This bug was filed with data right after it 
occurred with linux-image-4.10.0-33-generic.

  This only happens approximately 5% of the time with no discernible
  pattern.  I am able to reproduce the issue on one particular machine
  by scheduling shutdowns 3 times per day and waiting up to a few days
  for the problem to occur. Shutting down and starting up more
  frequently, like every 5 minutes or even an hour, will not trigger the
  problem, it seems like the machine needs to be running for a while.
  It does not seem to depend on any user actions, it happens even if you
  never login.  It has happened on reboots as as opposed to shutdowns as
  well.   I found a few similar bug reports but nothing for these exact
  symptoms.

  I have tried blacklisting mei_me with no change in behavior.  I'm not
  sure but the majority of the affected machines are using intel video
  chips.  Next I am going to try a mainline 4.10 kernel.

  
  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  apt-cache policy linux-image-4.10.0-33-generic
  linux-image-4.10.0-33-generic:
Installed: 4.10.0-33.37~16.04.1
Candidate: 4.10.0-33.37~16.04.1
Version table:
   *** 4.10.0-33.37~16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug 29 08:57:26 2017
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1732463] 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 1732463

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

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

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

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

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

Title:
  linux 4.14.0-7.9 ADT test failure with linux 4.14.0-7.9

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/l/linux/20171114_222341_0da97@/log.gz

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

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

[Kernel-packages] [Bug 1727024] Re: zfs-linux 0.6.5.11-1ubuntu3 ADT test failure with linux 4.14.0-3.4

[Seth Forshee]

Tests pass in latest run, so closing.

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

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

Title:
  zfs-linux 0.6.5.11-1ubuntu3 ADT test failure with linux 4.14.0-3.4

Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/z/zfs-linux/20171024_140344_d0953@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/z/zfs-linux/20171024_120405_d0953@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/s390x/z/zfs-linux/20171024_120045_d0953@/log.gz

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

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

[Kernel-packages] [Bug 1732463] [NEW] linux 4.14.0-7.9 ADT test failure with linux 4.14.0-7.9

[Seth Forshee]

Public bug reported:

Testing failed on:
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/l/linux/20171114_222341_0da97@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  linux 4.14.0-7.9 ADT test failure with linux 4.14.0-7.9

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Testing failed on:
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/l/linux/20171114_222341_0da97@/log.gz

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

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

[Kernel-packages] [Bug 1719853] Re: Plantronics P610 does not support sample rate reading

[Stefan Bader]

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

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

** Also affects: linux (Ubuntu Zesty)
   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/1719853

Title:
  Plantronics P610 does not support sample rate reading

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  New

Bug description:
  As per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282 , I
  believe the USB ID 0x047F 0xC02F needs to be added to quirks.c in
  order for me to use my Plantronics P610. Thanks!

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

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

[Kernel-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

[Konrad Zapałowicz]

** Attachment added: "1731467-failure-case.snoop"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+attachment/5009473/+files/1731467-failure-case.snoop

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

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  Confirmed

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

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

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

[Kernel-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

[Konrad Zapałowicz]

The only relevant log files that can be provided for this issue is a HCI
trace. It is in .snoop format therefore can be viewed in wireshark.

Attaching two log files:

1) failure-case: without proposed patch
2) success-case: with proposed patch

** Attachment added: "1731467-success-case.snoop"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+attachment/5009472/+files/1731467-success-case.snoop

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  Confirmed

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Brad]

On my machine it's a very difficult problem to reproduce.  I've only
gotten it to fail once so far with days of use on Antergos 17.9.  First
step in debugging this is finding how to reproduce it consistently.
Anyone know how?

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1650956] Re: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

[Nathan Cain]

I see the same thing on 17.10.

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

Title:
  ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.018601] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
  [0.018602] ENERGY_PERF_BIAS: View and update with 
x86_energy_perf_policy(8)

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

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

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

[Kernel-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

[Stefan Bader]

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

** Also affects: bluez (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/1731467

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in bluez source package in Xenial:
  New
Status in linux source package in Xenial:
  New

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

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

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

[Kernel-packages] [Bug 1731257] Re: linux 4.14.0-6.8 ADT test failure with linux 4.14.0-6.8

[Seth Forshee]

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

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

Title:
  linux 4.14.0-6.8 ADT test failure with linux 4.14.0-6.8

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/l/linux/20171107_153858_c2c05@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/l/linux/20171108_140414_c2c05@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/ppc64el/l/linux/20171107_154212_c2c05@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/l/linux/20171107_150354_c2c05@/log.gz

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

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

[Kernel-packages] [Bug 1732424] 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/1732424

Title:
  Surface Pro 4. System hangs when suspended or hibernated

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Surface Pro 4. I have problems with sleep and hibernation on
  my computer, because once it's turned on, the system won't wake up and
  you have to force the power off.

  I have tried several kernels:

  *The normal version

  *linux-image-4.9.0-rc8-mssp4+_4.9.0-rc8-mssp4+-10.00. Custom_amd64
  (special for Surface)

  *The last 4.14 kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1532 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov 15 13:13:19 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (24 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1732424] [NEW] Surface Pro 4. System hangs when suspended or hibernated

[Hicks]

Public bug reported:

I have a Surface Pro 4. I have problems with sleep and hibernation on my
computer, because once it's turned on, the system won't wake up and you
have to force the power off.

I have tried several kernels:

*The normal version

*linux-image-4.9.0-rc8-mssp4+_4.9.0-rc8-mssp4+-10.00. Custom_amd64
(special for Surface)

*The last 4.14 kernel

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  predatux   1532 F pulseaudio
CurrentDesktop: KDE
Date: Wed Nov 15 13:13:19 2017
HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
Lsusb:
 Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
 Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Microsoft Corporation Surface Pro 4
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic  N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-22 (24 days ago)
dmi.bios.date: 02/24/2017
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: 106.1624.768
dmi.board.name: Surface Pro 4
dmi.board.vendor: Microsoft Corporation
dmi.chassis.type: 9
dmi.chassis.vendor: Microsoft Corporation
dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
dmi.product.family: Surface
dmi.product.name: Surface Pro 4
dmi.product.version: D:0B:08F:1C:03P:38
dmi.sys.vendor: Microsoft Corporation

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


** Tags: amd64 apport-bug artful

** Summary changed:

- System hangs when suspended or hibernated
+ Surface Pro 4. System hangs when suspended or hibernated

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

Title:
  Surface Pro 4. System hangs when suspended or hibernated

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Surface Pro 4. I have problems with sleep and hibernation on
  my computer, because once it's turned on, the system won't wake up and
  you have to force the power off.

  I have tried several kernels:

  *The normal version

  *linux-image-4.9.0-rc8-mssp4+_4.9.0-rc8-mssp4+-10.00. Custom_amd64
  (special for Surface)

  *The last 4.14 kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1532 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov 15 13:13:19 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (24 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.l

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Brad]

what do you mean? you enabled it in the mouse panel and now the problem
is gone?  It's working now for you?

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4

[Hicks]

At the moment wifi still working... No crashes.

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

Title:
  Wifi does down "crash" in Surface Pro 4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[iBART]

^ maybe it is not a dead touchpad thing. I have forgotten that I
disabled it by mouse panel menu. So, apparently, after the login it is
enabled for a couple of seconds; after that, I guess, the setting
switches it off.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[iBART]

Another interesting fact: I noticed that if i try to move the touchpad
(rc7 kernel) as soon as I entered the password to login, it dies. But if
I move it after a couple of seconds after the login, I have no problems
at all. Once, it freezed my entire pc. Hard reset. Kaput.

I don't know how to debug this.

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1730852] Re: Device hotplugging with MPT SAS cannot work for VMWare ESXi

[Stefan Bader]

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

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

** Also affects: linux (Ubuntu Zesty)
   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/1730852

Title:
  Device hotplugging with MPT SAS cannot work for VMWare ESXi

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  New

Bug description:
  [Impact]
  The hotplugging disk cannot be detected with the simulated MPT SAS 
  device on VMWare ESXi.

  [Fix]
  Author: Hannes Reinecke 
  Date:   Thu Aug 24 14:52:43 2017 +0200

  scsi: mptsas: Fixup device hotplug for VMWare ESXi
  
  VMWare ESXi emulates an mptsas HBA, but exposes all drives as
  direct-attached SAS drives.  This it not how the driver originally
  envisioned things; SAS drives were supposed to be connected via an
  expander, and only SATA drives would be direct attached. As such, any 
  hotplug event for direct-attach SAS drives was silently ignored, and 
  the guest failed to detect new drives from within a VMWare ESXi
  environment.

  [Test]
  The patch has been verified based on the Ubuntu kernel v4.4.0-97.120.

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

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

[Kernel-packages] [Bug 1732034] Re: Microphone headset isn't detected with Intel Skull Canyon NUC

[Andrew Vos]

How do I try that kernel?

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

Title:
  Microphone headset isn't detected with Intel Skull Canyon NUC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've also tested this machine with two separate USB Microphone
  adapters, and they do the same thing really. Super-low volume on the
  mic. I can only see a bit of a spike if I tap the mic hard.

  I can confirm the Headset/Microphone selection screen pops up when
  plugging the headset in.

  This workaround works after a reboot:

  https://communities.intel.com/thread/108361

  > # Add to /etc/modprobe.d/alsa-base.conf
  > options snd-hda-intel model=dell-headset-multi

  I'm using this headset https://www.amazon.co.uk/HyperX-Stinger-Gaming-
  Headset-
  
Mobile/dp/B01LRX2DSA/ref=sr_1_2?ie=UTF8&qid=1510612581&sr=8-2&ppw=fresh&keywords=hyperx+gaming+headphones

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrewvos   1395 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 22:30:33 2017
  InstallationDate: Installed on 2017-11-10 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b7992a74-c44e-44cc-be68-f658972e448f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0050.2017.0831.1924
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0050.2017.0831.1924:bd08/31/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

-- 
Mailing list: https://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 1730924] Re: Wifi does down "crash" in Surface Pro 4

[Hicks]

El 14/11/17 a las 17:54, Joseph Salisbury escribió:
> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular problem?
No, always
>
> 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].

Testing...
>
> 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
>
>
> ** 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/1730924

Title:
  Wifi does down "crash" in Surface Pro 4

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1721070] Re: powerpc/64s: Add workaround for P9 vector CI load issue

[Po-Hsu Lin]

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

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

Title:
  powerpc/64s: Add workaround for P9 vector CI load issue

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  
  == SRU Justification ==
  POWER9 DD2.1 and earlier has an issue where some cache inhibited
  vector load will return bad data. The fix is two part, one
  firmware/microcode part triggers HMI interrupts when hitting such
  loads, the other part is commit 5080332c2c89 from linux-next which then
  emulates the instructions in Linux.

  The affected instructions are limited to lxvd2x, lxvw4x, lxvb16x and
  lxvh8x.

  Commit ccd3cd361341 is needed as a prereq for Artful.
  Commits a3d96f70c147 and ccd3cd361341 are needed as prereqs for Zesty.

  == Fixes ==
  a3d96f70c147 ("powerpc/64s: Fix system reset vs general interrupt reentrancy")
  ccd3cd361341 ("powerpc/mce: Move 64-bit machine check code into mce.c")
  5080332c2c89 ("powerpc/64s: Add workaround for P9 vector CI load issue")

  == Regression Potential ==
  These commits are specific to powerpc.  They required some back porting but
   have been tested by IBM.


  -- Problem Description --

  When an instruction triggers the HMI, all threads in the core will be
  sent to the HMI handler, not just the one running the vector load.

  In general, these spurious HMIs are detected by the emulation code and
  we just return back to the running process. Unfortunately, if a
  spurious interrupt occurs on a vector load that's to normal memory we
  have no way to detect that it's spurious (unless we walk the page
  tables, which is very expensive). In this case we emulate the load but
  we need do so using a vector load itself to ensure 128bit atomicity is
  preserved.

  Some additional debugfs emulated instruction counters are added also.

  In order to solve this bug, we need to cherry pick the following patch

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next&id=5080332c2c893118dbc18755f35c8b0131cf0fc4

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

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

[Kernel-packages] [Bug 1729277] Re: linux-aws: 4.4.0-1003.3 -proposed tracker

[Po-Hsu Lin]

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

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

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

Title:
  linux-aws: 4.4.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in 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: 1731264
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1729277] Re: linux-aws: 4.4.0-1003.3 -proposed tracker

[Po-Hsu Lin]

4.4.0-1003.3 - aws
Regression test CMPL.

Issue to note in x86_64 (aws):
  ebizzy - failed only on one instance (t2.nano), passed on the rest
  libhugetlbfs - 1 failed (alloc-instantiate-race shared), bad configuration 3, 
failed on 4 instances, passed on the rest
  ubuntu_fan_smoke_test - should be skipped on Trusty
  ubuntu_kvm_smoke_test - CPU does not support KVM extensions
  ubuntu_kvm_unit_tests - test disabled
  ubuntu_ltp - should be skipped on Trusty
  ubuntu_lttng_smoke_test - should be skipped on Trusty
  ubuntu_stress_smoke_test - should be skipped on Trusty
  ubuntu_sysdig_smoke_test - should be skipped on Trusty


** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux-aws: 4.4.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in 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: 1731264
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1722702] Re: libvirt - vnc port selection regression with newer kernels

[ChristianEhrhardt]

Waiting on the kernel fix to fully release, but as we won't change
libvirt updating the task.

** Changed in: libvirt (Ubuntu Artful)
   Status: Confirmed => Won't Fix

** Changed in: libvirt (Ubuntu)
   Status: Won't Fix => Fix Released

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

Title:
  libvirt - vnc port selection regression with newer kernels

Status in libvirt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in libvirt source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: Bug appears in linux-image-4.11.x kernels on 16.04.3.
  4.8.x and 4.10.x are okay.

  When libvirtd is restarted on Kernel 4.11.0-x-generic or above , it
  loses all information regarding existing port bindings and is unable
  to correctly re-identify vnc ports that currently in use. libvirt
  attempts to bind to an existing port and fails.

  instance-000a6096.log:2017-10-09T01:42:16.017220Z
  qemu-system-x86_64: -vnc 0.0.0.0:0: Failed to start VNC server: Failed to 
listen on socket: Address already in use

  Fairly certain this is the same bug reported, and patched in
  kernel-4.13.4-200.fc26 for Fedora
  https://bugzilla.redhat.com/show_bug.cgi?id=1432684

  Fix: Cherry picking a set of 3 patches (merged as the same set by
  David Miller) from upstream Linux.

  Testcase: Restart of libvirt.

  Risk for Regressions: Looking at the changes those 3 patches
  introduce, the delta is minimal and makes sense with respect to the
  explanations given in the commit message. Overall risk should be low.

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

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

[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

[Thorsten]

(sry for the second post) 
then 
 sudo update-grub 

and reboot

-- 
You 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 after resuming from suspend

Status in Linux:
  Unknown
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/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 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

[Thorsten]

hi, thanks a lot! I'm now using 4.13 with this parameter at it is
working fine!

For others you have to edit the file /etc/default/grub and change the line:
 
   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to 
 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash psmouse.synaptics_intertouch=0"

then

-- 
You 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 after resuming from suspend

Status in Linux:
  Unknown
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/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 1718548] Re: ubuntu-fan autopkgtests are broken against systemd-resolved

[Stefan Bader]

@Steve, we try to get the code base of Fan synced across releases (one
part of the reasons is that docker and lxd may backport things at any
time, the other part is to avoid having to maintain subtly different
code bases). The changes I attributed to this bug are an additional exit
in an awk script which is verified by the tests still working. The other
part is adding tests and print statements for DNS configuration (host
and container side) which can be verified by looking at the test logs.

As for the docker tests failing, we probably should move that to its own bug. 
Right now this only happens in the CI environment and I cannot see much that 
the Fan testing could do:
- the hosting VM (artful/bionic) is using netplan and from print statements
  has systemd-resolv ready before launching the container
- the container (docker) uses its own DNS resolver, we pull latest lts images so
  those are xenial based atm.
- the image is pulled by dockerd, so that has at least DNS resolution for the
  proxy
- however inside the container (and unfortunately that is rather limited in the
  supplied commands) DNS lookups via the docker resolver fail.

I can pull the current cloud-images used by adt locally and get all
testing passed without the slightest issue.

-- 
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:
  Triaged
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed

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 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

[Kai-Heng Feng]

Fortunately that commit introduces an extra knob, so you can use
"psmouse.synaptics_intertouch=0" to turn it off as a temporary
workaround.

-- 
You 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 after resuming from suspend

Status in Linux:
  Unknown
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/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 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

[Kai-Heng Feng]

e839ffab028981ac77f650faf8c84f16e1719738 is the first bad commit
commit e839ffab028981ac77f650faf8c84f16e1719738
Author: Benjamin Tissoires 
Date:   Thu Mar 2 14:13:53 2017 -0800

Input: synaptics - add support for Intertouch devices

Most of the Synaptics devices are connected through PS/2 and a different
bus (SMBus or HID over I2C). The secondary bus capability is indicated by
the InterTouch bit in extended capability 0x0C.

We only enable the InterTouch device to be created for the laptops
registered with the top software button property or those we know that are
functional. In the future, we might change the default to always rely on
the InterTouch bus. Currently, users can enable/disable the feature with
the psmouse parameter synaptics_intertouch.

Signed-off-by: Benjamin Tissoires 
Signed-off-by: Dmitry Torokhov 


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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=196719
   Importance: Unknown
   Status: Unknown

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

Title:
  Two-finger scrolling no longer works after resuming from suspend

Status in Linux:
  Unknown
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/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 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

[Thorsten]

hi, this is also working fine for me

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

Title:
  Two-finger scrolling no longer works after resuming from suspend

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 1731080] Re: Very slow display on Legacy mode, but it's normal on UEFI mode

[Leo-Chen]

https://bugs.freedesktop.org/show_bug.cgi?id=103751

** Bug watch added: freedesktop.org Bugzilla #103751
   https://bugs.freedesktop.org/show_bug.cgi?id=103751

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

Title:
  Very slow display on Legacy mode, but it's normal on UEFI mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I start boot into OS in text mode with BIOS Legacy mode,it is
  very slow display for example do type cmd: cat /proc/cpuinfo ,but I
  had tried add a GRUB_CMDLINE_LINUX=”vga=normal” in /etc/default/grub.
  It can be normal display

  My config on the server :
  OS ver:Ubuntu 16.04.x server w/o GUI
  VGA: onboard AST2x00 w/o install expansion vga card

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

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

[Kernel-packages] [Bug 1732370] 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 1732370

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

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

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

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

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

Title:
  ThunderX arm64 system failed with test 079 in zfs_xfs_generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This system constantly fails with the generic test 079 in
  ubuntu_zfs_xfs_generic test suite, even with the latest code from
  upstream.

  07:59:46 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_zfs_xfs_generic.079', 'ubuntu_zfs_xfs_generic.079')
  07:59:46 DEBUG| Waiting for pid 12399 for 3600 seconds
  07:59:47 INFO | Running: 
/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 079 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  07:59:51 DEBUG| [stdout]
  08:00:01 ERROR| Exception escaping from test:
  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
    File 
"/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.py",
 line 98, in run_once
  self.results = utils.system_output(cmd, retain_output=True)
    File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in 
system_output
  verbose=verbose, args=args).stdout
    File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
  "Command returned non-zero exit status")
  CmdError: Command 
 failed, rc=1, 
Command returned non-zero exit status
  * Command:
  /home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_
  generic.sh 079 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  Exit status: 1
  Duration: 13.813601017

  stdout:
  Creating zfs pool testpool..
  Creating zfs file systems test and scratch in testpool..
  VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  FSTYP -- zfs
  PLATFORM  -- Linux/aarch64 wright-kernel 4.10.0-38-generic
  MKFS_OPTIONS  -- testpool/scratch
  MOUNT_OPTIONS -- testpool/scratch /mnt/scratch

  generic/079- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad)
  --- tests/generic/079.out 2017-11-15 07:40:51.054794973 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad
2017-11-15 07:59:52.910100549 +
  @@ -1,7 +1,6 @@
   QA output created by 079
   *** starting up
  -testing immutable...PASS.
  -testing append-only...PASS.
  -testing immutable as non-root...PASS.
  -testing append-only as non-root...PASS.
  +acl: Function not implemented
  ...
  (Run 'diff -u tests/generic/079.out 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad'
  to see the entire diff)
  Ran: generic/079
  Failures: generic/079
  Failed 1 of 1 tests

  Destroying zfs pool testpool
  Removing VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42
  ProcVersionSignature: User Name 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic aarch64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 15 03:29 seq
   crw-rw 1 root audio 116, 33 Nov 15 03:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:

  Date: Wed Nov 15 06:27:54 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Cavium ThunderX CRB
  

[Kernel-packages] [Bug 1732162] Re: Zesty / Artful zKVM does not have /dev/kvm

[ChristianEhrhardt]

Hi,
I investigated this a bit.

TL;DR - this is intentionally off by default and opt in.
To use it you need:
- in the host set kvm.nested=1
- depending on your other virt stack set you might need to set host-passthrough 
or the sief2 feature (qemu -cpu host or ...,sief2=1)

Then the guest will have virt features "sie" in /proc/cpuinfo | grep
features

If anything we should consider backporting the "needs opt in" to Xenial.
That would be the following patch:
commit a411edf1320ed8fa3b4560902ac4e033c4a72bcf
Author: David Hildenbrand 
Date:   Tue Feb 2 15:41:22 2016 +0100

KVM: s390: vsie: add module parameter "nested"

Let's be careful first and allow nested virtualization only if enabled
by the system administrator. In addition, user space still has to
explicitly enable it via SCLP features for it to work.

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

Title:
  Zesty / Artful zKVM does not have /dev/kvm

Status in linux package in Ubuntu:
  Triaged

Bug description:
  For now we have 3 zKVM instances running Xenial, Zesty and Artful
  kernel respectively.

  The /dev/kvm does not exist on Zesty and Artful kernel.

  kvm-ok output on Zesty
  $ sudo kvm-ok
  INFO: /dev/kvm does not exist
  HINT:   sudo modprobe kvm
  modprobe: FATAL: Module msr not found in directory 
/lib/modules/4.10.0-40-generic

  kvm-ok output on Artful
  $ sudo kvm-ok
  INFO: /dev/kvm does not exist
  HINT:   sudo modprobe kvm
  modprobe: FATAL: Module msr not found in directory 
/lib/modules/4.13.0-17-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic s390x
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Tue Nov 14 11:18:49 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1732370] Re: ThunderX arm64 system failed with test 079 in zfs_xfs_generic

[Po-Hsu Lin]

The content of 079.out.bad is:
QA output created by 079
*** starting up
acl: Function not implemented
*** cleaning up
t_immutable: error opening /mnt/scratch/079/append-only.f: No such file or 
directory
t_immutable: Warning, expected parts of the test area missing, not removing.

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

Title:
  ThunderX arm64 system failed with test 079 in zfs_xfs_generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This system constantly fails with the generic test 079 in
  ubuntu_zfs_xfs_generic test suite, even with the latest code from
  upstream.

  07:59:46 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_zfs_xfs_generic.079', 'ubuntu_zfs_xfs_generic.079')
  07:59:46 DEBUG| Waiting for pid 12399 for 3600 seconds
  07:59:47 INFO | Running: 
/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 079 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  07:59:51 DEBUG| [stdout]
  08:00:01 ERROR| Exception escaping from test:
  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
    File 
"/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.py",
 line 98, in run_once
  self.results = utils.system_output(cmd, retain_output=True)
    File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in 
system_output
  verbose=verbose, args=args).stdout
    File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
  "Command returned non-zero exit status")
  CmdError: Command 
 failed, rc=1, 
Command returned non-zero exit status
  * Command:
  /home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_
  generic.sh 079 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  Exit status: 1
  Duration: 13.813601017

  stdout:
  Creating zfs pool testpool..
  Creating zfs file systems test and scratch in testpool..
  VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
  FSTYP -- zfs
  PLATFORM  -- Linux/aarch64 wright-kernel 4.10.0-38-generic
  MKFS_OPTIONS  -- testpool/scratch
  MOUNT_OPTIONS -- testpool/scratch /mnt/scratch

  generic/079- output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad)
  --- tests/generic/079.out 2017-11-15 07:40:51.054794973 +
  +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad
2017-11-15 07:59:52.910100549 +
  @@ -1,7 +1,6 @@
   QA output created by 079
   *** starting up
  -testing immutable...PASS.
  -testing append-only...PASS.
  -testing immutable as non-root...PASS.
  -testing append-only as non-root...PASS.
  +acl: Function not implemented
  ...
  (Run 'diff -u tests/generic/079.out 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad'
  to see the entire diff)
  Ran: generic/079
  Failures: generic/079
  Failed 1 of 1 tests

  Destroying zfs pool testpool
  Removing VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42
  ProcVersionSignature: User Name 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic aarch64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 15 03:29 seq
   crw-rw 1 root audio 116, 33 Nov 15 03:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:

  Date: Wed Nov 15 06:27:54 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
  RelatedPackageVersions:
   linu

[Kernel-packages] [Bug 1731269] Re: linux: 4.10.0-40.44 -proposed tracker

[Po-Hsu Lin]

4.10.0-40.44 - generic
Regression test CMPL.

Issue to note in amd64:
  hwclock - failed on lodygin only, bug 1714229
  libhugetlbfs - 6 failed (small_const / small_data is not hugepage), 7 killed 
by signal, 1 bad configuration
  monotonic_time - tsc failed on lodygin
  ubuntu_kvm_unit_tests - 19 failed on secchi, 20 failed on michael, 29 failed 
on pepe, 61 failed on lodygin
  ubuntu_unionmount_overlayfs_suite - failed on michael, passed on the rest
  xfstests - btrfs generic/166 timed out, bug 1731455

Issue to note in arm64:
  rtc - Update IRQs not supported on node wright
  ubuntu_bpf - failed to build, bug 1675395
  ubuntu_docker_smoke_test - Failed to fetch file, looks like a firewall issue
  ubuntu_kernel_selftests - breakpoint test failed to build, bug 1680507
  ubuntu_kvm_smoke_test - video device 'cirrus' not supported by qemu, bug 
1732338
  ubuntu_zfs_xfs_generic - test 079 (bug 1732370), 317 failed

Issue to note in i386:
  ubuntu_bpf - test_maps bpf test crashed, bug 1711512
  ubuntu_kvm_unit_tests - 7 failed on pepe (smap, hypercall, msr, tsc, 
taskswitch2, hyperv_connections, hyperv_stimer)
  xfstests - out of space, bug 1720343

Issue to note in ppc64le:
  libhugetlbfs - 6 failed, 6 killed by signal (small_const / small_data is not 
hugepage)
  rtc - Update IRQs not supported.
  ubuntu_kvm_smoke_test - uvtool issue, bug 1452016
  ubuntu_kvm_unit_tests - sprs failed, bug 1712803
  ubuntu_zfs_xfs_generic - generic/192 failed, passed after re-test
  xfstests - btrfs generic/166 timed out, bug 1731455

Issue to note in s390x (zKVM):
  aio_dio_bugs - event res -22, bug 1730895
  libhugetlbfs - 11 failed, 7 killed by signal, 1 bad config (the 1 extra 
failure is a new case)
  scrashme - failed to build bug 1689240
  ubuntu_bpf - failed to build, bug 1711299
  ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed (28 failed)
  ubuntu_kvm_smoke_test - KVM not available, bug 1732162
  ubuntu_kvm_unit_tests - selftest-setup and intercept failed, bug 1726225

Issue to note in s390x (zVM):
  aio_dio_bugs - event res -22, bug 1730895
  libhugetlbfs - IOError: [Errno 95] Operation not supported, bug 1729510
  scrashme - failed to build bug 1689240
  ubuntu_bpf - failed to build, bug 1711299
  ubuntu_ecryptfs - miscdev-bad-count.sh.xfs ~ namelen.sh failed (28 failed)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1452016)

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux: 4.10.0-40.44 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  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

  backports: 1731270
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1732370] [NEW] ThunderX arm64 system failed with test 079 in zfs_xfs_generic

[Po-Hsu Lin]

Public bug reported:

This system constantly fails with the generic test 079 in
ubuntu_zfs_xfs_generic test suite, even with the latest code from
upstream.

07:59:46 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_zfs_xfs_generic.079', 'ubuntu_zfs_xfs_generic.079')
07:59:46 DEBUG| Waiting for pid 12399 for 3600 seconds
07:59:47 INFO | Running: 
/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.sh
 079 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
07:59:51 DEBUG| [stdout]
08:00:01 ERROR| Exception escaping from test:
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
self.run_once(*args, **dargs)
  File 
"/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_generic.py",
 line 98, in run_once
self.results = utils.system_output(cmd, retain_output=True)
  File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in 
system_output
verbose=verbose, args=args).stdout
  File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
"Command returned non-zero exit status")
CmdError: Command 
 failed, rc=1, 
Command returned non-zero exit status
* Command:
/home/ubuntu/autotest/client/tests/ubuntu_zfs_xfs_generic/ubuntu_zfs_xfs_
generic.sh 079 /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
Exit status: 1
Duration: 13.813601017

stdout:
Creating zfs pool testpool..
Creating zfs file systems test and scratch in testpool..
VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src
FSTYP -- zfs
PLATFORM  -- Linux/aarch64 wright-kernel 4.10.0-38-generic
MKFS_OPTIONS  -- testpool/scratch
MOUNT_OPTIONS -- testpool/scratch /mnt/scratch

generic/079  - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad)
--- tests/generic/079.out   2017-11-15 07:40:51.054794973 +
+++ 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad
  2017-11-15 07:59:52.910100549 +
@@ -1,7 +1,6 @@
 QA output created by 079
 *** starting up
-testing immutable...PASS.
-testing append-only...PASS.
-testing immutable as non-root...PASS.
-testing append-only as non-root...PASS.
+acl: Function not implemented
...
(Run 'diff -u tests/generic/079.out 
/home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src/xfstests-bld/xfstests-dev/results//generic/079.out.bad'
  to see the entire diff)
Ran: generic/079
Failures: generic/079
Failed 1 of 1 tests

Destroying zfs pool testpool
Removing VDEVs in /home/ubuntu/autotest/client/tmp/ubuntu_zfs_xfs_generic/src

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-38-generic 4.10.0-38.42
ProcVersionSignature: User Name 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic aarch64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Nov 15 03:29 seq
 crw-rw 1 root audio 116, 33 Nov 15 03:29 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:

Date: Wed Nov 15 06:27:54 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Cavium ThunderX CRB
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 EFI VGA
 1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=ddcb8b36-6267-4392-a1f9-74d9203b742e ro
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-38-generic N/A
 linux-backports-modules-4.10.0-38-generic  N/A
 linux-firmware 1.164.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 0
dmi.chassis.vendor: Cavium
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Kai-Heng Feng]

Interesting. There are no change between v4.14-rc7 and v4.14-rc8 in hid
/i2c-hid, i2c and mfd drivers. Also, both -rc7 and -rc8 use the same
config file.

Maybe this is related to cold/warm boot?

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1726750] Re: linux-oem: 4.13.0-1007.8 -proposed tracker

[Timo Aaltonen]

** Package changed: linux (Ubuntu) => linux-oem (Ubuntu)

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

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

Title:
  linux-oem: 4.13.0-1007.8 -proposed tracker

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

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1731080] Re: Very slow display on Legacy mode, but it's normal on UEFI mode

[Kai-Heng Feng]

File an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/other

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

Title:
  Very slow display on Legacy mode, but it's normal on UEFI mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I start boot into OS in text mode with BIOS Legacy mode,it is
  very slow display for example do type cmd: cat /proc/cpuinfo ,but I
  had tried add a GRUB_CMDLINE_LINUX=”vga=normal” in /etc/default/grub.
  It can be normal display

  My config on the server :
  OS ver:Ubuntu 16.04.x server w/o GUI
  VGA: onboard AST2x00 w/o install expansion vga card

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

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