[Kernel-packages] [Bug 1673197] Re: Upgrading zfs-initramfs breaks booting from a zfs root

[Randall Leeds]

My last comment got cut off. I was going to say I don't see /usr/share
/initramfs-tools/conf.d/zfs on my filesystem.

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

Title:
  Upgrading zfs-initramfs breaks booting from a zfs root

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Upgrading to zfs-initramfs 0.6.5.9-4ubuntu1 breaks my boot.

  I've EFI and a small ext2 boot partition, and the rest of my SDD is a
  zfs pool. After upgrade I'm dropped in the initramfs shell and no
  zpools are available.

  Downgrading to 0.6.5.8-0ubuntu9 makes it boot again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: zfs-initramfs 0.6.5.9-4ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 15 18:29:04 2017
  InstallationDate: Installed on 2016-05-06 (312 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (113 days ago)

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

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

[Kernel-packages] [Bug 1673197] Re: Upgrading zfs-initramfs breaks booting from a zfs root

[Randall Leeds]

Maybe this is some regression in zfs-initramfs?

I see some mention of this in 
https://bugs.launchpad.net/ubuntu/+source/zfs-initramfs/+bug/1530953
I don

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

Title:
  Upgrading zfs-initramfs breaks booting from a zfs root

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Upgrading to zfs-initramfs 0.6.5.9-4ubuntu1 breaks my boot.

  I've EFI and a small ext2 boot partition, and the rest of my SDD is a
  zfs pool. After upgrade I'm dropped in the initramfs shell and no
  zpools are available.

  Downgrading to 0.6.5.8-0ubuntu9 makes it boot again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: zfs-initramfs 0.6.5.9-4ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 15 18:29:04 2017
  InstallationDate: Installed on 2016-05-06 (312 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (113 days ago)

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

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

[Kernel-packages] [Bug 1673197] Re: Upgrading zfs-initramfs breaks booting from a zfs root

[Randall Leeds]

I just happened to find that parameter mentioned in some ZFS root setup
guides and tried it as a wild guess.

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

Title:
  Upgrading zfs-initramfs breaks booting from a zfs root

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Upgrading to zfs-initramfs 0.6.5.9-4ubuntu1 breaks my boot.

  I've EFI and a small ext2 boot partition, and the rest of my SDD is a
  zfs pool. After upgrade I'm dropped in the initramfs shell and no
  zpools are available.

  Downgrading to 0.6.5.8-0ubuntu9 makes it boot again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: zfs-initramfs 0.6.5.9-4ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 15 18:29:04 2017
  InstallationDate: Installed on 2016-05-06 (312 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (113 days ago)

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

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

[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

[Kai-Heng Feng]

Probably because the WMI driver is not loaded.

Please install acpica-tools and run acpidump,

$ sudo apt install acpica-tools
$ sudo acpidump > acpi-dump

Attach acpi-dump file.

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [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)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: Name="G-SPY USB Gaming Mouse"
  P: Phys=usb-:00:14.0-2/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5
  U: Uniq=
  H: Handlers=sysrq kbd event5 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=e080ffdf01cf fffe
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=04d9 Product=a070 

[Kernel-packages] [Bug 1644919] Re: [fn] plus F2, F3, F4, F5, F6, F10, F11, F12 not responding - Fresh Install

[Kai-Heng Feng]

Hi,

Please download the attachment, and follow the steps:

$ tar xf gigabyte-wmi.tar.xz
$ cd gigabyte-wmi
$ make
$ sudo insmod gigabyte-wmi.ko

And attach the output of `dmesg`.

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

Title:
  [fn] plus F2,F3,F4,F5,F6,F10,F11,F12 not responding - Fresh Install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gigabyte P57 laptop

  Fresh install, 10 days old, updated yesterday so software/kernel
  should be current.

  Some function keys work.
  Function plus F1 puts the machine to sleep
  Function plus F7, F8, F9 control the volume

  However,
  Pressing Function plus F2 does not turn off wireless
  Pressing Function plus F3,F4 do not change brightness
  Function plus F5 does not change output to LCD or Monitor
  Pressing Function plus F6 does not toggle touchpad (a separate bug in this 
machine, but the Elantech touchpad is recognised at the moment.)
  Function plus F10 does not turn the display off
  Function plus F11 does not turn off bluetooth
  Function plus F12 does not disable the camera

  Please let me know if you need any further troubleshooting

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  horace 1948 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 26 07:44:13 2016
  HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e
  InstallationDate: Installed on 2016-11-13 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05af:1050 Jing-Mold Enterprise Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE P57
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FB0B
  dmi.board.asset.tag: Default string
  dmi.board.name: P57
  dmi.board.vendor: GIGABYTE
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: P57
  dmi.product.version: Default string
  dmi.sys.vendor: GIGABYTE

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

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

[Kernel-packages] [Bug 1644919] Re: [fn] plus F2, F3, F4, F5, F6, F10, F11, F12 not responding - Fresh Install

[Kai-Heng Feng]

** Attachment added: "gigabyte-wmi.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644919/+attachment/4839208/+files/gigabyte-wmi.tar.xz

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

Title:
  [fn] plus F2,F3,F4,F5,F6,F10,F11,F12 not responding - Fresh Install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gigabyte P57 laptop

  Fresh install, 10 days old, updated yesterday so software/kernel
  should be current.

  Some function keys work.
  Function plus F1 puts the machine to sleep
  Function plus F7, F8, F9 control the volume

  However,
  Pressing Function plus F2 does not turn off wireless
  Pressing Function plus F3,F4 do not change brightness
  Function plus F5 does not change output to LCD or Monitor
  Pressing Function plus F6 does not toggle touchpad (a separate bug in this 
machine, but the Elantech touchpad is recognised at the moment.)
  Function plus F10 does not turn the display off
  Function plus F11 does not turn off bluetooth
  Function plus F12 does not disable the camera

  Please let me know if you need any further troubleshooting

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  horace 1948 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Nov 26 07:44:13 2016
  HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e
  InstallationDate: Installed on 2016-11-13 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05af:1050 Jing-Mold Enterprise Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE P57
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FB0B
  dmi.board.asset.tag: Default string
  dmi.board.name: P57
  dmi.board.vendor: GIGABYTE
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: P57
  dmi.product.version: Default string
  dmi.sys.vendor: GIGABYTE

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

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

[Kernel-packages] [Bug 1673197] Re: Upgrading zfs-initramfs breaks booting from a zfs root

[Randall Leeds]

I don't know what changed, but adding `boot=zfs` to my grub kernel
parameters fixes this. I never needed it in the past and `update-grub`
doesn't create it.

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

Title:
  Upgrading zfs-initramfs breaks booting from a zfs root

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Upgrading to zfs-initramfs 0.6.5.9-4ubuntu1 breaks my boot.

  I've EFI and a small ext2 boot partition, and the rest of my SDD is a
  zfs pool. After upgrade I'm dropped in the initramfs shell and no
  zpools are available.

  Downgrading to 0.6.5.8-0ubuntu9 makes it boot again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: zfs-initramfs 0.6.5.9-4ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 15 18:29:04 2017
  InstallationDate: Installed on 2016-05-06 (312 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (113 days ago)

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

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

[Kernel-packages] [Bug 1667920] Re: login screen freeze

[Alexandru Chirvasitu]

Thanks!

That specific bug is gone in your version. I've booted and logged in
successfully and consistently, with and without GUI.

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

Title:
  login screen freeze

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

Bug description:
  Running an up-to-date (as of Feb 25 2017) 16.04 / Unity on an old MSI
  U160 netbook.

  After a recent update to kernel 4.4.0-63 I have started getting frozen
  login screens. The touchpad and keyboard are completely dead (before I
  ever get to enter my password), and my only way out is to force
  shutdown.

  I can start GRUB on boot and go for an earlier version instead, but
  everything past 4.4.0-62 freezes in the same fashion (that's what I'm
  currently running as a temporary fix); a newer update to 4.4.0-64 has
  not fixed the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chirvasitua   1841 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 03:42:57 2017
  HibernationDevice: RESUME=UUID=5e60245a-50f2-4f9c-97b2-d68560e38218
  InstallationDate: Installed on 2015-10-18 (495 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=250be7ea-5182-43d2-b638-5c4a933b4942 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EN051IMS.100
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-N051
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEN051IMS.100:bd02/06/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-N051:pvrTobefilledbyO.E.M.:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-N051:rvrTobefilledbyO.E.M.:cvnMICRO-STARINTERNATIONALCO.,LTD:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-N051
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Kernel-packages] [Bug 1672198] Re: RTL8723b Kernel driver not loading on normal boot. [kernel-bug-exists-upstream]

[Kai-Heng Feng]

In addition, please attach the output of `rfkill list`, thanks.

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

Title:
  RTL8723b Kernel driver not loading on normal boot. [kernel-bug-exists-
  upstream]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a very low end laptop with a built in rtl8723b wifi card. I
  always used the driver from lwfinger on github and that one worked
  well.

  But now Ubuntu comes with a driver for this card but that does not work on 
normal boot.
  Strange thing is this driver is initialised after resume from suspend.

  So i blacklisted the kernel module with:
  echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf

  and used the lwfinger driver from github again.

  So with rtl8xxu driver wifi card does not work on normal boot but does
  work when recovering from suspend to ram.

  Thank you. Bye.
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  InstallationDate: Installed on 2016-12-23 (79 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  serena
  Uname: Linux 4.9.10-040910-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1672198] Re: RTL8723b Kernel driver not loading on normal boot. [kernel-bug-exists-upstream]

[Kai-Heng Feng]

Can you boot with "rtl8xxxu.debug=0x" and attach the dmesg?

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

Title:
  RTL8723b Kernel driver not loading on normal boot. [kernel-bug-exists-
  upstream]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a very low end laptop with a built in rtl8723b wifi card. I
  always used the driver from lwfinger on github and that one worked
  well.

  But now Ubuntu comes with a driver for this card but that does not work on 
normal boot.
  Strange thing is this driver is initialised after resume from suspend.

  So i blacklisted the kernel module with:
  echo "blacklist rtl8xxxu" | sudo tee /etc/modprobe.d/rtl8xxxu.conf

  and used the lwfinger driver from github again.

  So with rtl8xxu driver wifi card does not work on normal boot but does
  work when recovering from suspend to ram.

  Thank you. Bye.
  ---
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  InstallationDate: Installed on 2016-12-23 (79 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  serena
  Uname: Linux 4.9.10-040910-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1616695] Re: Bluetooth signal is unusably poor

[JoaoH]

It would seem to me that with the recent boom in BT devices, that the
"importance" would be a little higher than "medium". I have a $250.00
set of Headphones that is basically useless and have to tether with an
audio cable. I am to the point that I may have to go back top Windows
and run the Linux apps in VM, it's that big of a deal breaker.

I am just saying...

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

Title:
  Bluetooth signal is unusably poor

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Brand new Macbook Pro 12,1.  Brand new Ubuntu 16.04 install (from
  scratch).

  In MacOS the machine can connect to my bluetooth speaker from across
  the room and play A2DP no trouble at all.  In Ubuntu 16.04 I have to
  literally hold up the macbook 1 inch away from the speaker to get it
  to connect and play, and even then it's a bit choppy.  Turning off
  Wifi seems to help a bit, which leads me to think this is some kind of
  transmit power issue.

  Syslog is chock full of warnings about skipping audio:

  Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 206099 us (= 36352 bytes) in audio stream
  Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 382089 us (= 67400 bytes) in audio stream
  Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 394108 us (= 69520 bytes) in audio stream
  Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 328125 us (= 57880 bytes) in audio stream
  Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 59087 us (= 10420 bytes) in audio stream
  Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 14036 us (= 2472 bytes) in audio stream
  Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 247134 us (= 43592 bytes) in audio stream
  Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 342190 us (= 60360 bytes) in audio stream
  Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 172035 us (= 30344 bytes) in audio stream
  Aug 24 16:22:35 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 803140 us (= 141672 bytes) in audio stream
  Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 651085 us (= 114848 bytes) in audio stream
  Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 202043 us (= 35640 bytes) in audio stream
  Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: 
Skipping 265112 us (= 46764 bytes) in audio stream

  
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

  $ uname -a
  Linux badassm 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ lsusb
  Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 05ac:0273 Apple, Inc. 
  Bus 001 Device 003: ID 05ac:8290 Apple, Inc. 
  Bus 001 Device 006: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 
4000 V1.0
  Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  $ hciconfig 
  hci0: Type: BR/EDR  Bus: USB
BD Address: 98:01:A7:A8:D4:6A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:5198 acl:2 sco:0 events:269 errors:0
TX bytes:7021 acl:2 sco:0 commands:218 errors:0

  [bluetooth]# show
  Controller 98:01:A7:A8:D4:6A
Name: badassm
Alias: badassm
Class: 0x1c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Vendor specific   

[Kernel-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs

[Mathieu Trudel-Lapierre]

** Description changed:

+ [Impact]
+ Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.
+ 
+ [Test case]
+ 1) Install on multipath system using EMC XtremIO storage / OR:
+  a) Start d-i install on qemu with multipath enabled
+  b) exit to d-i menu
+  c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
+  d) restart multipathd if necessary.
+ 2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
+ 3) Reboot to disk.
+ 
+ In a success case, the install should complete successfully without
+ requiring manual configuration from the user to support the multipath
+ storage past the normal detection of multipath and partitioning.
+ 
+ In a failure case, the install may not complete, or rebooting may fail
+ or lead to a system booted on a single path of the multipath device (ie.
+ / on /dev/sda2 rather than /dev/mpatha2).
+ 
+ [Regression Potential]
+ The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.
+ 
+ ---
+ 
  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs
  
  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.
  
  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.
  
  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.
  
  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.
  
  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.
  
  Patches are provided for 16.04 and 17.04.
  
  Error logs in LP comment #6.

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in multipath-tools package in Ubuntu:
  Triaged
Status in hw-detect source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in linux source package in Xenial:
  New
Status in multipath-tools source package in Xenial:
  New

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using 

[Kernel-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs

[Mathieu Trudel-Lapierre]

Triaged and assigned to me for the multipath-tools and d-i work. I've
notified the kernel team on IRC as well since I'll need to have
multipath-modules-udeb containing dm-queue-length before I can apply the
changes there. Then we can SRU the whole thing as well.

** Also affects: hw-detect (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: hw-detect (Ubuntu)
   Importance: Undecided => Critical

** Changed in: hw-detect (Ubuntu)
   Status: New => Triaged

** Changed in: hw-detect (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: hw-detect (Ubuntu)
Milestone: None => ubuntu-17.03

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in multipath-tools package in Ubuntu:
  Triaged
Status in hw-detect source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in linux source package in Xenial:
  New
Status in multipath-tools source package in Xenial:
  New

Bug description:
  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

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

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

[Kernel-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs

[Mathieu Trudel-Lapierre]

This goes without saying, thanks for filing this bug report.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Triaged

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Critical

** Also affects: multipath-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: multipath-tools (Ubuntu)
   Status: New => Triaged

** Changed in: multipath-tools (Ubuntu)
   Importance: Undecided => Critical

** Changed in: multipath-tools (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: initramfs-tools (Ubuntu)
Milestone: None => ubuntu-17.03

** Changed in: multipath-tools (Ubuntu)
Milestone: None => ubuntu-17.03

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

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

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

** Also affects: multipath-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in multipath-tools package in Ubuntu:
  Triaged
Status in hw-detect source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in linux source package in Xenial:
  New
Status in multipath-tools source package in Xenial:
  New

Bug description:
  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

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

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

[Kernel-packages] [Bug 1571416] Re: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC)

[K1773R]

change /etc/yaboot.conf
run: sudo ybin -v

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

Title:
  System freezes shortly after reaching the desktop (Ubuntu MATE 16.04,
  PowerPC)

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

Bug description:
  The freeze happens every time unless I use "radeon.agpmode=-1" as a
  kernel parameter.

  Affected machines:
  PowerBook G4 5,6 + PowerMac G5 7,3 (w. "ATI Radeon 9600 AP (AGP)".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-powerpc-smp 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-powerpc-smp 4.4.6
  Uname: Linux 4.4.0-18-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.373
  CurrentDesktop: MATE
  Date: Sun Apr 17 21:08:40 2016
  IwConfig:
   lono wireless extensions.

   enP2p36s15f0  no wireless extensions.
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160417.1)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: ro ramdisk_size=1048576 file=/cdrom/preseed/username.seed 
boot=casper quiet --- radeon.agpmode=-1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-powerpc-smp N/A
   linux-backports-modules-4.4.0-18-powerpc-smp  N/A
   linux-firmware1.157
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1673303] Re: [Xenial] net: better skb->sender_cpu and skb->napi_id cohabitation

[Joel Sing]

The firewalls deployed with the patched kernel have now been running
stably in production for more than 24 hours.

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

Title:
  [Xenial] net: better skb->sender_cpu and skb->napi_id cohabitation

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

Bug description:
  == Xenial SRU ==
  We've twice now tried to roll out new firewalls and twice had to
  revert back when the new firewalls almost immediately hung after
  cutover.

  At first we thought it was hardware issues, but after we reproduced it
  on 4 different firewalls, we realised it was more likely to be a
  problem with the Xenial kernel.

  We think we're running into something similar to:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579943

  And Joel thinks the following patch might fix it:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=52bd2d62ce6758d811edcbd2256eb9ea7f6a56cb

  Unfortunately, even when we mimic live production traffic on the new
  firewalls with port mirroring, we only have a ~20% success rate at
  reproducing the kernel hang and I'm keen not to have any more failed
  migration attempts (and the corresponding downtime for many many
  services).

  == Fix ==
  See http://kernel.ubuntu.com/~ogasawara/lp1579943/

  == Testing ==
  We've just successfully migrated four firewalls
  that are running with the patched kernel. Previously two of them would
  have survived for less than 2 minutes, both have now been running in
  production for over an hour.

  I'll provide another update tomorrow, however at this stage I'd suggest
  that it makes sense to get this into an SRU.

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

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

[Kernel-packages] [Bug 1571416] Re: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC)

[Marshall]

How do I add the boot options and have them stick? I tried modifying the
yaboot but I ended up breaking my install.

I can get it installed with the live radeon.agpmode=-1
then I was able to boot it by typing at the first boot Linux radeon.agpmode=-1

that's where it breaks down, I don't know how to make that change stick.
I'm used to using Linux Mint which is similar, but just different enough
that it breaks things when I try to adjust them.

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

Title:
  System freezes shortly after reaching the desktop (Ubuntu MATE 16.04,
  PowerPC)

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

Bug description:
  The freeze happens every time unless I use "radeon.agpmode=-1" as a
  kernel parameter.

  Affected machines:
  PowerBook G4 5,6 + PowerMac G5 7,3 (w. "ATI Radeon 9600 AP (AGP)".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-powerpc-smp 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-powerpc-smp 4.4.6
  Uname: Linux 4.4.0-18-powerpc-smp ppc
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: powerpc
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.373
  CurrentDesktop: MATE
  Date: Sun Apr 17 21:08:40 2016
  IwConfig:
   lono wireless extensions.

   enP2p36s15f0  no wireless extensions.
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release powerpc 
(20160417.1)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: ro ramdisk_size=1048576 file=/cdrom/preseed/username.seed 
boot=casper quiet --- radeon.agpmode=-1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-powerpc-smp N/A
   linux-backports-modules-4.4.0-18-powerpc-smp  N/A
   linux-firmware1.157
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1673635

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

Title:
  Touchpad doesn't work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell Inspiron N4110
  Touchpad doesn't work at all; not even in the LiveCD.

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

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

[Kernel-packages] [Bug 1673635] [NEW] Touchpad doesn't work

[Sanhita]

Public bug reported:

Dell Inspiron N4110
Touchpad doesn't work at all; not even in the LiveCD.

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

** Attachment added: "/proc/bus/input/devices"
   https://bugs.launchpad.net/bugs/1673635/+attachment/4839114/+files/devices

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

Title:
  Touchpad doesn't work

Status in linux package in Ubuntu:
  New

Bug description:
  Dell Inspiron N4110
  Touchpad doesn't work at all; not even in the LiveCD.

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

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

[Kernel-packages] [Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting

[Lo]

Hi Joseph

The kernel 4.11-rc1 with 16.04 still has the issue.

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

Title:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system
  hangs while rebooting

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

Bug description:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or 
UEFI mode.
  System hangs while rebooting

  Not found the issue in RAID0
  No issue on Ubuntu14.04
  Driver-OS inbox support

  Below as error messages
  ===
  INFO:  task systemd-shutdow:1 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task  jbd2/md126p2-8:1732 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task ext4lazyinit:1873 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

  INFO:  task kworker/u66:4:3139 blocked for more than 120 seconds.
  Not tainted 4.4.0-21-generic #37-Ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  ===

  WORKAROUND: edit /etc/sysctl.conf with follow commands and the system don't 
hang while rebooting:
  vm.dirty_background_ratio=5
  vm.dirty_ratio=10
  kernel.panic=3
  kernel.hung_task_panic=1
  kernel.hung_task_timeout_secs=30

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b
  InstallationDate: Installed on 2016-12-15 (10 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: Dell DCS6430G
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

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

  _MarkForUpload: True
  dmi.bios.date: 03/22/2016
  dmi.bios.vendor: Dell
  dmi.bios.version: 2.0.3
  dmi.board.name: 038VV0
  dmi.board.vendor: Dell
  dmi.board.version: X01
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell
  dmi.modalias: 
dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr:
  dmi.product.name: DCS6430G
  dmi.sys.vendor: Dell

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

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

[Kernel-packages] [Bug 1667920] Re: login screen freeze

[Joseph Salisbury]

An i386 version is now available in the same location:
http://kernel.ubuntu.com/~jsalisbury/lp1666421/

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

Title:
  login screen freeze

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

Bug description:
  Running an up-to-date (as of Feb 25 2017) 16.04 / Unity on an old MSI
  U160 netbook.

  After a recent update to kernel 4.4.0-63 I have started getting frozen
  login screens. The touchpad and keyboard are completely dead (before I
  ever get to enter my password), and my only way out is to force
  shutdown.

  I can start GRUB on boot and go for an earlier version instead, but
  everything past 4.4.0-62 freezes in the same fashion (that's what I'm
  currently running as a temporary fix); a newer update to 4.4.0-64 has
  not fixed the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chirvasitua   1841 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 03:42:57 2017
  HibernationDevice: RESUME=UUID=5e60245a-50f2-4f9c-97b2-d68560e38218
  InstallationDate: Installed on 2015-10-18 (495 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=250be7ea-5182-43d2-b638-5c4a933b4942 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EN051IMS.100
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-N051
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEN051IMS.100:bd02/06/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-N051:pvrTobefilledbyO.E.M.:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-N051:rvrTobefilledbyO.E.M.:cvnMICRO-STARINTERNATIONALCO.,LTD:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-N051
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[greenBird]

Watching the connect process, the phone try to pair my car as a headset.

My car use the protocol Hands-Free (HFP) 1.0 (or higher).

I believe there is no protocol HFP integrated. 
This could be the reason of connect error with cars.

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions

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

[Kernel-packages] [Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

[simon place]

cant see why this is still incomplete, enough here to say confirmed
surely.

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

Title:
  hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

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

Bug description:
  Message with Mouse Bluetooth

  [   32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag
  0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3344 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct 24 05:22:54 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-09-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/linux/+bug/1385113/+subscriptions

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

[Kernel-packages] [Bug 1672563] Re: ubuntu 16.04 doesnt boot normally on my asus k550vx

[farid]

no..it doesn't 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/1672563

Title:
  ubuntu 16.04 doesnt boot normally on my asus k550vx

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i just can boot ubuntu 16.04 in nomodeset or acpi=off mode. and even
  in this case when i try to install my nividia graphic cards driver, it
  never boots again after installation.

  my graphic card: nvidia 950m

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

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

[Kernel-packages] [Bug 1667531] Re: [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

[Joseph Salisbury]

I built a Xenial test kernel with all the patches from the following
bugs:

bug 1670518
 PCI: hv: Allocate physically contiguous hypercall params buffer
 PCI: hv: Make unnecessarily global IRQ masking functions static
 PCI: hv: Delete the device earlier from hbus->children for hot-remove
 PCI: hv: Fix hv_pci_remove() for hot-remove

bug 1672785 
 net/mlx4_core: Avoid delays during VF driver device shutdown

bug 1667531 
 tools: hv: Enable network manager for bonding scripts on RH
 [net-next] tools: hv: Add clean up function for Ubuntu config
 bcc5a76 tools: hv: Add a script to help bonding synthetic and VF NICs  

bug 1667527
4a9b0933bdfc PCI: hv: Use device serial number as PCI domain

bug 1667007 
d3de209 net/mlx4_core: Use cq quota in SRIOV when creating completion 
EQs

bug 1650058 
14c84da90b0d net/mlx4_en: Fix bad WQE issue
c46100f413ca net/mlx4_core: Fix racy CQ (Completion Queue) free
f4f73e2e6308 net/mlx4_core: Fix when to save some qp context flags for 
dynamic VST to VGT transitions
3c05ac20fe6e net/mlx4_core: Avoid command timeouts during VF driver 
device shutdown


The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/HyperVCombined/

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

Title:
  [Hyper-V] Include bondvf in /usr/sbin for SR-IOV interface bonding

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

Bug description:
  Please include bondvf.sh from kernel git tools/hv/ in /usr/sbin

  commit fd7aabb062fa1a8331a786d617744de220eaf002
  Author: Haiyang Zhang 
  Date:   Fri Dec 2 15:55:38 2016 -0800

  tools: hv: Enable network manager for bonding scripts on RHEL

  We found network manager is necessary on RHEL to make the synthetic
  NIC, VF NIC bonding operations handled automatically. So, enabling
  network manager here.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

  commit 178cd55f086629cf0bad9c66c793a7e2bcc3abb6
  Author: Haiyang Zhang 
  Date:   Mon Jul 11 17:06:42 2016 -0700

  tools: hv: Add a script to help bonding synthetic and VF NICs

  This script helps to create bonding network devices based on synthetic NIC
  (the virtual network adapter usually provided by Hyper-V) and the matching
  VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can
  function as one network device, and fail over to the synthetic NIC if VF 
is
  down.

  Mayjor distros (RHEL, Ubuntu, SLES) supported by Hyper-V are supported by
  this script.

  Signed-off-by: Haiyang Zhang 
  Reviewed-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 

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

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

[Kernel-packages] [Bug 1667007] Re: [Hyper-V] Mellanox VF driver does not support >16 vCPUs

[Joseph Salisbury]

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

I built a Xenial test kernel with all the patches from the following
bugs:

bug 1670518
 PCI: hv: Allocate physically contiguous hypercall params buffer
 PCI: hv: Make unnecessarily global IRQ masking functions static
 PCI: hv: Delete the device earlier from hbus->children for hot-remove
 PCI: hv: Fix hv_pci_remove() for hot-remove

bug 1672785 
 net/mlx4_core: Avoid delays during VF driver device shutdown

bug 1667531 
 tools: hv: Enable network manager for bonding scripts on RH
 [net-next] tools: hv: Add clean up function for Ubuntu config
 bcc5a76 tools: hv: Add a script to help bonding synthetic and VF NICs  

bug 1667527
4a9b0933bdfc PCI: hv: Use device serial number as PCI domain

bug 1667007 
d3de209 net/mlx4_core: Use cq quota in SRIOV when creating completion 
EQs

bug 1650058 
14c84da90b0d net/mlx4_en: Fix bad WQE issue
c46100f413ca net/mlx4_core: Fix racy CQ (Completion Queue) free
f4f73e2e6308 net/mlx4_core: Fix when to save some qp context flags for 
dynamic VST to VGT transitions
3c05ac20fe6e net/mlx4_core: Avoid command timeouts during VF driver 
device shutdown


The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/HyperVCombined/

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

Title:
  [Hyper-V] Mellanox VF driver does not support >16 vCPUs

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

Bug description:
  In the course of enabling SR-IOV on Azure, discovered that the
  Mellanox Driver with 16 or more vCPUs fails. Mellanox has submitted
  the following patch upstream to correct this problem.

  Prerequisite:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650058

  I will post the upstream commit once it lands.

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

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

[Kernel-packages] [Bug 1667527] Re: [Hyper-V] pci-hyperv: Use device serial number as PCI domain

[Joseph Salisbury]

I built a Xenial test kernel with all the patches from the following
bugs:

bug 1670518
 PCI: hv: Allocate physically contiguous hypercall params buffer
 PCI: hv: Make unnecessarily global IRQ masking functions static
 PCI: hv: Delete the device earlier from hbus->children for hot-remove
 PCI: hv: Fix hv_pci_remove() for hot-remove

bug 1672785 
 net/mlx4_core: Avoid delays during VF driver device shutdown

bug 1667531 
 tools: hv: Enable network manager for bonding scripts on RH
 [net-next] tools: hv: Add clean up function for Ubuntu config
 bcc5a76 tools: hv: Add a script to help bonding synthetic and VF NICs  

bug 1667527
4a9b0933bdfc PCI: hv: Use device serial number as PCI domain

bug 1667007 
d3de209 net/mlx4_core: Use cq quota in SRIOV when creating completion 
EQs

bug 1650058 
14c84da90b0d net/mlx4_en: Fix bad WQE issue
c46100f413ca net/mlx4_core: Fix racy CQ (Completion Queue) free
f4f73e2e6308 net/mlx4_core: Fix when to save some qp context flags for 
dynamic VST to VGT transitions
3c05ac20fe6e net/mlx4_core: Avoid command timeouts during VF driver 
device shutdown


The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/HyperVCombined/

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

Title:
  [Hyper-V] pci-hyperv: Use device serial number as PCI domain

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

Bug description:
  This allows PCI domain numbers starts with 1, and also unique
  on the same VM. So names, such as VF NIC names, that include
  domain number as part of the name, can be shorter than that
  based on part of bus UUID previously. The new names will also
  stay same for VMs created with copied VHD and same number of
  devices.

  This is needed for SR-IOV in Azure.

  This is Bjorn's tree for 4.11 here:
  https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci
  /host-hv=4a9b0933bdfcd85da840284bf5a0eb17b654b9c2

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

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

[Kernel-packages] [Bug 1672785] Re: [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver device shutdown

[Joseph Salisbury]

I built a Xenial test kernel with all the patches from the following
bugs:

bug 1670518
 PCI: hv: Allocate physically contiguous hypercall params buffer
 PCI: hv: Make unnecessarily global IRQ masking functions static
 PCI: hv: Delete the device earlier from hbus->children for hot-remove
 PCI: hv: Fix hv_pci_remove() for hot-remove

bug 1672785 
 net/mlx4_core: Avoid delays during VF driver device shutdown

bug 1667531 
 tools: hv: Enable network manager for bonding scripts on RH
 [net-next] tools: hv: Add clean up function for Ubuntu config
 bcc5a76 tools: hv: Add a script to help bonding synthetic and VF NICs  

bug 1667527
4a9b0933bdfc PCI: hv: Use device serial number as PCI domain

bug 1667007 
d3de209 net/mlx4_core: Use cq quota in SRIOV when creating completion 
EQs

bug 1650058 
14c84da90b0d net/mlx4_en: Fix bad WQE issue
c46100f413ca net/mlx4_core: Fix racy CQ (Completion Queue) free
f4f73e2e6308 net/mlx4_core: Fix when to save some qp context flags for 
dynamic VST to VGT transitions
3c05ac20fe6e net/mlx4_core: Avoid command timeouts during VF driver 
device shutdown


The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/HyperVCombined/

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

Title:
  [Hyper-V][Mellanox] net/mlx4_core: Avoid delays during VF driver
  device shutdown

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

Bug description:
  Mellanox has submitted the following patch upstream that's important
  for SR-IOV in Azure.

  Please integrate it into the Mellanox mlx4 drivers for lts-xenial,
  HWE, Zesty, and Azure custom.

  https://patchwork.ozlabs.org/patch/738305/

  From: Jack Morgenstein 

  Some Hypervisors detach VFs from VMs by instantly causing an FLR event
  to be generated for a VF.

  In the mlx4 case, this will cause that VF's comm channel to be disabled
  before the VM has an opportunity to invoke the VF device's "shutdown"
  method.

  For such Hypervisors, there is a race condition between the VF's
  shutdown method and its internal-error detection/reset thread.

  The internal-error detection/reset thread (which runs every 5 seconds) also
  detects a disabled comm channel. If the internal-error detection/reset
  flow wins the race, we still get delays (while that flow tries repeatedly
  to detect comm-channel recovery).

  The cited commit fixed the command timeout problem when the
  internal-error detection/reset flow loses the race.

  This commit avoids the unneeded delays when the internal-error
  detection/reset flow wins.

  Fixes: d585df1c5ccf ("net/mlx4_core: Avoid command timeouts during VF driver 
device shutdown")
  Signed-off-by: Jack Morgenstein 
  Reported-by: Simon Xiao 
  Signed-off-by: Tariq Toukan 
  ---
   drivers/net/ethernet/mellanox/mlx4/cmd.c  | 11 +++
   drivers/net/ethernet/mellanox/mlx4/main.c | 11 +++
   include/linux/mlx4/device.h   |  1 +
   3 files changed, 23 insertions(+)

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

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

[Kernel-packages] [Bug 1670518] Re: [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

[Joseph Salisbury]

I built a Xenial test kernel with all the patches from the following
bugs:

bug 1670518
 PCI: hv: Allocate physically contiguous hypercall params buffer
 PCI: hv: Make unnecessarily global IRQ masking functions static
 PCI: hv: Delete the device earlier from hbus->children for hot-remove
 PCI: hv: Fix hv_pci_remove() for hot-remove

bug 1672785 
 net/mlx4_core: Avoid delays during VF driver device shutdown

bug 1667531 
 tools: hv: Enable network manager for bonding scripts on RH
 [net-next] tools: hv: Add clean up function for Ubuntu config
 bcc5a76 tools: hv: Add a script to help bonding synthetic and VF NICs  

bug 1667527
4a9b0933bdfc PCI: hv: Use device serial number as PCI domain

bug 1667007 
d3de209 net/mlx4_core: Use cq quota in SRIOV when creating completion 
EQs

bug 1650058 
14c84da90b0d net/mlx4_en: Fix bad WQE issue
c46100f413ca net/mlx4_core: Fix racy CQ (Completion Queue) free
f4f73e2e6308 net/mlx4_core: Fix when to save some qp context flags for 
dynamic VST to VGT transitions
3c05ac20fe6e net/mlx4_core: Avoid command timeouts during VF driver 
device shutdown


The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/HyperVCombined/

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

Title:
  [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

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

Bug description:
  Looks like the rebase work missed some prerequisite patches in
  drivers/pci/host/pci-hyperv.c

  (Needed for SR-IOV in Azure on lts-xenial, HWE, and custom)

  commit 0de8ce3ee8e38cc66683438f715c79a2cc69539e
  Author: Long Li 
  Date:   Tue Nov 8 14:04:38 2016 -0800

  PCI: hv: Allocate physically contiguous hypercall params buffer

  hv_do_hypercall() assumes that we pass a segment from a physically
  contiguous buffer.  A buffer allocated on the stack may not work if
  CONFIG_VMAP_STACK=y is set.

  Use kmalloc() to allocate this buffer.

  
  commit 542ccf4551fa019a8ae9dfb7c8cd7e73a3d7e614
  Author: Tobias Klauser 
  Date:   Mon Oct 31 12:04:09 2016 +0100

  PCI: hv: Make unnecessarily global IRQ masking functions static

  Make hv_irq_mask() and hv_irq_unmask() static as they are only used in
  pci-hyperv.c

  This fixes a sparse warning.

  commit e74d2ebdda33b3bdd1826b5b92e9aa45bdf92bb3
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:19:52 2016 +

  PCI: hv: Delete the device earlier from hbus->children for hot-
  remove

  After we send a PCI_EJECTION_COMPLETE message to the host, the host will
  immediately send us a PCI_BUS_RELATIONS message with
  relations->device_count == 0, so pci_devices_present_work(), running on
  another thread, can find the being-ejected device, mark the
  hpdev->reported_missing to true, and run list_move_tail()/list_del() for
  the device -- this races hv_eject_device_work() -> list_del().

  Move the list_del() in hv_eject_device_work() to an earlier place, i.e.,
  before we send PCI_EJECTION_COMPLETE, so later the
  pci_devices_present_work() can't see the device.

  
  commit 17978524a636d007e6b929304ae3eb5ea0371019
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:18:47 2016 +

  PCI: hv: Fix hv_pci_remove() for hot-remove

  1. We don't really need such a big on-stack buffer when sending the
  teardown_packet: vmbus_sendpacket() here only uses sizeof(struct
  pci_message).

  2. In the hot-remove case (PCI_EJECT), after we send PCI_EJECTION_COMPLETE
  to the host, the host will send a RESCIND_CHANNEL message to us and the
  host won't access the per-channel ringbuffer any longer, so we needn't 
send
  PCI_RESOURCES_RELEASED/PCI_BUS_D0EXIT to the host, and we shouldn't expect
  the host's completion message of PCI_BUS_D0EXIT, which will never come.

  3. We should send PCI_BUS_D0EXIT after
  hv_send_resources_released().

  Signed-off-by: Dexuan Cui 
  Signed-off-by: Bjorn Helgaas 
  Reviewed-by: Jake Oshins 
  Acked-by: K. Y. Srinivasan 
  CC: Haiyang Zhang 
  CC: Vitaly Kuznetsov 

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

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

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

[Brad Figg]

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed 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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

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

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

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

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

[Kernel-packages] [Bug 1673222] Re: linux: 4.8.0-43.46 -proposed tracker

[Brad Figg]

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

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

Title:
  linux: 4.8.0-43.46 -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 Committed
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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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

  backports: 1673223,1673224
  derivatives: 1673228

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

[anders_c_]

Ryzen 1700
Gigabyte ab350 Gaming 3

I created a usb with 16.04.1 and it starts without problems. When i
tried to install it asked if I wanted UEFI or bios mode, UEFI failed to
install but bios worked.

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

Title:
  System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

Status in linux package in Ubuntu:
  Confirmed

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

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

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

  1. add "acpi=off" to boot params

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

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

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

  Some observed problems:

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1667920] Re: login screen freeze

[Joseph Salisbury]

I'll build an i386 version and post it.

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

Title:
  login screen freeze

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

Bug description:
  Running an up-to-date (as of Feb 25 2017) 16.04 / Unity on an old MSI
  U160 netbook.

  After a recent update to kernel 4.4.0-63 I have started getting frozen
  login screens. The touchpad and keyboard are completely dead (before I
  ever get to enter my password), and my only way out is to force
  shutdown.

  I can start GRUB on boot and go for an earlier version instead, but
  everything past 4.4.0-62 freezes in the same fashion (that's what I'm
  currently running as a temporary fix); a newer update to 4.4.0-64 has
  not fixed the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chirvasitua   1841 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 03:42:57 2017
  HibernationDevice: RESUME=UUID=5e60245a-50f2-4f9c-97b2-d68560e38218
  InstallationDate: Installed on 2015-10-18 (495 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=250be7ea-5182-43d2-b638-5c4a933b4942 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EN051IMS.100
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-N051
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEN051IMS.100:bd02/06/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-N051:pvrTobefilledbyO.E.M.:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-N051:rvrTobefilledbyO.E.M.:cvnMICRO-STARINTERNATIONALCO.,LTD:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-N051
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  BLUETOOTH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bluetooth on my ELitebook doesnt work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  muigai 1449 F pulseaudio
   /dev/snd/controlC0:  muigai 1449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Mar 16 21:30:12 2017
  InstallationDate: Installed on 2016-04-25 (324 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook Folio 1040 G2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=ba86533b-18b7-4466-bc75-b3c1d7bf8771 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M76 Ver. 01.05
  dmi.board.name: 2270
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 81.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM76Ver.01.05:bd01/19/2016:svnHewlett-Packard:pnHPEliteBookFolio1040G2:pvrA3009DD18303:rvnHewlett-Packard:rn2270:rvrKBCVersion81.29:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook Folio 1040 G2
  dmi.product.version: A3009DD18303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1673213] Re: linux: 4.4.0-69.90 -proposed tracker

[Brad Figg]

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1673216
  derivatives: 1673218,1673219,1673220,1673221
+ kernel-stable-phase-changed:Thursday, 16. March 2017 18:48 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: 1673216
  derivatives: 1673218,1673219,1673220,1673221
  kernel-stable-phase-changed:Thursday, 16. March 2017 18:48 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.4.0-69.90 -proposed tracker

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

  backports: 1673216
  derivatives: 1673218,1673219,1673220,1673221
  kernel-stable-phase-changed:Thursday, 16. March 2017 18:48 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1671760] Please test proposed package

[Brian Murray]

Hello Stefan, or anyone else affected,

Accepted xen into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/xen/4.4.2-0ubuntu0.14.04.10 in a
few hours, and then in the -proposed repository.

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

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

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

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

Title:
  Xen HVM guests running linux 4.10 fail to boot on Intel hosts

Status in linux package in Ubuntu:
  Won't Fix
Status in xen package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in xen source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in xen source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Invalid
Status in xen source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in xen source package in Zesty:
  Fix Released

Bug description:
  Starting with Linux kernel 4.10, the kernel does some sanity checking
  on the TSC_ADJUST MSR. Xen has implemented some support for that MSR
  in the hypervisor (Xen 4.3 and later) for HVM guests. But boot and
  secondary vCPUs are set up inconsistently. This causes the boot of a
  4.10 HVM guest to hang early on boot.

  This was fixed in the hypervisor by:

    commit 98297f09bd07bb63407909aae1d309d8adeb572e
    x86/hvm: do not set msr_tsc_adjust on hvm_set_guest_tsc_fixed

  That fix would be contained in 4.6.5 and 4.7.2 and would be in 4.8.1
  (not released, yet) which mean that Ubuntu 14.04/16.04/16.10 and 17.04
  currently are affected.

  ---

  SRU Justification:

  Impact: Without the TSC_ADJUST MSR fix, 4.10 and later kernels will
  get stuck at boot when running as (PV)HVM guests on Xen 4.3 and later.

  Fix: Above fix either individually applied or as part of Xen stable
  stream (for Xen 4.7.x and 4.6.x) resolves the issue.

  Testcase:
  - Requires Intel based host which supports the TSC_ADJUST MSR
  - Configured as Xen host
  - HVM guest running Zesty/17.04
  - Stuck at boot before, normal booting OS after

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

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

[Kernel-packages] [Bug 1673498] Re: move aufs.ko from -extra to linux-image package

[Kamal Mostafa]

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

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

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

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

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

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

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

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
   Status: In Progress

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

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

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

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

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

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

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

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

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

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

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

Title:
  move aufs.ko from -extra to linux-image package

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in aa-series:
  New

Bug description:
  Docker is ordinarily configured to use aufs, but the aufs kernel
  module is only available after installing the linux-image-extra
  package.

  Please promote aufs.ko from the linux-image-extra package to the main
  linux-image package for all supported Ubuntu kernels and derivatives,
  so as to remove Docker's dependence on linux-image-extra.

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

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

[Kernel-packages] [Bug 1673565] [NEW] BLUETOOTH

[David Muigai]

Public bug reported:

Bluetooth on my ELitebook doesnt work

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  muigai 1449 F pulseaudio
 /dev/snd/controlC0:  muigai 1449 F pulseaudio
CurrentDesktop: X-Cinnamon
Date: Thu Mar 16 21:30:12 2017
InstallationDate: Installed on 2016-04-25 (324 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP EliteBook Folio 1040 G2
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=ba86533b-18b7-4466-bc75-b3c1d7bf8771 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-66-generic N/A
 linux-backports-modules-4.4.0-66-generic  N/A
 linux-firmware1.157.8
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/19/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M76 Ver. 01.05
dmi.board.name: 2270
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 81.29
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM76Ver.01.05:bd01/19/2016:svnHewlett-Packard:pnHPEliteBookFolio1040G2:pvrA3009DD18303:rvnHewlett-Packard:rn2270:rvrKBCVersion81.29:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook Folio 1040 G2
dmi.product.version: A3009DD18303
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug xenial

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

Title:
  BLUETOOTH

Status in linux package in Ubuntu:
  New

Bug description:
  Bluetooth on my ELitebook doesnt work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  muigai 1449 F pulseaudio
   /dev/snd/controlC0:  muigai 1449 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Mar 16 21:30:12 2017
  InstallationDate: Installed on 2016-04-25 (324 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook Folio 1040 G2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=ba86533b-18b7-4466-bc75-b3c1d7bf8771 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-66-generic N/A
   linux-backports-modules-4.4.0-66-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M76 Ver. 01.05
  dmi.board.name: 2270
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 81.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM76Ver.01.05:bd01/19/2016:svnHewlett-Packard:pnHPEliteBookFolio1040G2:pvrA3009DD18303:rvnHewlett-Packard:rn2270:rvrKBCVersion81.29:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook Folio 1040 G2
  dmi.product.version: A3009DD18303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1667920] Re: login screen freeze

[Alexandru Chirvasitu]

I don't think I'll be able to test that: the folder you link to seems to
only have the amd64 version; I'm on i386..

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

Title:
  login screen freeze

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

Bug description:
  Running an up-to-date (as of Feb 25 2017) 16.04 / Unity on an old MSI
  U160 netbook.

  After a recent update to kernel 4.4.0-63 I have started getting frozen
  login screens. The touchpad and keyboard are completely dead (before I
  ever get to enter my password), and my only way out is to force
  shutdown.

  I can start GRUB on boot and go for an earlier version instead, but
  everything past 4.4.0-62 freezes in the same fashion (that's what I'm
  currently running as a temporary fix); a newer update to 4.4.0-64 has
  not fixed the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chirvasitua   1841 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 03:42:57 2017
  HibernationDevice: RESUME=UUID=5e60245a-50f2-4f9c-97b2-d68560e38218
  InstallationDate: Installed on 2015-10-18 (495 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=250be7ea-5182-43d2-b638-5c4a933b4942 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EN051IMS.100
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-N051
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEN051IMS.100:bd02/06/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-N051:pvrTobefilledbyO.E.M.:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-N051:rvrTobefilledbyO.E.M.:cvnMICRO-STARINTERNATIONALCO.,LTD:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-N051
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Kernel-packages] [Bug 1671760] Please test proposed package

[Brian Murray]

Hello Stefan, or anyone else affected,

Accepted xen into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/xen/4.6.5-0ubuntu1 in
a few hours, and then in the -proposed repository.

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

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

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

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

Title:
  Xen HVM guests running linux 4.10 fail to boot on Intel hosts

Status in linux package in Ubuntu:
  Won't Fix
Status in xen package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in xen source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in xen source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Invalid
Status in xen source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in xen source package in Zesty:
  Fix Released

Bug description:
  Starting with Linux kernel 4.10, the kernel does some sanity checking
  on the TSC_ADJUST MSR. Xen has implemented some support for that MSR
  in the hypervisor (Xen 4.3 and later) for HVM guests. But boot and
  secondary vCPUs are set up inconsistently. This causes the boot of a
  4.10 HVM guest to hang early on boot.

  This was fixed in the hypervisor by:

    commit 98297f09bd07bb63407909aae1d309d8adeb572e
    x86/hvm: do not set msr_tsc_adjust on hvm_set_guest_tsc_fixed

  That fix would be contained in 4.6.5 and 4.7.2 and would be in 4.8.1
  (not released, yet) which mean that Ubuntu 14.04/16.04/16.10 and 17.04
  currently are affected.

  ---

  SRU Justification:

  Impact: Without the TSC_ADJUST MSR fix, 4.10 and later kernels will
  get stuck at boot when running as (PV)HVM guests on Xen 4.3 and later.

  Fix: Above fix either individually applied or as part of Xen stable
  stream (for Xen 4.7.x and 4.6.x) resolves the issue.

  Testcase:
  - Requires Intel based host which supports the TSC_ADJUST MSR
  - Configured as Xen host
  - HVM guest running Zesty/17.04
  - Stuck at boot before, normal booting OS after

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

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

[Kernel-packages] [Bug 1501345] Re: linux-image-3.13.0-65-generic breaks serial communication

[Jon Watte]

This bug is back in kernel 4.8 series. I'm seeing it in pyserial, using
the Cura 2.4 application, on current Ubuntu 16.04 LTS install.


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

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

Title:
  linux-image-3.13.0-65-generic breaks serial communication

Status in linux-lts-trusty package in Ubuntu:
  Fix Released
Status in linux-lts-xenial package in Ubuntu:
  New

Bug description:
  Today after updating to the linux-image-3.13.0-65-generic 3.13.0-65
  Kernel on Lubuntu 14.04.3 LTS two different programs that rely on
  PySerial quit working. miniterm.py and my ROS (Robot Operating System)
  based Python node quit working.

  When rebooted and selected 3.13.0-63-generic via GRUB everything
  worked again.

  Here are the steps to create the issue with miniterm.py, note that you
  need something connected via a USB to Serial adapter for this to work.
  I am working with a Parallax Activity Board, but an Arduino should
  also exhibit the same behavior.

  sudo apt install linux-image-3.13.0-65-generic
  sudo apt install linux-image-extra-3.13.0-65-generic
  reboot

   $ miniterm.py /dev/ttyUSB0 115200
  --- Miniterm on /dev/ttyUSB0: 115200,8,N,1 ---
  --- Quit: Ctrl+]  |  Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---

  --- exit ---
  Exception in thread Thread-1:
  Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
  self.run()
File "/usr/lib/python2.7/threading.py", line 763, in run
  self.__target(*self.__args, **self.__kwargs)
File "/usr/bin/miniterm.py", line 220, in reader
  data = character(self.serial.read(1))
File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 460, in 
read
  raise SerialException('device reports readiness to read but returned no 
data (device disconnected?)')
  SerialException: device reports readiness to read but returned no data 
(device disconnected?)

  Reverting to the 3.13.0-63 kernel allows miniterm.py and other Python
  Serial based programs to work normally.

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

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

[Kernel-packages] [Bug 1663975] Re: XHCI errors causes dock USB and network adapter dropouts

[Kaz Wolfe]

Just for the sake of completeness, yet another error log:
http://pastebin.com/z8U9usDY

4.8.0-41-generic #44~16.04.1-Ubuntu, HWE because reasons. Kernel is
tainted (NVIDIA, VirtualBox), but this issue seems to exist anyways.

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

Title:
  XHCI errors causes dock USB and network adapter dropouts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Machine: Dell XPS 15 (9560) - released 2017 January
  Install: disk completely erased
   Ubuntu 16.04.1 installed over wireless with:
 - download updates while installing ubuntu
 - install third-party hardware
 - full disk crypto+luks
   Note 1: Installation process did not realize there exists a GTX 1050
   so we are solely using Intel integrated graphics.
   Note 2: Installation done not on Dell TB16 Dock to isolate wireless
   problems alone first.
  First Boot: update/upgrade/dist-upgrade'd after first boot and rebooted

  


  After testing wireless problems and being able to reproduce them,
  machine was rebooted to the login screen, and then plugged into a Dell
  TB16 dock.

  1. Turn down wireless networking.
  2. Turn up wired networking.
  3. Browse things until this happens, after which the wired interface no 
longer works and can sometimes be successfully `down/up`ed but at other times 
locks up and requires a reboot:

  [  598.238303] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.238307] xhci_hcd :0e:00.0: Looking for event-dma 000855403010 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.238634] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.238639] xhci_hcd :0e:00.0: Looking for event-dma 000855403020 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239248] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239253] xhci_hcd :0e:00.0: Looking for event-dma 000855403030 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239571] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239576] xhci_hcd :0e:00.0: Looking for event-dma 000855403040 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239792] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239794] xhci_hcd :0e:00.0: Looking for event-dma 000855403050 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240186] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240191] xhci_hcd :0e:00.0: Looking for event-dma 000855403060 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240326] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240328] xhci_hcd :0e:00.0: Looking for event-dma 000855403070 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240698] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240703] xhci_hcd :0e:00.0: Looking for event-dma 000855403080 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  605.601884] [ cut here ]
  [  605.601890] WARNING: CPU: 1 PID: 0 at 
/build/linux-W6HB68/linux-4.4.0/net/sched/sch_generic.c:306 
dev_watchdog+0x237/0x240()
  [  605.601892] NETDEV WATCHDOG: enxd481d70e6a39 (r8152): transmit queue 0 
timed out
  [  605.601892] Modules linked in: hid_logitech_hidpp snd_usb_audio 
snd_usbmidi_lib hid_generic hid_logitech_dj cdc_ether usbnet r8152 mii ctr ccm 
arc4 rfcomm bnep nls_iso8859_1 i2c_designware_platform i2c_designware_core 
dell_wmi dcdbas ath10k_pci ath10k_core ath snd_hda_codec_hdmi mac80211 dell_led 
snd_hda_codec_realtek snd_hda_codec_generic cfg80211 rtsx_pci_ms memstick 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm x86_pkg_temp_thermal 
coretemp snd_seq_midi kvm_intel snd_seq_midi_event snd_rawmidi kvm snd_seq 
uvcvideo irqbypass snd_seq_device snd_timer videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

[Kaz Wolfe]

Seems related to Bug #1663975. Same problem, I'd think...

Also, just for the sake of completeness, yet another error log:
http://pastebin.com/z8U9usDY

4.8.0-41-generic #44~16.04.1-Ubuntu, HWE because reasons. Kernel is
tainted (NVIDIA, VirtualBox), but this issue seems to exist anyways.

Posted same comment over on the other bug report, sorry for any spam
that may report.

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

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New
Status in linux package in Fedora:
  New

Bug description:
  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9030 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9040 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9050 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9060 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9070 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:39 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9080 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx timeout
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:06 ubuntu kernel: r8152 4-1.2:1.0 enx204747f8f471: Tx status -2
  Feb 24 16:43:09 ubuntu kernel: usb 4-1.2: reset 

[Kernel-packages] [Bug 1671063] Re: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

[Brian Murray]

Strangely this didn't get marked Fix Released by the janitor.

ltt-control (2.9.3-1ubuntu1) zesty; urgency=medium

  * Fix lttng list --kernel --syscall failure (LP: #1671063)

 -- Colin Ian King   Tue, 14 Mar 2017 13:39:11
+

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

** Tags added: verification-needed

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

Title:
  ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

Status in ltt-control package in Ubuntu:
  Fix Released
Status in ltt-control source package in Yakkety:
  Fix Committed

Bug description:
  == SRU Request [Xenial, Yaketty + Zesty ] ==

  Without this minor fix, the lttng tool receives a "Not enough memory" error
  when in fact this is not the case.

  == How to reproduce ==

  lttng list --kernel --sysall

  produces:
  Error: Unable to list system calls: Not enough memory
  Error: Command error

  With the fix, this does not occur.

  == Fix ==

  https://lists.lttng.org/pipermail/lttng-dev/2017-March/026959.html

  == Regression Potential ==

  Minimal, low risk.

  

  Two test cases failed on this arch:
  == lttng smoke test list kernel events ==
  PASSED (lttng list --kernel)
  Error: Unable to list system calls: Not enough memory
  Error: Command error
  FAILED (lttng list --kernel --syscall)
  FAILED (lttng list --kernel --syscall more output expected)

  == lttng smoke test trace open/close system calls ==
  ...
  FAILED (did not trace any open system calls)

  Please find attachment for complete log.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-40-generic 4.8.0-40.43
  ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
  Uname: Linux 4.8.0-40-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  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'
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Mar  8 06:39:24 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug 
udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-40-generic N/A
   linux-backports-modules-4.8.0-40-generic  N/A
   linux-firmware1.161.1
  RfKill: Error: [Errno 2] No such file or directory: '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/ltt-control/+bug/1671063/+subscriptions

-- 
Mailing list: https://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 1673535] [NEW] drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS

[Michael Hohnbaum]

Leann,

This looks like one for the Kernel team.

Michael


On 03/16/2017 10:09 AM, Launchpad Bug Tracker wrote:
> bugproxy (bugproxy) has assigned this bug to you for Ubuntu:
>
> Canonical,
>
> Please add patch into 17.04:
>
> commit 3856081eede297b617560b85e948cfb00bb395ec
>
>
> drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS
> 
> The current POST code for the AST2300/2400 family doesn't work properly
> if the chip hasn't been initialized previously by either the BMC own FW
> or the VBIOS. This fixes it.
>
> ** Affects: ubuntu
>  Importance: Undecided
>  Assignee: Taco Screen team (taco-screen-team)
>  Status: New
>
>
> ** Tags: architecture-ppc64le bugnameltc-152622 severity-high 
> targetmilestone-inin---

-- 
Michael Hohnbaum
OIL Program Manager
Power (ppc64el) Development Project Manager
Canonical, Ltd.

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

Title:
  drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS

Status in linux package in Ubuntu:
  New

Bug description:
  Canonical,

  Please add patch into 17.04:

  commit 3856081eede297b617560b85e948cfb00bb395ec

  
  drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS
  
  The current POST code for the AST2300/2400 family doesn't work properly
  if the chip hasn't been initialized previously by either the BMC own FW
  or the VBIOS. This fixes it.

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

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

[Kernel-packages] [Bug 1671063] Re: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

[Brian Murray]

Oh, it didn't get changed because this has a linux not ltt-control bug
task.

** Package changed: linux (Ubuntu) => ltt-control (Ubuntu)

** Also affects: ltt-control (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: ltt-control (Ubuntu Yakkety)
   Status: New => 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/1671063

Title:
  ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

Status in ltt-control package in Ubuntu:
  Fix Released
Status in ltt-control source package in Yakkety:
  Fix Committed

Bug description:
  == SRU Request [Xenial, Yaketty + Zesty ] ==

  Without this minor fix, the lttng tool receives a "Not enough memory" error
  when in fact this is not the case.

  == How to reproduce ==

  lttng list --kernel --sysall

  produces:
  Error: Unable to list system calls: Not enough memory
  Error: Command error

  With the fix, this does not occur.

  == Fix ==

  https://lists.lttng.org/pipermail/lttng-dev/2017-March/026959.html

  == Regression Potential ==

  Minimal, low risk.

  

  Two test cases failed on this arch:
  == lttng smoke test list kernel events ==
  PASSED (lttng list --kernel)
  Error: Unable to list system calls: Not enough memory
  Error: Command error
  FAILED (lttng list --kernel --syscall)
  FAILED (lttng list --kernel --syscall more output expected)

  == lttng smoke test trace open/close system calls ==
  ...
  FAILED (did not trace any open system calls)

  Please find attachment for complete log.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-40-generic 4.8.0-40.43
  ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
  Uname: Linux 4.8.0-40-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  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'
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Mar  8 06:39:24 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug 
udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-40-generic N/A
   linux-backports-modules-4.8.0-40-generic  N/A
   linux-firmware1.161.1
  RfKill: Error: [Errno 2] No such file or directory: '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/ltt-control/+bug/1671063/+subscriptions

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

[Kernel-packages] [Bug 1671063] Please test proposed package

[Brian Murray]

Hello Po-Hsu, or anyone else affected,

Accepted ltt-control into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ltt-
control/2.8.1-1ubuntu1 in a few hours, and then in the -proposed
repository.

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

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

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

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

Title:
  ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)

Status in ltt-control package in Ubuntu:
  Fix Released
Status in ltt-control source package in Yakkety:
  Fix Committed

Bug description:
  == SRU Request [Xenial, Yaketty + Zesty ] ==

  Without this minor fix, the lttng tool receives a "Not enough memory" error
  when in fact this is not the case.

  == How to reproduce ==

  lttng list --kernel --sysall

  produces:
  Error: Unable to list system calls: Not enough memory
  Error: Command error

  With the fix, this does not occur.

  == Fix ==

  https://lists.lttng.org/pipermail/lttng-dev/2017-March/026959.html

  == Regression Potential ==

  Minimal, low risk.

  

  Two test cases failed on this arch:
  == lttng smoke test list kernel events ==
  PASSED (lttng list --kernel)
  Error: Unable to list system calls: Not enough memory
  Error: Command error
  FAILED (lttng list --kernel --syscall)
  FAILED (lttng list --kernel --syscall more output expected)

  == lttng smoke test trace open/close system calls ==
  ...
  FAILED (did not trace any open system calls)

  Please find attachment for complete log.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-40-generic 4.8.0-40.43
  ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
  Uname: Linux 4.8.0-40-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  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'
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Mar  8 06:39:24 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug 
udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-40-generic N/A
   linux-backports-modules-4.8.0-40-generic  N/A
   linux-firmware1.161.1
  RfKill: Error: [Errno 2] No such file or directory: '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/ltt-control/+bug/1671063/+subscriptions

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

[Kernel-packages] [Bug 1670508] Re: CIFS: Enable encryption for SMB3

[Joseph Salisbury]

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

** Tags added: kernel-da-key kernel-hyper-v

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

Title:
  CIFS: Enable encryption for SMB3

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  There has been work upstream to enable encryption support for SMB3
  connections. This is a particularly valuable (and commonly requested)
  feature with the Azure Files service as encryption is required to
  connect to an Azure Files storage share from on-prem or from a
  different Azure region.

  The relevant commits are as follows:

  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

  CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e

  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb

  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e

  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

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

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

[Kernel-packages] [Bug 1673538] Re: Xenial update to v4.4.53 stable release

[Tim Gardner]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.4.63 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The v4.4.63 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v4.4.63 stable release shall be
+ applied:
  
-The following patches from the v4.4.63 stable release shall be
- applied:
+ samples: move mic/mpssd example code from Documentation
+ MIPS: Fix special case in 64 bit IP checksumming.
+ MIPS: BCM47XX: Fix button inversion for Asus WL-500W
+ MIPS: OCTEON: Fix copy_from_user fault handling for large buffers
+ MIPS: Lantiq: Keep ethernet enabled during boot
+ MIPS: Clear ISA bit correctly in get_frame_info()
+ MIPS: Prevent unaligned accesses during stack unwinding
+ MIPS: Fix get_frame_info() handling of microMIPS function size
+ MIPS: Fix is_jump_ins() handling of 16b microMIPS instructions
+ MIPS: Calculate microMIPS ra properly when unwinding the stack
+ MIPS: Handle microMIPS jumps in the same way as MIPS32/MIPS64 jumps
+ am437x-vpfe: always assign bpp variable
+ uvcvideo: Fix a wrong macro
+ media: fix dm1105.c build error
+ ARM: at91: define LPDDR types
+ ARM: dts: at91: Enable DMA on sama5d4_xplained console
+ ARM: dts: at91: Enable DMA on sama5d2_xplained console
+ ALSA: hda/realtek - Cannot adjust speaker's volume on a Dell AIO
+ ALSA: hda - fix Lewisburg audio issue
+ ALSA: timer: Reject user params with too small ticks
+ ALSA: ctxfi: Fallback DMA mask to 32bit
+ ALSA: seq: Fix link corruption by event error handling
+ ALSA: hda - Add subwoofer support for Dell Inspiron 17 7000 Gaming
+ ALSA: hda - Fix micmute hotkey problem for a lenovo AIO machine
+ staging: rtl: fix possible NULL pointer dereference
+ regulator: Fix regulator_summary for deviceless consumers
+ iommu/vt-d: Fix some macros that are incorrectly specified in intel-iommu
+ iommu/vt-d: Tylersburg isoch identity map check is done too late.
+ mm/page_alloc: fix nodes for reclaim in fast path
+ mm: vmpressure: fix sending wrong events on underflow
+ mm: do not access page->mapping directly on page_endio
+ ipc/shm: Fix shmat mmap nil-page protection
+ dm cache: fix corruption seen when using cache > 2TB
+ dm stats: fix a leaked s->histogram_boundaries array
+ Revert "scsi: storvsc: properly set residual data length on errors"
+ scsi: storvsc: properly set residual data length on errors
+ scsi: aacraid: Reorder Adapter status check
+ scsi: use 'scsi_device_from_queue()' for scsi_dh
+ sd: get disk reference in sd_check_events()
+ Fix: Disable sys_membarrier when nohz_full is enabled
+ jbd2: don't leak modified metadata buffers on an aborted journal
+ block/loop: fix race between I/O and set_status
+ loop: fix LO_FLAGS_PARTSCAN hang
+ ext4: Include forgotten start block on fallocate insert range
+ ext4: do not polute the extents cache while shifting extents
+ ext4: trim allocation requests to group size
+ ext4: fix data corruption in data=journal mode
+ ext4: fix inline data error paths
+ ext4: preserve the needs_recovery flag when the journal is aborted
+ ext4: return EROFS if device is r/o and journal replay is needed
+ samples/seccomp: fix 64-bit comparison macros
+ target: Obtain se_node_acl->acl_kref during get_initiator_node_acl
+ target: Fix multi-session dynamic se_node_acl double free OOPs
+ ath5k: drop bogus warning on drv_set_key with unsupported cipher
+ ath9k: fix race condition in enabling/disabling IRQs
+ ath9k: use correct OTP register offsets for the AR9340 and AR9550
+ crypto: testmgr - Pad aes_ccm_enc_tv_template vector
+ fuse: add missing FR_FORCE
+ arm/arm64: KVM: Enforce unconditional flush to PoC when mapping to stage-2
+ iio: pressure: mpl115: do not rely on structure field ordering
+ iio: pressure: mpl3115: do not rely on structure field ordering
+ can: usb_8dev: Fix memory leak of priv->cmd_msg_buffer
+ w1: don't leak refcount on slave attach failure in w1_attach_slave_device()
+ w1: ds2490: USB transfer buffers need to be DMAable
+ usb: musb: da8xx: Remove CPPI 3.0 quirk and methods
+ usb: host: 

[Kernel-packages] [Bug 1670518] Re: [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

[Joseph Salisbury]

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

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

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

Title:
  [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

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

Bug description:
  Looks like the rebase work missed some prerequisite patches in
  drivers/pci/host/pci-hyperv.c

  (Needed for SR-IOV in Azure on lts-xenial, HWE, and custom)

  commit 0de8ce3ee8e38cc66683438f715c79a2cc69539e
  Author: Long Li 
  Date:   Tue Nov 8 14:04:38 2016 -0800

  PCI: hv: Allocate physically contiguous hypercall params buffer

  hv_do_hypercall() assumes that we pass a segment from a physically
  contiguous buffer.  A buffer allocated on the stack may not work if
  CONFIG_VMAP_STACK=y is set.

  Use kmalloc() to allocate this buffer.

  
  commit 542ccf4551fa019a8ae9dfb7c8cd7e73a3d7e614
  Author: Tobias Klauser 
  Date:   Mon Oct 31 12:04:09 2016 +0100

  PCI: hv: Make unnecessarily global IRQ masking functions static

  Make hv_irq_mask() and hv_irq_unmask() static as they are only used in
  pci-hyperv.c

  This fixes a sparse warning.

  commit e74d2ebdda33b3bdd1826b5b92e9aa45bdf92bb3
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:19:52 2016 +

  PCI: hv: Delete the device earlier from hbus->children for hot-
  remove

  After we send a PCI_EJECTION_COMPLETE message to the host, the host will
  immediately send us a PCI_BUS_RELATIONS message with
  relations->device_count == 0, so pci_devices_present_work(), running on
  another thread, can find the being-ejected device, mark the
  hpdev->reported_missing to true, and run list_move_tail()/list_del() for
  the device -- this races hv_eject_device_work() -> list_del().

  Move the list_del() in hv_eject_device_work() to an earlier place, i.e.,
  before we send PCI_EJECTION_COMPLETE, so later the
  pci_devices_present_work() can't see the device.

  
  commit 17978524a636d007e6b929304ae3eb5ea0371019
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:18:47 2016 +

  PCI: hv: Fix hv_pci_remove() for hot-remove

  1. We don't really need such a big on-stack buffer when sending the
  teardown_packet: vmbus_sendpacket() here only uses sizeof(struct
  pci_message).

  2. In the hot-remove case (PCI_EJECT), after we send PCI_EJECTION_COMPLETE
  to the host, the host will send a RESCIND_CHANNEL message to us and the
  host won't access the per-channel ringbuffer any longer, so we needn't 
send
  PCI_RESOURCES_RELEASED/PCI_BUS_D0EXIT to the host, and we shouldn't expect
  the host's completion message of PCI_BUS_D0EXIT, which will never come.

  3. We should send PCI_BUS_D0EXIT after
  hv_send_resources_released().

  Signed-off-by: Dexuan Cui 
  Signed-off-by: Bjorn Helgaas 
  Reviewed-by: Jake Oshins 
  Acked-by: K. Y. Srinivasan 
  CC: Haiyang Zhang 
  CC: Vitaly Kuznetsov 

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

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

[Kernel-packages] [Bug 1673541] Re: Xenial update to v4.4.54 stable release

[Tim Gardner]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.4.54 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The v4.4.54 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v4.4.54 stable release shall be
+ applied:
  
-The following patches from the v4.4.54 stable release shall be
- applied:
+ serial: 8250_pci: Add MKS Tenta SCOM-0800 and SCOM-0801 cards
+ KVM: s390: Disable dirty log retrieval for UCONTROL guests
+ KVM: VMX: use correct vmcs_read/write for guest segment selector/base
+ Bluetooth: Add another AR3012 04ca:3018 device
+ s390/qdio: clear DSCI prior to scanning multiple input queues
+ s390/dcssblk: fix device size calculation in dcssblk_direct_access()
+ s390: TASK_SIZE for kernel threads
+ s390: make setup_randomness work
+ s390: use correct input data address for setup_randomness
+ net: mvpp2: fix DMA address calculation in mvpp2_txq_inc_put()
+ mnt: Tuck mounts under others instead of creating shadow/side mounts.
+ IB/ipoib: Fix deadlock between rmmod and set_mode
+ IB/IPoIB: Add destination address when re-queue packet
+ IB/srp: Avoid that duplicate responses trigger a kernel bug
+ IB/srp: Fix race conditions related to task management
+ ktest: Fix child exit code processing
+ ceph: remove req from unsafe list when unregistering it
+ target: Fix NULL dereference during LUN lookup + active I/O shutdown
+ nlm: Ensure callback code also checks that the files match
+ pwm: pca9685: Fix period change with same duty cycle
+ xtensa: move parse_tag_fdt out of #ifdef CONFIG_BLK_DEV_INITRD
+ mac80211: flush delayed work when entering suspend
+ drm/amdgpu: add more cases to DCE11 possible crtc mask setup
+ drm/ast: Fix test for VGA enabled
+ drm/ast: Call open_key before enable_mmio in POST code
+ drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS
+ drm/edid: Add EDID_QUIRK_FORCE_8BPC quirk for Rotel RSX-1058
+ drm/ttm: Make sure BOs being swapped out are cacheable
+ drm/atomic: fix an error code in mode_fixup()
+ fakelb: fix schedule while atomic
+ drm/i915/dsi: Do not clear DPOUNIT_CLOCK_GATE_DISABLE from 
vlv_init_display_clock_gating
+ libceph: use BUG() instead of BUG_ON(1)
+ fat: fix using uninitialized fields of fat_inode/fsinfo_inode
+ drivers: hv: Turn off write permission on the hypercall page
+ Linux 4.4.54

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

Title:
  Xenial update to v4.4.54 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

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

  serial: 8250_pci: Add MKS Tenta SCOM-0800 and SCOM-0801 cards
  KVM: s390: Disable dirty log retrieval for UCONTROL guests
  KVM: VMX: use correct vmcs_read/write for guest segment selector/base
  Bluetooth: Add another AR3012 04ca:3018 device
  s390/qdio: clear DSCI prior to scanning multiple input queues
  s390/dcssblk: fix device size calculation in dcssblk_direct_access()
  s390: TASK_SIZE for kernel threads
  s390: make setup_randomness work
  s390: use correct input data address for setup_randomness
  net: mvpp2: fix DMA address calculation in mvpp2_txq_inc_put()
  mnt: Tuck mounts under others instead of creating shadow/side mounts.
  IB/ipoib: Fix deadlock between rmmod and set_mode
  IB/IPoIB: Add destination address when 

[Kernel-packages] [Bug 1671760] Re: Xen HVM guests running linux 4.10 fail to boot on Intel hosts

[Brian Murray]

Hello Stefan, or anyone else affected,

Accepted xen into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/xen/4.7.2-0ubuntu1 in
a few hours, and then in the -proposed repository.

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

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

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

** Tags added: verification-needed

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

Title:
  Xen HVM guests running linux 4.10 fail to boot on Intel hosts

Status in linux package in Ubuntu:
  Won't Fix
Status in xen package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Invalid
Status in xen source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Invalid
Status in xen source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Invalid
Status in xen source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in xen source package in Zesty:
  Fix Released

Bug description:
  Starting with Linux kernel 4.10, the kernel does some sanity checking
  on the TSC_ADJUST MSR. Xen has implemented some support for that MSR
  in the hypervisor (Xen 4.3 and later) for HVM guests. But boot and
  secondary vCPUs are set up inconsistently. This causes the boot of a
  4.10 HVM guest to hang early on boot.

  This was fixed in the hypervisor by:

    commit 98297f09bd07bb63407909aae1d309d8adeb572e
    x86/hvm: do not set msr_tsc_adjust on hvm_set_guest_tsc_fixed

  That fix would be contained in 4.6.5 and 4.7.2 and would be in 4.8.1
  (not released, yet) which mean that Ubuntu 14.04/16.04/16.10 and 17.04
  currently are affected.

  ---

  SRU Justification:

  Impact: Without the TSC_ADJUST MSR fix, 4.10 and later kernels will
  get stuck at boot when running as (PV)HVM guests on Xen 4.3 and later.

  Fix: Above fix either individually applied or as part of Xen stable
  stream (for Xen 4.7.x and 4.6.x) resolves the issue.

  Testcase:
  - Requires Intel based host which supports the TSC_ADJUST MSR
  - Configured as Xen host
  - HVM guest running Zesty/17.04
  - Stuck at boot before, normal booting OS after

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

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

[Kernel-packages] [Bug 1673541] [NEW] Xenial update to v4.4.54 stable release

[Tim Gardner]

Public bug reported:


SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

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

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

Title:
  Xenial update to v4.4.54 stable release

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

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

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

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

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

[Kernel-packages] [Bug 1673538] [NEW] Xenial update to v4.4.53 stable release

[Tim Gardner]

Public bug reported:


SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

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

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

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


** Tags: kernel-stable-tracking-bug

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

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

** Summary changed:

- Xenial update to v4.4.63 stable release
+ Xenial update to v4.4.53 stable release

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

Title:
  Xenial update to v4.4.53 stable release

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

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

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

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

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

[Kernel-packages] [Bug 1673443] Re: Packaging: Provide etcd package to provide distributed key value store on POWER

[Tim Gardner]

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

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

Title:
  Packaging: Provide etcd package to provide distributed key value store
  on POWER

Status in etcd package in Ubuntu:
  New

Bug description:
  As package is now available in Debian SID at level 3.1.2+dfsg-1 
  https://packages.debian.org/search?searchon=sourcenames=etcd
  can we expect an upgrade on Ubuntu ?

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

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

[Kernel-packages] [Bug 1673535] [NEW] drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS

[bugproxy]

Public bug reported:

Canonical,

Please add patch into 17.04:

commit 3856081eede297b617560b85e948cfb00bb395ec


drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS

The current POST code for the AST2300/2400 family doesn't work properly
if the chip hasn't been initialized previously by either the BMC own FW
or the VBIOS. This fixes it.

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


** Tags: architecture-ppc64le bugnameltc-152622 severity-high 
targetmilestone-inin---

** Tags added: architecture-ppc64le bugnameltc-152622 severity-high
targetmilestone-inin---

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

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

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

Title:
  drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS

Status in linux package in Ubuntu:
  New

Bug description:
  Canonical,

  Please add patch into 17.04:

  commit 3856081eede297b617560b85e948cfb00bb395ec

  
  drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS
  
  The current POST code for the AST2300/2400 family doesn't work properly
  if the chip hasn't been initialized previously by either the BMC own FW
  or the VBIOS. This fixes it.

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

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

[Kernel-packages] [Bug 1673535] [NEW] drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Canonical,

Please add patch into 17.04:

commit 3856081eede297b617560b85e948cfb00bb395ec


drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS

The current POST code for the AST2300/2400 family doesn't work properly
if the chip hasn't been initialized previously by either the BMC own FW
or the VBIOS. This fixes it.

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


** Tags: architecture-ppc64le bugnameltc-152622 severity-high 
targetmilestone-inin---
-- 
drm/ast: Fix AST2400 POST failure without BMC FW or VBIOS
https://bugs.launchpad.net/bugs/1673535
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1666209] Re: PPC new 4.4.0-63-powerpc63-smp kernel kills networking

[Kirill Nersesyan]

Hard to say at the moment. The machine is on 24/7 and is serving a
rather large company. I might be able to try to shut it down for
sometime late Friday. But can't promise anything. If I do should expect
the mainline kernel NOT to change the interfaces names ?

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

Title:
  PPC new 4.4.0-63-powerpc63-smp kernel kills networking

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

Bug description:
  After upgrading to a new kernel (4.4.0-63-powerpc64-smp) completely
  lost ethernet. Looks like the kernel doesn't load a module for my
  interface (driver r8169). Rolling back to previous kernel version
  fixes networking.

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

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

[Kernel-packages] [Bug 1670508] Re: CIFS: Enable encryption for SMB3

[Joshua R. Poulson]

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

Title:
  CIFS: Enable encryption for SMB3

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  There has been work upstream to enable encryption support for SMB3
  connections. This is a particularly valuable (and commonly requested)
  feature with the Azure Files service as encryption is required to
  connect to an Azure Files storage share from on-prem or from a
  different Azure region.

  The relevant commits are as follows:

  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

  CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e

  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb

  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e

  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

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

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

[Kernel-packages] [Bug 1670508] Re: CIFS: Enable encryption for SMB3

[Launchpad Bug Tracker]

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

** 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 linux in Ubuntu.
https://bugs.launchpad.net/bugs/1670508

Title:
  CIFS: Enable encryption for SMB3

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  There has been work upstream to enable encryption support for SMB3
  connections. This is a particularly valuable (and commonly requested)
  feature with the Azure Files service as encryption is required to
  connect to an Azure Files storage share from on-prem or from a
  different Azure region.

  The relevant commits are as follows:

  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

  CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e

  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb

  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e

  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

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

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

[Kernel-packages] [Bug 1670508] Re: CIFS: Enable encryption for SMB3

[Brad Figg]

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

Title:
  CIFS: Enable encryption for SMB3

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  There has been work upstream to enable encryption support for SMB3
  connections. This is a particularly valuable (and commonly requested)
  feature with the Azure Files service as encryption is required to
  connect to an Azure Files storage share from on-prem or from a
  different Azure region.

  The relevant commits are as follows:

  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

  CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e

  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb

  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e

  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

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

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

[Kernel-packages] [Bug 1670508] Re: CIFS: Enable encryption for SMB3

[Joseph Salisbury]

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

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

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

Title:
  CIFS: Enable encryption for SMB3

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  There has been work upstream to enable encryption support for SMB3
  connections. This is a particularly valuable (and commonly requested)
  feature with the Azure Files service as encryption is required to
  connect to an Azure Files storage share from on-prem or from a
  different Azure region.

  The relevant commits are as follows:

  CIFS: Fix possible use after free in demultiplex thread
  Commit 61cfac6f267dabcf2740a7ec8a0295833b28b5f5

  CIFS: Allow to switch on encryption with seal mount option
  Commit ae6f8dd4d0c87bfb72da9d9b56342adf53e69c31

  CIFS: Add capability to decrypt big read responses
  Commit c42a6abe3012832a68a371dabe17c2ced97e62ad

  CIFS: Decrypt and process small encrypted packets
  Commit 4326ed2f6a16ae9d33e4209b540dc9a371aba840

  CIFS: Add copy into pages callback for a read operation
  Commit d70b9104b1ca586f73aaf59426756cec3325a40e

  CIFS: Add mid handle callback
  Commit 9b7c18a2d4b798963ea80f6769701dcc4c24b55e

  CIFS: Add transform header handling callbacks
  Commit 9bb17e0916a03ab901fb684e874d77a1e96b3d1e

  CIFS: Encrypt SMB3 requests before sending
  Commit 026e93dc0a3eefb0be060bcb9ecd8d7a7fd5c398

  CIFS: Enable encryption during session setup phase
  Commit cabfb3680f78981d26c078a26e5c748531257ebb

  CIFS: Add capability to transform requests before sending
  Commit 7fb8986e7449d0a5cebd84d059927afa423fbf85

  CIFS: Separate RFC1001 length processing for SMB2 read
  Commit b8f57ee8aad414a3122bff72d7968a94baacb9b6

  CIFS: Separate SMB2 sync header processing
  Commit cb200bd6264a80c04e09e8635fa4f3901cabdaef

  CIFS: Send RFC1001 length in a separate iov
  Commit 738f9de5cdb9175c19d24cfdf90b4543fc3b47bf

  CIFS: Make send_cancel take rqst as argument
  Commit fb2036d817584df42504910fe104f68517e8990e

  CIFS: Make SendReceive2() takes resp iov
  Commit da502f7df03d2d0b416775f92ae022f3f82bedd5

  CIFS: Separate SMB2 header structure
  Commit 31473fc4f9653b73750d3792ffce6a6e1bdf0da7

  cifs: Add soft dependencies
  Commit b9be76d585d48cb25af8db0d35e1ef9030fbe13a

  cifs: Only select the required crypto modules
  Commit 3692304bba6164be3810afd41b84ecb0e1e41db1

  cifs: Simplify SMB2 and SMB311 dependencies
  Commit c1ecea87471bbb614f8121e00e5787f363140365

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

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

[Kernel-packages] [Bug 1650058] Re: [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and image

[Brad Figg]

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

Title:
  [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel
  and image

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

Bug description:
  In order to have the correct VF driver to support SR-IOV in Azure, the
  Mellanox OFED distribution needs to be included in the kernel and the
  image. Mellanox's drivers are not upstream, but they are available
  from here:

  
https://www.mellanox.com/page/products_dyn?product_family=26=linux_sw_drivers=3nnhohirh5htv6dnp1uk7tf487

  While this configuration is not explicitly listed as supported in the
  release notes, Microsoft and Mellanox engineers are working on the
  corresponding Windows Server 2016 PF driver to support this VF driver
  in operation in Ubuntu guests.

  I file file a corresponding rebase request to pick up the PCI
  passthrough and other SR-IOV work done for the Hyper-V capabilities in
  the upstream 4.9 kernel.

  Only 64-bit support for Ubuntu 16.04's HWE kernel is needed.

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

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

[Kernel-packages] [Bug 1664663] Re: [Hyper-V] kvp daemon start failure on Zesty

[Joshua R. Poulson]

Long is working on a patch for submission upstream that should help with
this, and I will add it here when he does.

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

Title:
  [Hyper-V] kvp daemon start failure on Zesty

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

Bug description:
  Hello,

  On Ubuntu Server 17.04 daily from Febr 14th we see that the KVP daemon
  although it is enabled in systemd, it fails to start at system boot.

  This is shown by error: "KVP: read failed; error:9 Bad file
  descriptor"

  I then manually ran the kvp binary, it returned the KVP data, and it's also 
automatically loading at boot. However, this is of course not the normal 
behavior.
  17.04 daily from Febr 14th is the first build we covered, so I cannot say if 
this is a regression introduced only at some point in 17.04 dailies.

  In syslog these are the only messages for KVP:
  Feb 14 08:01:22 ubuntu systemd[1]: Started Hyper-V KVP Protocol Daemon.
  Feb 14 08:01:22 ubuntu KVP: KVP starting; pid is:1837
  Feb 14 08:01:22 ubuntu KVP: KVP LIC Version: 3.1
  Feb 14 08:02:31 ubuntu KVP: read failed; error:9 Bad file descriptor

  
  systemd status:
  root@ubuntu:~# systemctl status hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
 Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Tue 2017-02-14 08:02:31 PST; 1min 
41s ago
   Main PID: 1837 (code=exited, status=1/FAILURE)
CPU: 4ms

  Feb 14 08:01:22 ubuntu systemd[1]: Started Hyper-V KVP Protocol Daemon.
  Feb 14 08:01:22 ubuntu KVP[1837]: KVP starting; pid is:1837
  Feb 14 08:01:22 ubuntu KVP[1837]: KVP LIC Version: 3.1
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Unit entered failed 
state.
  Feb 14 08:02:31 ubuntu systemd[1]: hv-kvp-daemon.service: Failed with result 
'exit-code'.

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

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

[Kernel-packages] [Bug 1666209] Re: PPC new 4.4.0-63-powerpc63-smp kernel kills networking

[Joseph Salisbury]

Can you test the latest upstream stable kernel to see if this regression
is already fixed? It can be downloaded from:

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

If the bug does still exiest in 4.4.54, we can perform a kernel bisect
to identify the commit that introduced the regression.

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

Title:
  PPC new 4.4.0-63-powerpc63-smp kernel kills networking

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

Bug description:
  After upgrading to a new kernel (4.4.0-63-powerpc64-smp) completely
  lost ethernet. Looks like the kernel doesn't load a module for my
  interface (driver r8169). Rolling back to previous kernel version
  fixes networking.

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

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

[Kernel-packages] [Bug 1667920] Re: login screen freeze

[Joseph Salisbury]

This might be a duplicate of bug 1666421 .

I built a Xenial test kernel with a pick of commit 60f59ce02785. The test 
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1666421/

Can you test this kernel and see if it resolves this bug?

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

Title:
  login screen freeze

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

Bug description:
  Running an up-to-date (as of Feb 25 2017) 16.04 / Unity on an old MSI
  U160 netbook.

  After a recent update to kernel 4.4.0-63 I have started getting frozen
  login screens. The touchpad and keyboard are completely dead (before I
  ever get to enter my password), and my only way out is to force
  shutdown.

  I can start GRUB on boot and go for an earlier version instead, but
  everything past 4.4.0-62 freezes in the same fashion (that's what I'm
  currently running as a temporary fix); a newer update to 4.4.0-64 has
  not fixed the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chirvasitua   1841 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 03:42:57 2017
  HibernationDevice: RESUME=UUID=5e60245a-50f2-4f9c-97b2-d68560e38218
  InstallationDate: Installed on 2015-10-18 (495 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=250be7ea-5182-43d2-b638-5c4a933b4942 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EN051IMS.100
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-N051
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEN051IMS.100:bd02/06/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-N051:pvrTobefilledbyO.E.M.:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-N051:rvrTobefilledbyO.E.M.:cvnMICRO-STARINTERNATIONALCO.,LTD:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-N051
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Kernel-packages] [Bug 759725] Re: The kernel is no longer readable by non-root users

[Velkan]

Why guestmount can't work out of box? That was a perfect userspace
option to get a loop device to test out-of-space errors.

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

Title:
  The kernel is no longer readable by non-root users

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  The mode of the latest kernel has changed so it is no longer readable
  by non-root users:

  -rw-r--r-- 1 root root 4336016 2010-10-17 01:37 
/boot/vmlinuz-2.6.35-22-generic
  -rw-r--r-- 1 root root 4336912 2010-11-24 12:46 
/boot/vmlinuz-2.6.35-23-generic
  -rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic
  -rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic

  This prevents people from using this kernel to boot qemu
  virtual machines as non-root.

  Please change the mode back to make the kernel readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: aplay: device_list:240: no soundcards found...
  Architecture: amd64
  ArecordDevices: arecord: device_list:240: no soundcards found...
  CRDA: Error: [Errno 2] No such file or directory
  Date: Wed Apr 13 13:05:01 2011
  HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  PciMultimedia:
   
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-2.6.35-22-generic N/A
   linux-backports-modules-2.6.35-22-generic  N/A
   linux-firmware 1.50
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.0.0PC:cvnRedHat:ct1:cvr:
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.0.0 PC
  dmi.sys.vendor: Red Hat

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

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

[Kernel-packages] [Bug 1667920] Re: login screen freeze

[Joseph Salisbury]

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

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

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

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

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

Title:
  login screen freeze

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

Bug description:
  Running an up-to-date (as of Feb 25 2017) 16.04 / Unity on an old MSI
  U160 netbook.

  After a recent update to kernel 4.4.0-63 I have started getting frozen
  login screens. The touchpad and keyboard are completely dead (before I
  ever get to enter my password), and my only way out is to force
  shutdown.

  I can start GRUB on boot and go for an earlier version instead, but
  everything past 4.4.0-62 freezes in the same fashion (that's what I'm
  currently running as a temporary fix); a newer update to 4.4.0-64 has
  not fixed the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chirvasitua   1841 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 25 03:42:57 2017
  HibernationDevice: RESUME=UUID=5e60245a-50f2-4f9c-97b2-d68560e38218
  InstallationDate: Installed on 2015-10-18 (495 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-N051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic 
root=UUID=250be7ea-5182-43d2-b638-5c4a933b4942 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-62-generic N/A
   linux-backports-modules-4.4.0-62-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EN051IMS.100
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-N051
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEN051IMS.100:bd02/06/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-N051:pvrTobefilledbyO.E.M.:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-N051:rvrTobefilledbyO.E.M.:cvnMICRO-STARINTERNATIONALCO.,LTD:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-N051
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Kernel-packages] [Bug 1673213] Re: linux: 4.4.0-69.90 -proposed tracker

[Thadeu Lima de Souza Cascardo]

** Summary changed:

- linux: 4.4.0-68.89 -proposed tracker
+ linux: 4.4.0-69.90 -proposed tracker

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

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

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

Title:
  linux: 4.4.0-69.90 -proposed tracker

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

  backports: 1673216
  derivatives: 1673218,1673219,1673220,1673221

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

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

[Kernel-packages] [Bug 1673498] [NEW] move aufs.ko from -extra to linux-image package

[Kamal Mostafa]

Public bug reported:

Docker is ordinarily configured to use aufs, but the aufs kernel module
is only available after installing the linux-image-extra package.

Please promote aufs.ko from the linux-image-extra package to the main
linux-image package for all supported Ubuntu kernels and derivatives, so
as to remove Docker's dependence on linux-image-extra.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: Incomplete


** Tags: bot-stop-nagging

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

Title:
  move aufs.ko from -extra to linux-image package

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Docker is ordinarily configured to use aufs, but the aufs kernel
  module is only available after installing the linux-image-extra
  package.

  Please promote aufs.ko from the linux-image-extra package to the main
  linux-image package for all supported Ubuntu kernels and derivatives,
  so as to remove Docker's dependence on linux-image-extra.

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

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1673498

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

Title:
  move aufs.ko from -extra to linux-image package

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Docker is ordinarily configured to use aufs, but the aufs kernel
  module is only available after installing the linux-image-extra
  package.

  Please promote aufs.ko from the linux-image-extra package to the main
  linux-image package for all supported Ubuntu kernels and derivatives,
  so as to remove Docker's dependence on linux-image-extra.

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

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

[Kernel-packages] [Bug 1663991] Re: Unable to Connect Third HDD via USB Hub

[Joseph Salisbury]

@Vej Yes the SRU request can be viewed in this mail thread on the kernel
team mailing list:

https://lists.ubuntu.com/archives/kernel-team/2017-March/082946.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/1663991

Title:
  Unable to Connect Third HDD via USB Hub

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Hello, I am running:

  (K)Ubuntu 16.10
  4.8.0-37-generic #39-Ubuntu SMP Thu Jan 26 02:27:07 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

  There has been found a bug in 4.8, which causes kernel call trace when
  I connect third USB HDD to a USB hub. After the trace, kswapd0 process
  uses 100% of CPU.

  The bug has been fixed in 4.10. Is it possible to roll out new kernel
  packages, please?

  
  References:
  https://ubuntuforums.org/showthread.php?t=2345213
  https://bugzilla.kernel.org/show_bug.cgi?id=177551
  http://marc.info/?l=linux-mm-commits=148650422714993=2

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

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

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

[Joseph Salisbury]

The 4.4.44 kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.44/

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1664602] Re: Using an NVMe drive causes huge power drain

[Tim Gardner]

** Changed in: linux (Ubuntu Zesty)
   Status: Won't Fix => In Progress

** Changed in: linux (Ubuntu Zesty)
 Assignee: Tim Gardner (timg-tpi) => Kai-Heng Feng (kaihengfeng)

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

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

Title:
  Using an NVMe drive causes huge power drain

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

Bug description:
  PCIe NVMe drives are very common in new laptops. The Zesty's kernels 
(including latest 4.10 rc8 from CKT PPA) does not support APST (autonomous 
power state transitions). A patch does exist :
  http://lists.infradead.org/pipermail/linux-nvme/2017-February/008051.html
  https://github.com/damige/linux-nvme

  It seems that we cannot expect this before kernel 4.11.

  Additionally my laptop CPU does never go under PC3 power saving state, 
powertop says. I don't know if it's related.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ft 1900 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=a04b55bf-b1b6-464c-88ce-44b6adbbbc10
  InstallationDate: Installed on 2016-12-12 (63 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=0d1f213e-73a9-4097-ae64-9cd963cfba23 ro quiet
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-8-generic N/A
   linux-backports-modules-4.10.0-8-generic  N/A
   linux-firmware1.163
  Tags:  zesty
  Uname: Linux 4.10.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.5
  dmi.board.name: 0YH43H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.5:bd12/22/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0YH43H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

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

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

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

[Joseph Salisbury]

It sounds like the upstream 4.4 kernel does not have the bug per
comments #10 and #12.

It appears this bug may be caused by a SAUCE patch that is not in the
upstream kernel.  To confirm that, can you test the upstream 4.4.44
kernel, which is what 4.4.0-64.85 is based on?

If the bug does not exist in 4.4.44, we can perform a kernel bisect with
the Ubuntu kernels to find that SAUCE commit that introduced this bug.

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1292036] Re: Displayport on Thinkpad T420s is not usable

[parislanuit]

Computer: Lenovo Thinkpad T420
Ubuntu 16.10: Display port still don't work

I am using a cable displayport to Hdmi with an asus screen with no
displayport (but 2xhdmi)

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
83et79ww (1.49)
09/05/2016


in the bios : Screen not found, only the built in lcd.
in ubuntu: System/screen => both screens are detected although the 2nd screen 
seems not to receive any data & the screen shuts off automatically very fast 
(stand by)

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

Title:
  Displayport on Thinkpad T420s is not usable

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,
  I'm trying to connect an external screen to my thinkpad T420s. I'm running 
Ubuntu 14.04 and here is the output of xrandr:

  $ xrandr
  Screen 0: minimum 320 x 200, current 1600 x 900, maximum 32767 x 32767
  LVDS1 connected primary 1600x900+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
 1600x900   60.0*+   40.0  
 1440x900   59.9  
 1360x768   59.8 60.0  
 1152x864   60.0  
 1024x768   60.0  
 800x60060.3 56.2  
 640x48059.9  
  VGA1 disconnected (normal left inverted right x axis y axis)
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)

  LVDS1 is the LCD-display on the laptop. This is the output of lspci:

  $ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
  01:00.0 VGA compatible controller: NVIDIA Corporation GF119M [NVS 4200M] (rev 
ff)

  The screen recognises that something is plugged into the DisplayPort
  but Ubuntu is unable to send output to it. It's probably related to
  the whole dual graphics card thing.

  Thank you for reading this bug!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  Date: Thu Mar 13 15:32:36 2014
  DistUpgraded: 2014-02-24 23:10:48,392 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21d3]
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2013-08-07 (217 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MachineType: LENOVO 4174PEG
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=7d44dac8-470f-4bb6-a331-e31a6e61ea51 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-02-24 (16 days ago)
  dmi.bios.date: 11/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8CET50WW (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4174PEG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8CET50WW(1.30):bd11/01/2011:svnLENOVO:pn4174PEG:pvrThinkPadT420s:rvnLENOVO:rn4174PEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4174PEG
  dmi.product.version: ThinkPad T420s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140305-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Mar 13 14:44:03 2014
  xserver.configfile: default
  xserver.errors: Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8510 
   vendor

[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)

[aljosa]

I still haven't found workaround for any of our problems with ASUS laptops.
Kernel developer who in the past solved Elan touchpad issues on my previous two 
ASUS laptops told me that this time he unfortunately can't help me because my 
current problem is something with the elan_i2c driver. Consequently, I 
contacted some other kernel developers a month ago, but I haven't received any 
concrete response.

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

Title:
  ASUS G752VS: Touchpad and Fn keys not working (Ubuntu
  16.04.1/16.10/17.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Non-Optimus laptop ASUS G752VS-GC063D-CST256.
  17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 
NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 
802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 
x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS.

  Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and
  17.04, among other problems I found that touchpad and Fn keys (all
  except volume control) doesn't work on my brand new ASUS G752VS.

  It is very hard even to try Ubuntu 16.10 and 17.04 because of the
  missing mouse pointer. This problem must be related to a video driver
  because if after installing one is capable to install Nvidia drivers -
  problem is solved. This problem doesn't exist both while trying and
  installing Ubuntu 16.04.1!

  I'm currently on Windows 10, and this bug report is made from Ubuntu
  16.04.1 LiveCD.

  
  dmesg | grep -i elan
  [  101.082929] input: ELAN1203:00 04F3:3043 Touchpad as 
/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11
  [  101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID 
v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00

  
  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ G-SPY USB Gaming Mouse  id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN1203:00 04F3:3043 Touchpad  id=15   [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)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ G-SPY USB Gaming Mouse  id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ ASASTeK COMPUTER INC. ROG MacroKey  id=12   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4
  U: Uniq=
  H: Handlers=kbd event4 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=04d9 Product=a070 Version=0110
  N: Name="G-SPY USB Gaming Mouse"
  P: Phys=usb-:00:14.0-2/input0
  S: 

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

[Thadeu Lima de Souza Cascardo]

** Summary changed:

- linux-lts-trusty:  -proposed tracker
+ linux-lts-trusty: 3.13.0-114.161~precise1 -proposed tracker

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed 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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

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

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

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

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

[Kernel-packages] [Outdated E-Mail!] Re: [Bug 1177086] Re: amd64: "Fixing recursive fault but reboot is needed!"

[The Bright Side]

Hi there!

This e-mail address (m...@knowingme.org) is no longer in use.

Your e-mail has been forwarded to my current e-mail address
(m...@meetmatteastwood.com), and I will respond to you from there.

Be sure to update your address book :-)

Thanks,
- Matt.

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

Title:
  amd64: "Fixing recursive fault but reboot is needed!"

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After the completed Raring Ringtail amd64 installation every boot ends
  in the following statement "Fixing recursive fault but reboot is
  needed!". No terminal, no gui, no logs at this point. Others say they
  can boot after about 10 tries every time, but I can not. Maybe someone
  can provide logs from a successful boot, but mine are all empty. I
  attach lscpu, lshw and lspci output acquired from the Raring Ringtail
  amd64 live CD. The live mode works fine, the problem arises upon
  installation.

  I can not boot the Raring installation at all.

  Several people experiencing this bug, including me, reported it over
  at bug #1066435, but I was told that, although both bugs share the
  same behaviour, they probably originate from different problems. Also,
  bug #1175660 has a similar error message, but seems able to boot
  properly.

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

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

[Kernel-packages] [Bug 1646622] Re: TouchPad doesn't work ASUS x556uj

[Christopher M. Penalver]

As per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646622/comments/13.

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1646622

Title:
  TouchPad doesn't work ASUS x556uj

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  My TouchPad doesn't work on ASUS x556uj-xx186D 
  It is a new laptop, with dual bot with windows 10, and the touchpad work fine 
in windows 10.
  in my ubuntu 16.10 the touchpad isn't working.

  (i don't know what is the manufacturer of the touchpad is...)

  thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-28-generic 4.8.0-28.30
  ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
  Uname: Linux 4.8.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  avi2228 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec  1 23:10:43 2016
  HibernationDevice: RESUME=UUID=e64b1929-f4cf-4bcb-bbfc-e77d031f6728
  InstallationDate: Installed on 2016-11-28 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: ASUSTeK COMPUTER INC. X556UJ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-28-generic 
root=UUID=ae71182c-429d-4b16-acf4-990d1bdf256f ro quiet splash pci=nomsi 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-28-generic N/A
   linux-backports-modules-4.8.0-28-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UJ.406
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UJ.406:bd06/28/2016:svnASUSTeKCOMPUTERINC.:pnX556UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X556UJ
  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/1646622/+subscriptions

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

[Kernel-packages] [Bug 1670800] Re: Power9 kernel: add virtualization patches

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Power9 kernel: add virtualization patches

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

Bug description:
  Dear Canonical,

  Please add the following patches for POWER9:

  From powerpc/next tree:

cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of
  radix MMU under hypervisor on POWER9

6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9
  architected mode to cputable

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

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

[Kernel-packages] [Bug 1671169] Re: POWER9: Improve CAS negotiation

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  POWER9: Improve CAS negotiation

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

Bug description:
  Dear Canonical,

  Could you please add the following patches into Ubuntu 17.04 and
  16.04.2 (4.8) ? It improves Virtualization on POWER9.

  commit 014d02cbf16b3106dc8e93281d2a9c189751ed5e
  Author: Suraj Jitindar Singh 
  Date:   Tue Feb 28 17:03:48 2017 +1100

  powerpc: Update to new option-vector-5 format for CAS

  commit 12cc9fd6b2d8ee307a735b3b9faed0d17b719463
  Author: Suraj Jitindar Singh 
  Date:   Tue Feb 28 17:03:47 2017 +1100

  powerpc: Parse the command line before calling CAS

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

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

[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

[Christopher M. Penalver]

** Project changed: linux => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => 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/1602888

Title:
  Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
  be an issue with the fan control. When I first boot up the machine the
  fans are off. However, after the laptop warms up under normal usage,
  the fans kick on and then never shut off again.  Even when the CPU
  cools down to below 35c, the fans will continue to run.

  If I suspend the the laptop, and then immediately wake it up again
  then fans are once again off, until it warms up again.  So
  essentially, once the fans start they don't seem to ever shut off.

  Fans seem to work normally under Windows 10.  They turn on as needed,
  and then turn off once the laptop cools down.

  I've tried the various BIOS updates that Dell has released, without
  success. I am currently running Dell's latest BIOS for this laptop
  (v1.1.8)

  Below is the output of lm-sensors showing the fans running when the
  CPU is at a cool 35c

  dell_smm-virtual-0
  Adapter: Virtual device
  Processor Fan: 1925 RPM
  Processor Fan: 2143 RPM
  CPU:+35.0°C  
  GPU: +1.0°C  
  SODIMM: +49.0°C

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1709 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 19:18:45 2016
  HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
  InstallationDate: Installed on 2016-07-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 7559
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.8
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.8
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

[Christopher M. Penalver]

** No longer affects: linux (Ubuntu)

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

Title:
  Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
  be an issue with the fan control. When I first boot up the machine the
  fans are off. However, after the laptop warms up under normal usage,
  the fans kick on and then never shut off again.  Even when the CPU
  cools down to below 35c, the fans will continue to run.

  If I suspend the the laptop, and then immediately wake it up again
  then fans are once again off, until it warms up again.  So
  essentially, once the fans start they don't seem to ever shut off.

  Fans seem to work normally under Windows 10.  They turn on as needed,
  and then turn off once the laptop cools down.

  I've tried the various BIOS updates that Dell has released, without
  success. I am currently running Dell's latest BIOS for this laptop
  (v1.1.8)

  Below is the output of lm-sensors showing the fans running when the
  CPU is at a cool 35c

  dell_smm-virtual-0
  Adapter: Virtual device
  Processor Fan: 1925 RPM
  Processor Fan: 2143 RPM
  CPU:+35.0°C  
  GPU: +1.0°C  
  SODIMM: +49.0°C

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1709 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 19:18:45 2016
  HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
  InstallationDate: Installed on 2016-07-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 7559
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.8
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.8
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

[Launchpad Bug Tracker]

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

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

Title:
  Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
  be an issue with the fan control. When I first boot up the machine the
  fans are off. However, after the laptop warms up under normal usage,
  the fans kick on and then never shut off again.  Even when the CPU
  cools down to below 35c, the fans will continue to run.

  If I suspend the the laptop, and then immediately wake it up again
  then fans are once again off, until it warms up again.  So
  essentially, once the fans start they don't seem to ever shut off.

  Fans seem to work normally under Windows 10.  They turn on as needed,
  and then turn off once the laptop cools down.

  I've tried the various BIOS updates that Dell has released, without
  success. I am currently running Dell's latest BIOS for this laptop
  (v1.1.8)

  Below is the output of lm-sensors showing the fans running when the
  CPU is at a cool 35c

  dell_smm-virtual-0
  Adapter: Virtual device
  Processor Fan: 1925 RPM
  Processor Fan: 2143 RPM
  CPU:+35.0°C  
  GPU: +1.0°C  
  SODIMM: +49.0°C

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1709 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 19:18:45 2016
  HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
  InstallationDate: Installed on 2016-07-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 7559
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.8
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.8
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1671614] Re: linux: 4.10.0-13.15 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  linux: 4.10.0-13.15 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  Confirmed
Status in Kernel Development Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug is for tracking the 4.10.0-13.15 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-development-workflow/+bug/1671614/+subscriptions

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

[Kernel-packages] [Bug 1645962] Re: [Feature] GLK Intel PT write

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  [Feature] GLK Intel PT write

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Gemini Lake has support for Intel PT write.

  HW: Gemini Lake

  Upstream schedule:
  kernel: 4.11

  Commit Ids:
  5443624bed
  8ee83b2ab3

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

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

[Kernel-packages] [Bug 1670726] Re: h-prod does not function across cores

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  h-prod does not function across cores

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Released

Bug description:
  There is a  performance problem issue with h-prod. I can see that
  h-prod calls are only waking hardware threads from a h-cede call when
  the caller is on the same core as the thread being awoken (sibling
  theads).  For cross core prods the target thread remains in h-cede
  until its next decrementer interrupt.  That is causing guest OS some
  significant dispatching delays.

   The fix is now upstream as commit 8464c8842de2 ("KVM: PPC: Book3S HV:
  Fix H_PROD to actually wake the target vcpu", 2016-12-06) in
  v4.11-rc1.

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

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

[Kernel-packages] [Bug 1671602] Re: QDF2400: Fix panic introduced by erratum 1003

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  QDF2400: Fix panic introduced by erratum 1003

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  zesty's kernel carries a backport of an erratum workaround (Falkor
  1003) from 4.11-rc1. This was found to cause a crash on the QDF2400.

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

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

[Kernel-packages] [Bug 1671169] Re: POWER9: Improve CAS negotiation

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  POWER9: Improve CAS negotiation

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

Bug description:
  Dear Canonical,

  Could you please add the following patches into Ubuntu 17.04 and
  16.04.2 (4.8) ? It improves Virtualization on POWER9.

  commit 014d02cbf16b3106dc8e93281d2a9c189751ed5e
  Author: Suraj Jitindar Singh 
  Date:   Tue Feb 28 17:03:48 2017 +1100

  powerpc: Update to new option-vector-5 format for CAS

  commit 12cc9fd6b2d8ee307a735b3b9faed0d17b719463
  Author: Suraj Jitindar Singh 
  Date:   Tue Feb 28 17:03:47 2017 +1100

  powerpc: Parse the command line before calling CAS

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

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

[Kernel-packages] [Bug 1667078] Re: bcache device numbers increase by 16

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  bcache device numbers increase by 16

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  On 4.10 kernel, when creating bcache devices, each device kname is now
  incremented by 16

  /dev/bcache0
  /dev/bcache16
  /dev/bcache32

  etc.

  This was to support partitioning of bcache devices[1], however, This
  also will limit the number of bcache devices and doesn't match how
  other block devices name themselves, md for example, you get md0p1,
  md1p1, md2p1 etc.

  Ideally we'd continue to see devices increment by 1, and ensure we
  allocate partition numbers as well.

  I think the patch[1] below is incomplete; I think we also want to
  shift the minor value by the number of partitions when we set the
  disk_name value.

  drivers/md/bcache/super.c:

 snprintf(d->disk->disk_name, DISK_NAME_LEN, "bcache%i", minor);

  to

 snprintf(d->disk->disk_name, DISK_NAME_LEN, "bcache%i", minor >>
  4);

  This should keep the devname index based, while creating the device node with
  the appropriate space for partitions, like this:

  $ ls -al /dev/bcache*
  brw-rw 1 root disk 251,  0 Feb 22 17:40 /dev/bcache0
  brw-rw 1 root disk 251,  1 Feb 22 17:40 /dev/bcache0p1
  brw-rw 1 root disk 251, 16 Feb 22 17:40 /dev/bcache1
  brw-rw 1 root disk 251, 17 Feb 22 17:40 /dev/bcache1p1

  
  1. https://www.spinics.net/lists/linux-bcache/msg04267.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-8-generic 4.10.0-8.10
  ProcVersionSignature: User Name 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 22 17:36 seq
   crw-rw 1 root audio 116, 33 Feb 22 17:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Feb 22 17:41:18 2017
  Ec2AMI: ami-056c
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=15278dff-350d-42a1-8767-1424dfca7894 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-8-generic N/A
   linux-backports-modules-4.10.0-8-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr13.1.2:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: OpenStack Nova
  

[Kernel-packages] [Bug 1670800] Re: Power9 kernel: add virtualization patches

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  Power9 kernel: add virtualization patches

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

Bug description:
  Dear Canonical,

  Please add the following patches for POWER9:

  From powerpc/next tree:

cc3d2940133d24000e2866b21e03ce32adfead0a - powerpc/64: Enable use of
  radix MMU under hypervisor on POWER9

6ae3f8ad2017079292cb49c8959b527bcbcbefed - powerpc: Add POWER9
  architected mode to cputable

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

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

[Kernel-packages] [Bug 1655986] Re: lowlatency kernel is lacking support for latencytop

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  lowlatency kernel is lacking support for latencytop

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Actual behavior:

  $ sudo latencytop
  mount: none is already mounted or /sys/kernel/debug busy
  Please enable the CONFIG_LATENCYTOP configuration in your kernel.
  Exiting...

  $ grep -i latencytop /boot/config-`uname -r`
  CONFIG_HAVE_LATENCYTOP_SUPPORT=y
  # CONFIG_LATENCYTOP is not set

  
  Expected behavior:

  # working latencytop and
  $ grep -i latencytop /boot/config-`uname -r`
  CONFIG_HAVE_LATENCYTOP_SUPPORT=y
  CONFIG_LATENCYTOP=y

  
  Tested with package linux-image-4.4.0-57-lowlatency.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-lowlatency 4.4.0.59.62
  ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
  Uname: Linux 4.4.0-57-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mira   2801 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Jan 12 16:33:59 2017
  EcryptfsInUse: Yes
  HibernationDevice:
   #RESUME=UUID=609d4e01-862b-4199-bd45-ad8841f8c8c3
   #RESUME=UUID=69fefec2-0a4f-489b-bb6e-62eab3d97735
  InstallationDate: Installed on 2009-10-08 (2652 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Alpha amd64 (20091008)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency 
root=UUID=23b87e6c-20b4-4242-9489-1599d62abcce ro vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-lowlatency N/A
   linux-backports-modules-4.4.0-57-lowlatency  N/A
   linux-firmware   1.157.6
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-11-14 (59 days ago)
  dmi.bios.date: 08/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/20/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1671598] Re: irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Performance of devices on GICv3 based systems can be improved by
  allowing them to read the GIC-ITS and GICR tables out of cache instead
  of external memory. This was addressed upstream in the following
  commit:

  commit 2fd632a00383e812db7186f903ebed808d9951bd
  Author: Shanker Donthineni 
  Date:   Wed Jan 25 21:51:41 2017 -0600

  irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

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

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

[Kernel-packages] [Bug 1671601] Re: QDF2400 PCI ports require ACS quirk

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  QDF2400 PCI ports require ACS quirk

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Features of the QDF2400 PCI root ports are disabled because they do
  not advertise an ACS capability. A quirk has been merged upstream that
  re-enable these features on that platform:

  commit 33be632b8443b6ac74aa293504f430604fb9abeb
  Author: Sinan Kaya 
  Date:   Thu Feb 16 17:01:45 2017 -0500

  PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432
  
  The Qualcomm QDF2xxx root ports don't advertise an ACS capability, but 
they
  do provide ACS-like features to disable peer transactions and validate bus
  numbers in requests.
  
  To be specific:
  * Hardware supports source validation but it will report the issue as
  Completer Abort instead of ACS Violation.
  
  * Hardware doesn't support peer-to-peer and each root port is a root
  complex with unique segment numbers.
  
  * It is not possible for one root port to pass traffic to the other root
  port.  All PCIe transactions are terminated inside the root port.
  
  Add an ACS quirk for the QDF2400 and QDF2432 products.
  
  [bhelgaas: changelog]
  Signed-off-by: Sinan Kaya 
  Signed-off-by: Bjorn Helgaas 
  Reviewed-by: Alex Williamson 

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

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

[Kernel-packages] [Bug 1665113] Re: [Ubuntu 17.04] Kernel panics when large number of hugepages is passed as an boot argument to kernel.

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  [Ubuntu 17.04] Kernel panics when large number of hugepages is passed
  as an boot argument to kernel.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Issue:
  ---
  Kernel unable to handle paging request and panic occurs when more number of 
hugepages is passed as a boot argument to the kernel .

  Environment:
  --
  Power NV : Habanaro Bare metal
  OS : Ubuntu 17.04
  Kernel Version : 4.9.0-11-generic

  Steps To reproduce:
  ---

  1 - When the ubuntu Kernel boots try to add the boot argument
  'hugepages = 1200'.

  The Kernel Panics and displays call traces like as below.

  [5.030274] Unable to handle kernel paging request for data at address 
0x
  [5.030323] Faulting instruction address: 0xc0302848
  [5.030366] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.030399] SMP NR_CPUS=2048 [5.030416] NUMA 
  [5.039443] PowerNV
  [5.039461] Modules linked in:
  [5.050091] CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.9.0-11-generic 
#12-Ubuntu
  [5.053266] Workqueue: events pcpu_balance_workfn
  [5.080647] task: c03c8fe9b800 task.stack: c03ffb118000
  [5.090876] NIP: c0302848 LR: c02709d4 CTR: 
c016cef0
  [5.094175] REGS: c03ffb11b410 TRAP: 0300   Not tainted  
(4.9.0-11-generic)
  [5.103040] MSR: 92009033 [
5.114466]   CR: 22424222  XER: 
  [5.124932] CFAR: c0008a60 DAR:  DSISR: 4000 
SOFTE: 1 
  GPR00: c02709d4 c03ffb11b690 c141a400 c03fff50e300 
  GPR04:  024001c2 c03ffb11b780 00219df5 
  GPR08: 003ffb09 c1454fd8   
  GPR12: 4400 c7b6 024001c2 024001c2 
  GPR16: 024001c2   0002 
  GPR20: 000c   024200c0 
  GPR24: c16eef48  c03fff50fd00 024001c2 
  GPR28:  c03fff50fd00 c03fff50e300 c03ffb11b820 
  NIP [c0302848] mem_cgroup_soft_limit_reclaim+0xf8/0x4f0
  [5.213613] LR [c02709d4] do_try_to_free_pages+0x1b4/0x450
  [5.230521] Call Trace:
  [5.230643] [c03ffb11b760] [c02709d4] 
do_try_to_free_pages+0x1b4/0x450
  [5.254184] [c03ffb11b800] [c0270d68] 
try_to_free_pages+0xf8/0x270
  [5.281896] [c03ffb11b890] [c0259b88] 
__alloc_pages_nodemask+0x7a8/0xff0
  [5.321407] [c03ffb11bab0] [c0282cd0] 
pcpu_populate_chunk+0x110/0x520
  [5.336262] [c03ffb11bb50] [c02841b8] 
pcpu_balance_workfn+0x758/0x960
  [5.351526] [c03ffb11bc50] [c00ecdd0] 
process_one_work+0x2b0/0x5a0
  [5.362561] [c03ffb11bce0] [c00ed168] worker_thread+0xa8/0x660
  [5.374007] [c03ffb11bd80] [c00f5320] kthread+0x110/0x130
  [5.385160] [c03ffb11be30] [c000c0e8] 
ret_from_kernel_thread+0x5c/0x74
  [5.389456] Instruction dump:
  [5.410036] eb81ffe0 eba1ffe8 ebc1fff0 ebe1fff8 4e800020 3d230001 e9499a42 
3d220004 
  [5.423598] 3929abd8 794a1f24 7d295214 eac90100  2fa9 
419eff74 3b20 
  [

[Kernel-packages] [Bug 1669807] Re: Allow Mir/Unity8 to run inside Virtualbox

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

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

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  Allow Mir/Unity8 to run inside Virtualbox

Status in Mir:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released

Bug description:
  (See duplicate bug 1639745 for more history)

  Vboxvideo lacks PRIME support. A patch has been sent upstream.

  https://www.virtualbox.org/pipermail/vbox-dev/2017-March/014293.html

  It may take some time until that hits the repository. I attached a
  patch I tested on zesty and allows unity8 to run virtualbox.

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

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

[Kernel-packages] [Bug 1671589] Re: ehci-platform needed in usb-modules udeb

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  ehci-platform needed in usb-modules udeb

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  ehci-platform is a usb host driver. This is used to drive the host
  controller on HiSilicon D05 systems. In order to allow netboot-based
  installs using a USB NIC, or CD/usbstick based installs using USB-
  connected media, this driver needs to be included in the installer.
  Adding this module to the usb-modules udeb produced by the kernel
  would be sufficient to do so.

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

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

[Kernel-packages] [Bug 1669061] Re: arm64: ACPI platform MSI support required for new systems

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-13.15

---
linux (4.10.0-13.15) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
- LP: #1671614

  * ehci-platform needed in usb-modules udeb (LP: #1671589)
- d-i: add ehci-platform to usb-modules

  * irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints
(LP: #1671598)
- irqchip/gic-v3-its: Enable cacheable attribute Read-allocate hints

  * iommu: Fix static checker warning in iommu_insert_device_resv_regions
(LP: #1671599)
- iommu: Fix static checker warning in iommu_insert_device_resv_regions

  * QDF2400: Fix panic introduced by erratum 1003 (LP: #1671602)
- arm64: Avoid clobbering mm in erratum workaround on QDF2400

  * QDF2400 PCI ports require ACS quirk (LP: #1671601)
- PCI: Add ACS quirk for Qualcomm QDF2400 and QDF2432

  * tty: pl011: Work around QDF2400 E44 stuck BUSY bit (LP: #1671600)
- tty: pl011: Work around QDF2400 E44 stuck BUSY bit

  * CVE-2017-2636
- tty: n_hdlc: get rid of racy n_hdlc.tbuf

  * Sync virtualbox to 5.1.16-dfsg-1 in zesty (LP: #1671470)
- ubuntu: vbox -- Update to 5.1.16-dfsg-1

 -- Tim Gardner   Thu, 09 Mar 2017 06:16:24
-0700

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-2636

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

Title:
  arm64: ACPI platform MSI support required for new systems

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  The HiSilicon D05 and Qualcomm QDF2400 systems require ACPI support
  for platform MSIs.

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

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

[Kernel-packages] [Bug 1665113] meminfo of the system

[bugproxy]

Default Comment by Bridge

** Attachment added: "meminfo of the system"
   https://bugs.launchpad.net/bugs/1665113/+attachment/4838984/+files/NV_meminfo

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

Title:
  [Ubuntu 17.04] Kernel panics when large number of hugepages is passed
  as an boot argument to kernel.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Issue:
  ---
  Kernel unable to handle paging request and panic occurs when more number of 
hugepages is passed as a boot argument to the kernel .

  Environment:
  --
  Power NV : Habanaro Bare metal
  OS : Ubuntu 17.04
  Kernel Version : 4.9.0-11-generic

  Steps To reproduce:
  ---

  1 - When the ubuntu Kernel boots try to add the boot argument
  'hugepages = 1200'.

  The Kernel Panics and displays call traces like as below.

  [5.030274] Unable to handle kernel paging request for data at address 
0x
  [5.030323] Faulting instruction address: 0xc0302848
  [5.030366] Oops: Kernel access of bad area, sig: 11 [#1]
  [5.030399] SMP NR_CPUS=2048 [5.030416] NUMA 
  [5.039443] PowerNV
  [5.039461] Modules linked in:
  [5.050091] CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.9.0-11-generic 
#12-Ubuntu
  [5.053266] Workqueue: events pcpu_balance_workfn
  [5.080647] task: c03c8fe9b800 task.stack: c03ffb118000
  [5.090876] NIP: c0302848 LR: c02709d4 CTR: 
c016cef0
  [5.094175] REGS: c03ffb11b410 TRAP: 0300   Not tainted  
(4.9.0-11-generic)
  [5.103040] MSR: 92009033 [
5.114466]   CR: 22424222  XER: 
  [5.124932] CFAR: c0008a60 DAR:  DSISR: 4000 
SOFTE: 1 
  GPR00: c02709d4 c03ffb11b690 c141a400 c03fff50e300 
  GPR04:  024001c2 c03ffb11b780 00219df5 
  GPR08: 003ffb09 c1454fd8   
  GPR12: 4400 c7b6 024001c2 024001c2 
  GPR16: 024001c2   0002 
  GPR20: 000c   024200c0 
  GPR24: c16eef48  c03fff50fd00 024001c2 
  GPR28:  c03fff50fd00 c03fff50e300 c03ffb11b820 
  NIP [c0302848] mem_cgroup_soft_limit_reclaim+0xf8/0x4f0
  [5.213613] LR [c02709d4] do_try_to_free_pages+0x1b4/0x450
  [5.230521] Call Trace:
  [5.230643] [c03ffb11b760] [c02709d4] 
do_try_to_free_pages+0x1b4/0x450
  [5.254184] [c03ffb11b800] [c0270d68] 
try_to_free_pages+0xf8/0x270
  [5.281896] [c03ffb11b890] [c0259b88] 
__alloc_pages_nodemask+0x7a8/0xff0
  [5.321407] [c03ffb11bab0] [c0282cd0] 
pcpu_populate_chunk+0x110/0x520
  [5.336262] [c03ffb11bb50] [c02841b8] 
pcpu_balance_workfn+0x758/0x960
  [5.351526] [c03ffb11bc50] [c00ecdd0] 
process_one_work+0x2b0/0x5a0
  [5.362561] [c03ffb11bce0] [c00ed168] worker_thread+0xa8/0x660
  [5.374007] [c03ffb11bd80] [c00f5320] kthread+0x110/0x130
  [5.385160] [c03ffb11be30] [c000c0e8] 
ret_from_kernel_thread+0x5c/0x74
  [5.389456] Instruction dump:
  [5.410036] eb81ffe0 eba1ffe8 ebc1fff0 ebe1fff8 4e800020 3d230001 e9499a42 
3d220004 
  [5.423598] 3929abd8 794a1f24 7d295214 eac90100  2fa9 
419eff74 3b20 
  [5.436503] ---[ end trace 23b650e96be5c549 ]---
  [5.439700] 

  This is purely a negative scenario where the system does not have
  enough memory as the hugepages is given a very large argument.

  Free output in a system:
  free -h
totalusedfree  shared  buff/cache   
available
  Mem:   251G2.1G248G5.2M502M
248G
  Swap:  2.0G159M1.8G

  The same scenario when tried after the linux is up like as,

  echo 1200 > /proc/sys/vm/nr_hugepages

  HugePages_Total:   15069
  HugePages_Free:15069
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:  16384 kB
  root@ltc-haba2:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   251G237G 13G5.6M311M 
13G
  Swap:  2.0G159M1.8G

  In this case the kernel is able to allocate around 237 Gb for hugetlb.

  But while the system is booting it gives us panic so please let know
  if this scenario  is expected  to be handled.

  I identified the root cause of the panic.
  When the system is running with low memory during mem cgroup