[Kernel-packages] [Bug 1503695] Re: nft nat not working

[Launchpad Bug Tracker]

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

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

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

Title:
  nft nat not working

Status in linux package in Ubuntu:
  Expired
Status in nftables package in Ubuntu:
  Expired

Bug description:
  Hi ,

  I have installed an ubuntu 15.10 beta machine and configured nftables
  firewalling.

  While the regular firewalling works (using the default settings that
  come with the package), I found that nat rules are silently ignored.
  I've added this to the /etc/nftables.conf and read it:

  table ip nat {

chain prerouting {
  type nat hook prerouting priority 0;
  ip daddr 1.2.3.4 tcp dport 80 redirect to 1234
  tcp dport 80 redirect to 1235
}

chain postrouting {
  type nat hook postrouting priority 0;
} 

  }

  
  following the example from 

  http://wiki.nftables.org/wiki-
  nftables/index.php/Performing_Network_Address_Translation_%28NAT%29#Redirect

  (1.2.3.4 is just a placeholder for the address actually used here, i
  do not want to reveal the address to the bug report). nft reads this
  without complaining, and

  nft list table ip nat

  gives exactly that output (except for replacing 80 with "http"), so
  the configuration is read correctly.


  But it simply does not work. Without having any daemon listening on
  ports 1234, 1235 , traffic to port 80 works as usual. As long as there
  is not process waiting on 1234/1235, connection should be refused.


  Which is dangerous and a security flaw, since this was meant (and used
  in a similar way with iptables and Ubuntu 14.04) to avoid revealing
  sensitive data over the internet (an application that is not able to
  use https should be tunneled). When firewall rules have been loaded
  and accepted without any warning, one would expect them to run.

  Ive tried to unload all iptables-related kernel packages and to load
  packages like nft_nat, nft_redir, nft_redir_ipv4, but the direct
  connection to port 80 still works although it shouldn't.

  No error warning, no message. It just allows outgoing port 80 although
  it shouldn't.

  Which is a problem, since this is security-relevant. If it doesn't
  work, it should spit out some error message.

  (FYI: It was implemented under Ubuntu 14.04 with

  iptables -t nat -I OUTPUT -d 1.2.3.4 -p tcp --dport 80 -j REDIRECT --to-port 
1234
  )

  
  My current guess: On that wiki page's bottem there's a hint that iptables and 
nft nat cannot be used at the same time. Unfortunately Ubuntu 15.10 still loads 
plenty of iptables stuff. Although I've tried to remove it all and it's kernel 
modules, I guess this could be a problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nftables 0.4-7
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct  7 15:21:36 2015
  InstallationDate: Installed on 2015-09-03 (33 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: nftables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1713017] Re: Enable MIDI support

[Andrew M]

Any chance this could be added? I know the last message is from 2017,
but there commercial products such as the Yamaha MD-BT01 Bluetooth
Wireless MIDI Adaptor that rely on this being enabled.

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

Title:
  Enable MIDI support

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Now that bluez has landed with 5.46-0ubuntu2, it would be nice to
  enable Bluetooth MIDI support. This did not seem to be enabled by
  default in the build from
  https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE
  MIDI devices, gatttool could talk to them, but no MIDI device was
  made; also ldd showed no linkage to libasound.so.2).

  After recompiling it with libasound2-dev installed and --enable-midi
  in debian/rules, it worked.

  Suggestion: add libasound2-dev to bluez dependencies, add --enable-
  midi to rules.

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

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

[Kernel-packages] [Bug 1815925] Re: wifi doesnt work.

[Anthony Wong]

I can't find any wireless device in your PCI bus, perhaps it's on USB.
Can you attach the output of 'lsusb -v' here?

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

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

Title:
  wifi doesnt work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  wifi card doesnt get detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 21:32:28 2019
  IwConfig: lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 009: ID 1018:1006
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash vt.handoff=1 
hid.ignore_special_drivers=1
  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.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: ilife.Wi314.NANNEBN09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZED AIR
  dmi.board.vendor: I-Life Digital Technologies LLC
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: 10.1 Tablet PC
  dmi.product.name: ZED AIR
  dmi.product.version: V1.00.01
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

[Kernel-packages] [Bug 1815808] Re: Thunderbolt Ethernet high-traffic exception

[Anthony Wong]

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

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

Title:
  Thunderbolt Ethernet high-traffic exception

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running iperf3 on Dell XP-15 with TB-10 Thunderbolt dock causes a
  kernel exception and ethernet failure after about 30 seconds.

  Easy to reproduce.  Connect to another machine via Gig-E and run
  iperf3 in either direction until the problem occurs.  Should run 900+
  Mb in either direction.  On one occasion I also lost the USB ports.
  However the display continues to work.

  
  # uname -a
  Linux hauser 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  # apt install iperf3
  # iperf3 -s

  
  # apt install iperf3
  # iperf3 -c my-machine -t 1000 # send to my machine
  # iperf3 -c my-machine -t 1000 -R  # receive data from my machine

  When the bitrate drops to zero, look in syslog for the exception.

  Note: Until recently the TB-10 Ethernet would not receive full speed.
  (prior to -43 kernel) Did not see this problem before the Ethernet
  performance increased.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1994 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 13 13:54:28 2019
  HibernationDevice: RESUME=UUID=d15ecb23-8691-42a1-9909-a56f934b536c
  InstallationDate: Installed on 2018-11-19 (86 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=a73e2d3e-5ce3-4130-917d-d116c1316153 ro net.ifnames=0 
mem_sleep_default=deep
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 02MJVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/25/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn02MJVY:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

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

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

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

[bugproxy]

--- Comment From pavsu...@in.ibm.com 2019-02-15 01:11 EDT---
I have installed all the packages as mentioned.

root@ltc-zz10:~# dpkg -i 
linux-modules-4.15.0-45-generic_4.15.0-45.48~16.04.1_ppc64el.deb
(Reading database ... 129194 files and directories currently installed.)
Preparing to unpack 
linux-modules-4.15.0-45-generic_4.15.0-45.48~16.04.1_ppc64el.deb ...
Unpacking linux-modules-4.15.0-45-generic (4.15.0-45.48~16.04.1) over 
(4.15.0-45.48~16.04.1) ...
Setting up linux-modules-4.15.0-45-generic (4.15.0-45.48~16.04.1) ...
Processing triggers for linux-image-unsigned-4.15.0-45-generic 
(4.15.0-45.48~16.04.1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
/etc/kernel/postinst.d/x-grub-legacy-ec2:
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Updating /boot/grub/menu.lst ... done

/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinux-4.15.0-45-generic
Found initrd image: /boot/initrd.img-4.15.0-45-generic
Found linux image: /boot/vmlinux-4.15.0-43-generic
Found initrd image: /boot/initrd.img-4.15.0-43-generic
done

root@ltc-zz10:~# dpkg -i 
linux-modules-extra-4.15.0-45-generic_4.15.0-45.48~16.04.1_ppc64el.deb
(Reading database ... 129185 files and directories currently installed.)
Preparing to unpack 
linux-modules-extra-4.15.0-45-generic_4.15.0-45.48~16.04.1_ppc64el.deb ...
Unpacking linux-modules-extra-4.15.0-45-generic (4.15.0-45.48~16.04.1) over 
(4.15.0-45.48~16.04.1) ...
Setting up linux-modules-extra-4.15.0-45-generic (4.15.0-45.48~16.04.1) ...
Processing triggers for linux-image-unsigned-4.15.0-45-generic 
(4.15.0-45.48~16.04.1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
/etc/kernel/postinst.d/x-grub-legacy-ec2:
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Updating /boot/grub/menu.lst ... done

/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinux-4.15.0-45-generic
Found initrd image: /boot/initrd.img-4.15.0-45-generic
Found linux image: /boot/vmlinux-4.15.0-43-generic
Found initrd image: /boot/initrd.img-4.15.0-43-generic
done

root@ltc-zz10:~# dpkg -i 
linux-image-unsigned-4.15.0-45-generic_4.15.0-45.48~16.04.1_ppc64el.deb
(Reading database ... 129175 files and directories currently installed.)
Preparing to unpack 
linux-image-unsigned-4.15.0-45-generic_4.15.0-45.48~16.04.1_ppc64el.deb ...
Unpacking linux-image-unsigned-4.15.0-45-generic (4.15.0-45.48~16.04.1) over 
(4.15.0-45.48~16.04.1) ...
Setting up linux-image-unsigned-4.15.0-45-generic (4.15.0-45.48~16.04.1) ...
Processing triggers for linux-image-unsigned-4.15.0-45-generic 
(4.15.0-45.48~16.04.1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
/etc/kernel/postinst.d/x-grub-legacy-ec2:
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Updating /boot/grub/menu.lst ... done

/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinux-4.15.0-45-generic
Found initrd image: /boot/initrd.img-4.15.0-45-generic
Found linux image: /boot/vmlinux-4.15.0-43-generic
Found initrd image: /boot/initrd.img-4.15.0-43-generic
done

Then rebooted the Linux HOST and executed the command again.

root@ltc-zz10:~# reboot

root@ltc-zz10:~# dpkg --list | grep linux-modules
ii  linux-modules-4.15.0-43-generic4.15.0-43.46~16.04.1 
  ppc64el  Linux kernel extra modules for version 4.15.0 on PowerPC 
64el SMP
ii  linux-modules-4.15.0-45-generic4.15.0-45.48~16.04.1 
  ppc64el  Linux kernel extra modules for version 4.15.0 on PowerPC 
64el SMP
ii  linux-modules-extra-4.15.0-43-generic  4.15.0-43.46~16.04.1 
  ppc64el  Linux kernel extra modules for version 4.15.0 on PowerPC 
64el SMP
ii  linux-modules-extra-4.15.0-45-generic  4.15.0-45.48~16.04.1 
  ppc64el  Linux kernel extra modules for version 4.15.0 on PowerPC 
64el SMP

root@ltc-zz10:~# dpkg --list | grep linux-image
ii  linux-image-4.15.0-43-generic  4.15.0-43.46~16.04.1 
  

[Kernel-packages] [Bug 1815925] Re: wifi doesnt work.

[ktb]

please find attached file.

In dmesg it does shows some error regading  (Broadcom network).

** Attachment added: "lsusb-v.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815925/+attachment/5238829/+files/lsusb-v.txt

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

Title:
  wifi doesnt work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  wifi card doesnt get detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 14 21:32:28 2019
  IwConfig: lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 009: ID 1018:1006
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash vt.handoff=1 
hid.ignore_special_drivers=1
  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.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: ilife.Wi314.NANNEBN09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZED AIR
  dmi.board.vendor: I-Life Digital Technologies LLC
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: 10.1 Tablet PC
  dmi.product.name: ZED AIR
  dmi.product.version: V1.00.01
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

[Kernel-packages] [Bug 1503695] Re: nft nat not working

[Launchpad Bug Tracker]

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

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

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

Title:
  nft nat not working

Status in linux package in Ubuntu:
  Expired
Status in nftables package in Ubuntu:
  Expired

Bug description:
  Hi ,

  I have installed an ubuntu 15.10 beta machine and configured nftables
  firewalling.

  While the regular firewalling works (using the default settings that
  come with the package), I found that nat rules are silently ignored.
  I've added this to the /etc/nftables.conf and read it:

  table ip nat {

chain prerouting {
  type nat hook prerouting priority 0;
  ip daddr 1.2.3.4 tcp dport 80 redirect to 1234
  tcp dport 80 redirect to 1235
}

chain postrouting {
  type nat hook postrouting priority 0;
} 

  }

  
  following the example from 

  http://wiki.nftables.org/wiki-
  nftables/index.php/Performing_Network_Address_Translation_%28NAT%29#Redirect

  (1.2.3.4 is just a placeholder for the address actually used here, i
  do not want to reveal the address to the bug report). nft reads this
  without complaining, and

  nft list table ip nat

  gives exactly that output (except for replacing 80 with "http"), so
  the configuration is read correctly.


  But it simply does not work. Without having any daemon listening on
  ports 1234, 1235 , traffic to port 80 works as usual. As long as there
  is not process waiting on 1234/1235, connection should be refused.


  Which is dangerous and a security flaw, since this was meant (and used
  in a similar way with iptables and Ubuntu 14.04) to avoid revealing
  sensitive data over the internet (an application that is not able to
  use https should be tunneled). When firewall rules have been loaded
  and accepted without any warning, one would expect them to run.

  Ive tried to unload all iptables-related kernel packages and to load
  packages like nft_nat, nft_redir, nft_redir_ipv4, but the direct
  connection to port 80 still works although it shouldn't.

  No error warning, no message. It just allows outgoing port 80 although
  it shouldn't.

  Which is a problem, since this is security-relevant. If it doesn't
  work, it should spit out some error message.

  (FYI: It was implemented under Ubuntu 14.04 with

  iptables -t nat -I OUTPUT -d 1.2.3.4 -p tcp --dport 80 -j REDIRECT --to-port 
1234
  )

  
  My current guess: On that wiki page's bottem there's a hint that iptables and 
nft nat cannot be used at the same time. Unfortunately Ubuntu 15.10 still loads 
plenty of iptables stuff. Although I've tried to remove it all and it's kernel 
modules, I guess this could be a problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nftables 0.4-7
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct  7 15:21:36 2015
  InstallationDate: Installed on 2015-09-03 (33 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: nftables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1808635] Re: [nouveau] [Quadro FX 3800] no boot just red square on screen

[Launchpad Bug Tracker]

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

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

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

Title:
  [nouveau] [Quadro FX 3800] no boot just red square on screen

Status in linux package in Ubuntu:
  Expired

Bug description:
  no boot just red squar on screan

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Dec 15 10:16:34 2018
  DistUpgraded: 2018-08-28 08:03:16,046 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GT200GL [Quadro FX 3800] [10de:05ff] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GT200GL [Quadro FX 3800] [10de:0661]
  InstallationDate: Installed on 2016-09-30 (806 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Z400 Workstation
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=2aeb5d71-8879-4ee6-8084-763dda365c5a ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-08-28 (109 days ago)
  dmi.bios.date: 07/15/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G3 v03.57
  dmi.board.asset.tag: 2UA935021D
  dmi.board.name: 0AE4h
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: C
  dmi.chassis.asset.tag: 2UA935021D
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G3v03.57:bd07/15/2013:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0AE4h:rvrC:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z400 Workstation
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Aug 28 22:26:33 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

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

[Kernel-packages] [Bug 1808677] Re: apt hangs when updating to inux-headers-4.18.0-12-generic

[Launchpad Bug Tracker]

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

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

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

Title:
  apt hangs when updating to inux-headers-4.18.0-12-generic

Status in linux package in Ubuntu:
  Expired

Bug description:
  When updating only the kernel it hangs:

  apt install --only-upgrade linux-generic
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
linux-headers-4.18.0-12 linux-headers-4.18.0-12-generic 
linux-headers-generic linux-image-4.18.0-12-generic linux-image-generic 
linux-modules-4.18.0-12-generic
linux-modules-extra-4.18.0-12-generic
  Suggested packages:
fdutils linux-doc-4.18.0 | linux-source-4.18.0 linux-tools
  The following NEW packages will be installed:
linux-headers-4.18.0-12 linux-headers-4.18.0-12-generic 
linux-image-4.18.0-12-generic linux-modules-4.18.0-12-generic 
linux-modules-extra-4.18.0-12-generic
  The following packages will be upgraded:
linux-generic linux-headers-generic linux-image-generic
  3 upgraded, 5 newly installed, 0 to remove and 148 not upgraded.
  Need to get 0 B/66,0 MB of archives.
  After this operation, 330 MB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Reading changelogs... Done
  Selecting previously unselected package linux-modules-4.18.0-12-generic.
  (Reading database ... 269826 files and directories currently installed.)
  Preparing to unpack 
.../0-linux-modules-4.18.0-12-generic_4.18.0-12.13_amd64.deb ...
  Unpacking linux-modules-4.18.0-12-generic (4.18.0-12.13) ...
  Selecting previously unselected package linux-image-4.18.0-12-generic.
  Preparing to unpack 
.../1-linux-image-4.18.0-12-generic_4.18.0-12.13_amd64.deb ...
  Unpacking linux-image-4.18.0-12-generic (4.18.0-12.13) ...
  Selecting previously unselected package linux-modules-extra-4.18.0-12-generic.
  Preparing to unpack 
.../2-linux-modules-extra-4.18.0-12-generic_4.18.0-12.13_amd64.deb ...
  Unpacking linux-modules-extra-4.18.0-12-generic (4.18.0-12.13) ...
  Preparing to unpack .../3-linux-generic_4.18.0.12.13_amd64.deb ...
  Unpacking linux-generic (4.18.0.12.13) over (4.18.0.11.12) ...
  Preparing to unpack .../4-linux-image-generic_4.18.0.12.13_amd64.deb ...
  Unpacking linux-image-generic (4.18.0.12.13) over (4.18.0.11.12) ...
  Selecting previously unselected package linux-headers-4.18.0-12.
  Preparing to unpack .../5-linux-headers-4.18.0-12_4.18.0-12.13_all.deb ...
  Unpacking linux-headers-4.18.0-12 (4.18.0-12.13) ...
  Selecting previously unselected package linux-headers-4.18.0-12-generic.
  Preparing to unpack 
.../6-linux-headers-4.18.0-12-generic_4.18.0-12.13_amd64.deb ...
  Unpacking linux-headers-4.18.0-12-generic (4.18.0-12.13) ...
  Preparing to unpack .../7-linux-headers-generic_4.18.0.12.13_amd64.deb ...
  Unpacking linux-headers-generic (4.18.0.12.13) over (4.18.0.11.12) ...
  Setting up linux-headers-4.18.0-12 (4.18.0-12.13) ...
  Setting up linux-modules-4.18.0-12-generic (4.18.0-12.13) ...
  Setting up linux-headers-4.18.0-12-generic (4.18.0-12.13) ...

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

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

[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )

[Natetronn]

Not sure I should chime in, since it's already been confirmed but, I'm
seeing this as well.

Says it's 100c in Disks and in Freon too.

$ sudo hddtemp /dev/sdb   
/dev/sdb: KINGSTON SA400S37240G: 26°C

I'm a bit too tired at this point to try and figure out how to address
the issue. I'll read the thread again in the morning.

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

Title:
  constantly shows wrong temperature (99°C )

Status in libatasmart:
  Unknown
Status in libatasmart package in Ubuntu:
  In Progress
Status in libatasmart source package in Trusty:
  Confirmed
Status in libatasmart source package in Xenial:
  Confirmed
Status in libatasmart source package in Yakkety:
  Confirmed

Bug description:
  Hello, here's my system info

  ~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ~$ apt-cache policy udisks2
  udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
   *** 2.1.7-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C 
(210°F), but in reality it's 30°C

  
  ~$ sudo smartctl -A /dev/sda
  smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART Attributes Data Structure revision number: 16
  Vendor Specific SMART Attributes with Thresholds:
  ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b   100   100   050Pre-fail  Always  
 -   0
9 Power_On_Hours  0x0012   100   100   000Old_age   Always  
 -   24
   12 Power_Cycle_Count   0x0012   100   100   000Old_age   Always  
 -   51
  168 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   0
  170 Unknown_Attribute   0x0003   100   100   010Pre-fail  Always  
 -   231
  173 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   65539
  192 Power-Off_Retract_Count 0x0012   100   100   000Old_age   Always  
 -   23
  194 Temperature_Celsius 0x0023   070   070   030Pre-fail  Always  
 -   30 (Min/Max 30/30)
  218 Unknown_Attribute   0x000b   100   100   050Pre-fail  Always  
 -   0
  231 Temperature_Celsius 0x0013   100   100   000Pre-fail  Always  
 -   99
  241 Total_LBAs_Written  0x0012   100   100   000Old_age   Always  
 -   337


  in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
  works well though:

  ~$ sudo hddtemp /dev/sda
  /dev/sda: PNY EU SSD CS1311 240GB: 30°C

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

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

[Kernel-packages] [Bug 1815312] Re: Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10 Cosmic)

[Anthony Wong]

Can you undo what you have done and then try the kernel at
http://people.canonical.com/~ypwong/lp1815312 to see if it fixes the
problem?

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

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.175.1
  Tags:  cosmic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  

[Kernel-packages] [Bug 1815776] Re: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build

[daniel CURTIS]

Hello.

There is a similar raport about failed 'nvidia_304' module build on
latest '-proposed' v4.4.0-143-generic kernel:

✗ https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-304/+bug/1815858

Mentioned issue happened on both: amd64 and i385/i686 architectures.

Best regards.

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

Title:
  nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed
  to build

Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  fails on latest kernel 134 on get_user_pages calls.  Arguments changed
  for the function between -142 and -143 kernels.

  common/inc/nv-mm.h includes a macro to deal with this problem, but it
  is not working.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-384 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-143-generic
  Date: Wed Feb 13 10:15:20 2019
  DuplicateSignature: 
dkms:nvidia-384:384.130-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-384/384.130/build/common/inc/nv-mm.h:49:35:
 error: too few arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2011-08-11 (2743 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageVersion: 384.130-0ubuntu0.16.04.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-384_hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1815776/+subscriptions

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

[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport

[Guilherme G. Piccoli]

You're welcome Putatieve, thanks for testing the Xenial 4.4.0-143
version!

And you're right, we will have a fix for Xenial-HWE - as soon it is available, 
you will observe a new message from Brad Figg here, this time adding a tag 
"verification-needed-bionic".
And then, likely the version for Xenial-HWE will be ready to test.

Notice the "likely" word above: happens that the build process is
usually parallel, with Bionic 4.15 and Xenial 4.15~16.04 at same time;
but there are small code changes (mostly toolchain related) between
Bionic 4.15 and Xenial-HWE, so it may happen that Bionic version is
ready before Xenial-HWE. It's likely to be at same time (or with some
hours of difference) though.

If you're interested in more knowledge about Ubuntu kernel cycles, I'd like to 
suggest you this interesting wiki page: 
https://wiki.ubuntu.com/Kernel/FAQ#Kernel.2FSupport.Ubuntu_Kernel_Release_Schedule
You can check the releases and also, how the HWE works (18.04 kernel 4.15 is 
present as a long-term supported HWE kernel for 16.04.5 version; same relation 
we observe between 16.04 and 14.04.5).

Feel free to expose any remaining questions you have - also, your testing when 
the 4.15 version gets released to -proposed is much appreciated!
Cheers,


Guilherme

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

Title:
  Userspace break as a result of missing patch backport

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Hi,

  The most recent set of Ubuntu kernels applied a variety of tty patches
  including:
  
https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b

  But have not applied the more recent
  
https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0
  patch.

  This second patch is required to prevent a rather serious regression
  where userspace applications reading from stdin can receive EAGAIN
  when they should not.

  I will try to link correspondence from the mailing list archives once
  they are available, but for now if you have access to the linux-
  console mailing list you can find discussion under the thread
  "Userspace break? read from STDIN returns EAGAIN if tty is "touched"".

  I would appreciate it if this could be examined soon as it is a
  regression on userspace.

  Thanks
  Michael

  
  Good:
  4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018

  
  Bad:
  4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019

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

-- 
Mailing list: https://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 1813873] Re: Userspace break as a result of missing patch backport

[Ulli Horlacher]

On Thu 2019-02-14 (10:46), SAMUEL TEIXEIRA SANTOS wrote:

> In my case I have two stations with ubuntu 18.04(bionic), both with
> linux-image-4.15.0-45-generic and linux-image-4.15.0-43-generic.
> 
> So, I wait or can I apply somehow the fix it?

Install linux-image-generic-hwe-18.04

This package has the bug-fix,

-- 
Ullrich Horlacher  Server und Virtualisierung
Rechenzentrum TIK 
Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de
Allmandring 30aTel:++49-711-68565868
70569 Stuttgart (Germany)  WWW:http://www.tik.uni-stuttgart.de/
REF:<155014120837.28446.2912150246365160313.mal...@chaenomeles.canonical.com>

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

Title:
  Userspace break as a result of missing patch backport

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Hi,

  The most recent set of Ubuntu kernels applied a variety of tty patches
  including:
  
https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b

  But have not applied the more recent
  
https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0
  patch.

  This second patch is required to prevent a rather serious regression
  where userspace applications reading from stdin can receive EAGAIN
  when they should not.

  I will try to link correspondence from the mailing list archives once
  they are available, but for now if you have access to the linux-
  console mailing list you can find discussion under the thread
  "Userspace break? read from STDIN returns EAGAIN if tty is "touched"".

  I would appreciate it if this could be examined soon as it is a
  regression on userspace.

  Thanks
  Michael

  
  Good:
  4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018

  
  Bad:
  4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019

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

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

[Kernel-packages] [Bug 1814733] Re: linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Wednesday, 13. February 2019 14:03 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages copies requested
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   snap-release-to-beta: Pending -- snap not in 18/beta channel
+   snap-release-to-edge: Pending -- snap not in 18/edge channel
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Wednesday, 13. February 2019 14:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1813604] Re: Lineout and headphones audio keep switching automatically -- broken audio

[JP]

Is there any way to "bump this up"?

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

Title:
  Lineout and headphones audio keep switching automatically -- broken
  audio

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have been a long-term Ubuntu user (since 10.04) and take pride in
  having fixed all problems on my own thanks to the excellent
  documentation, but this time I am utterly stumped and have run out of
  ideas (hence this report).

  With my headphones jacked in, the line out and headphones output
  options keep switching automatically, resulting in crackling (and
  broken audio).  I have tried many solutions I found online but none of
  the suggested fixes work.  I am attaching a video of what I see (note
  that this happens automatically, I don't click anywhere)

  This is not a hardware issue (the headphones work fine on another
  machine running Ubuntu 16.04, and as far as I'm aware this problem
  only appeared after I upgraded from 16.04 to 18.04).

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  I have uploaded two different videos showing what I see here:
  https://youtu.be/S49cEC5DRsk
  https://youtu.be/zSfi5ko5nBY
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jp 5422 F pulseaudio
   /dev/snd/controlC1:  jp 5422 F pulseaudio
   /dev/snd/controlC2:  jp 5422 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=84a04536-72b0-461c-99b3-6dd8190bd471
  InstallationDate: Installed on 2016-05-12 (992 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   docker0   no wireless extensions.
   
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic 
root=UUID=38883a30-ab46-453d-af78-cd67fe68236b ro quiet splash acpi=force
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-44-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-23 (159 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0601
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0601:bd01/26/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  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/1813604/+subscriptions

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

[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport

[Guilherme G. Piccoli]

Samuel, for now the suggestion is to keep kernel 4.15.0-43, as it
doesn't show the issue reported in this LP.

Soon (probably later today or tomorrow) the new version for 4.15 will
show up in -proposed pocket, so you can update to that version for
testing purposes, since that version will have the fix for the issue
reported here.

Cheers,


Guilherme

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

Title:
  Userspace break as a result of missing patch backport

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Hi,

  The most recent set of Ubuntu kernels applied a variety of tty patches
  including:
  
https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b

  But have not applied the more recent
  
https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0
  patch.

  This second patch is required to prevent a rather serious regression
  where userspace applications reading from stdin can receive EAGAIN
  when they should not.

  I will try to link correspondence from the mailing list archives once
  they are available, but for now if you have access to the linux-
  console mailing list you can find discussion under the thread
  "Userspace break? read from STDIN returns EAGAIN if tty is "touched"".

  I would appreciate it if this could be examined soon as it is a
  regression on userspace.

  Thanks
  Michael

  
  Good:
  4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018

  
  Bad:
  4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019

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

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

[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport

[SAMUEL TEIXEIRA SANTOS]

Hi all.

I'm following your discussion, but I couldn't realize if I can fix or
just waiting the fix.

In my case I have two stations with ubuntu 18.04(bionic), both with
linux-image-4.15.0-45-generic and linux-image-4.15.0-43-generic.

So, I wait or can I apply somehow the fix it?

All this is very new to me, sorry


Regards,


Samuel

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

Title:
  Userspace break as a result of missing patch backport

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Hi,

  The most recent set of Ubuntu kernels applied a variety of tty patches
  including:
  
https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b

  But have not applied the more recent
  
https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0
  patch.

  This second patch is required to prevent a rather serious regression
  where userspace applications reading from stdin can receive EAGAIN
  when they should not.

  I will try to link correspondence from the mailing list archives once
  they are available, but for now if you have access to the linux-
  console mailing list you can find discussion under the thread
  "Userspace break? read from STDIN returns EAGAIN if tty is "touched"".

  I would appreciate it if this could be examined soon as it is a
  regression on userspace.

  Thanks
  Michael

  
  Good:
  4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018

  
  Bad:
  4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019

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

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

[Kernel-packages] [Bug 1762719] Re: System Z {kernel} UBUNTU18.04 wrong kernel config

[Frank Heimes]

Since this bug was already successfully verified, I'm adjusting the tags
accordingly ...

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

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

Title:
  System Z {kernel} UBUNTU18.04 wrong kernel config

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic)
  is not OK, because both security mechanisms nobp AND expoline are
  enabled:

  CONFIG_KERNEL_NOBP=y
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  If the kernel is compiled with a gcc that can generate expoline thunks
  the correct config is as follows:

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  Alternatively the auto-detection patch can be used which is upstream
  as of today:

  commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

  s390: add automatic detection of the spectre defense
  
  Automatically decide between nobp vs. expolines if the spectre_v2=auto
  kernel parameter is specified or CONFIG_EXPOLINE_AUTO=y is set.
  
  The decision made at boot time due to CONFIG_EXPOLINE_AUTO=y being set
  can be overruled with the nobp, nospec and spectre_v2 kernel parameters.
  
  If this patch is used, then the correct config is

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  CONFIG_EXPOLINE_AUTO=y
  # CONFIG_EXPOLINE_FULL is not set

  This patch goes together with three others, so a total of four patches
  would be needed for the latest-and-greated solution:

  b2e2f43a01bace1a25bdbae04c9f9846882b727a
  6e179d64126b909f0b288fa63cdbf07c531e9b1d
  bc035599718412cfba9249aa713f90ef13f13ee9
  d424986f1d6b16079b3231db0314923f4f8deed1

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

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

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

[Kleber Sacilotto de Souza]

** Summary changed:

- linux-lts-trusty:  -proposed tracker
+ linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  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-dnu 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:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814645
  phase: Packaging
  phase-changed: Thursday, 07. February 2019 14:34 UTC
  reason:
prepare-package: Pending -- version not specified

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

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

[Kernel-packages] [Bug 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  == Justification ==
  Commit b2d35fa5fc80 ("selftests: add headers_install to lib.mk")
  introduced a requirement that Makefiles more than one level below the
  selftests directory need to define top_srcdir, but it didn't update
  any of the powerpc Makefiles.

  This broke building all the powerpc selftests with eg:

    make[1]: Entering directory '/src/linux/tools/testing/selftests/powerpc'
    BUILD_TARGET=/src/linux/tools/testing/selftests/powerpc/alignment; mkdir -p 
$BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
    make[2]: Entering directory 
'/src/linux/tools/testing/selftests/powerpc/alignment'
    ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory
    make[2]: *** No rule to make target '../../../../scripts/subarch.include'.
    make[2]: Failed to remake makefile '../../../../scripts/subarch.include'.
    Makefile:38: recipe for target 'alignment' failed

  == Fix ==
  7e0cf1c983b5 (selftests/powerpc: Fix Makefiles for headers_install change)
  It can be cherry-picked for Cosmic. And it's already landed in Disco.

  == Regression Potential ==
  None, this just fixes the broken build issue for the test. Nothing else will 
be affected.

  
  ===
  This test passed with 4.18.0-12 on the last cycle [1]
  But failed with the proposed 4.18.0-13 this time.

  Test failed to build because of a missing include file:
  50.   ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory

  Tried to reproduce this cycle with 4.18.0-12 first and this can be
  reproduced as well.

  39.   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
  40.   
BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment;
 mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
  41.   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  42.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned
  43.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned
  44.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned
  45.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned
  46.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 alignment_handler.c 

[Kernel-packages] [Bug 1789436] Re: pmtu.sh fails on 4.18 kernel

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  pmtu.sh fails on 4.18 kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  pmtu.sh is a network selftest that was introduced on 4.17. It is
  currently failing on 4.18. After revert of ccd740cbc6 "vti6: Add pmtu
  handling to vti6_xmit.", it passes.

  The fail is in the nature of holding netdevices refcounts, so some
  network operations start hanging, including the loading and removal of
  network modules.

  [  159.936543] unregister_netdevice: waiting for veth_b to become
  free. Usage count = 1

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

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

[Kernel-packages] [Bug 1806766] Re: [Regression] crashkernel fails on HiSilicon D05

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [Regression] crashkernel fails on HiSilicon D05

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  kdump support isn't usable on HiSilicon D05 systems. This previously worked 
in bionic.

  [Test Case]
  sudo apt install linux-crashdump
  echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT 
crashkernel=512M"' | \
    sudo tee /etc/default/grub.d/kdump-tools.cfg
  sudo update-grub
  sudo reboot
  echo 1 | sudo tee /proc/sys/kernel/sysrq
  echo c | sudo tee /proc/sysrq-trigger

  On failure:
  [2.362261] [ cut here ]
  [2.362263] [CRTC:29:crtc-0] vblank wait timed out
  [2.362294] WARNING: CPU: 0 PID: 143 at 
drivers/gpu/drm/drm_atomic_helper.c:1386 
drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 [drm_kms_helper]
  [2.362295] Modules linked in: hibmc_drm(+) ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm hisi_sas_v2_hw(+) hisi_sas_main 
ehci_platform libsas scsi_transport_sas
  [2.362309] CPU: 0 PID: 143 Comm: systemd-udevd Tainted: G C   
 4.19.0-7-generic #8-Ubuntu
  [2.362310] Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.50 
06/01/2018
  [2.362312] pstate: 6045 (nZCv daif +PAN -UAO)
  [2.362324] pc : drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 
[drm_kms_helper]
  [2.362335] lr : drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 
[drm_kms_helper]
  [2.362336] sp : 0a2fb1f0
  [2.362337] x29: 0a2fb1f0 x28: 0001 
  [2.362339] x27:  x26: 0001 
  [2.362342] x25: 0038 x24: 8000208c5800 
  [2.362344] x23:  x22: 0001 
  [2.362346] x21: 80001eebb818 x20: 800025b18600 
  [2.362349] x19:  x18: 0001 
  [2.362351] x17:  x16:  
  [2.362353] x15:  x14: 09848708 
  [2.362355] x13: 0074 x12: 09a12000 
  [2.362357] x11: 0986d000 x10: 09a122f8 
  [2.362359] x9 : 0001 x8 : 09a15104 
  [2.362361] x7 :  x6 : 004ce5700bb7 
  [2.362363] x5 : 00ff x4 :  
  [2.362365] x3 :  x2 :  
  [2.362367] x1 : 0b15ae454042e100 x0 :  
  [2.362370] Call trace:
  [2.362381]  drm_atomic_helper_wait_for_vblanks.part.9+0x280/0x290 
[drm_kms_helper]
  [2.362392]  drm_atomic_helper_commit_tail+0x68/0x80 [drm_kms_helper]
  [2.362402]  commit_tail+0x7c/0x80 [drm_kms_helper]
  [2.362413]  drm_atomic_helper_commit+0xd8/0x150 [drm_kms_helper]
  [2.362440]  drm_atomic_commit+0x54/0x60 [drm]
  [2.362451]  restore_fbdev_mode_atomic+0x184/0x1f8 [drm_kms_helper]
  [2.362461]  restore_fbdev_mode+0x48/0x190 [drm_kms_helper]
  [2.362472]  drm_fb_helper_restore_fbdev_mode_unlocked+0x78/0xd8 
[drm_kms_helper]
  [2.362482]  drm_fb_helper_set_par+0x34/0x60 [drm_kms_helper]
  [2.362488]  fbcon_init+0x3ac/0x4f0
  [2.362491]  visual_init+0xb8/0x110
  [2.362492]  do_bind_con_driver+0x1ec/0x3a8
  [2.362494]  do_take_over_console+0x148/0x208
  [2.362495]  do_fbcon_takeover+0x70/0xd8
  [2.362497]  fbcon_event_notify+0x838/0x8a8
  [2.362501]  notifier_call_chain+0x5c/0x98
  [2.362502]  blocking_notifier_call_chain+0x64/0x88
  [2.362504]  fb_notifier_call_chain+0x30/0x40
  [2.362506]  register_framebuffer+0x22c/0x328
  [2.362516]  __drm_fb_helper_initial_config_and_unlock+0x210/0x408 
[drm_kms_helper]
  [2.362526]  drm_fb_helper_initial_config+0x4c/0x58 [drm_kms_helper]
  [2.362530]  hibmc_fbdev_init+0x88/0x190 [hibmc_drm]
  [2.362534]  hibmc_pci_probe+0x228/0x3c8 [hibmc_drm]
  [2.362537]  local_pci_probe+0x44/0xa8
  [2.362539]  pci_device_probe+0x194/0x1a8
  [2.362541]  really_probe+0x21c/0x3b8
  [2.362543]  driver_probe_device+0xe4/0x138
  [2.362544]  __driver_attach+0xe4/0x150
  

[Kernel-packages] [Bug 1814651] Re: linux-aws: 4.4.0-1076.86 -proposed tracker

[Brad Figg]

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814647
- phase: Packaging
- phase-changed: Thursday, 07. February 2019 08:05 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 14. February 2019 11:31 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete

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

Title:
  linux-aws: 4.4.0-1076.86 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  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: 1814647
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 14. February 2019 11:31 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete

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

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

[Kernel-packages] [Bug 1762719] Re: System Z {kernel} UBUNTU18.04 wrong kernel config

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  System Z {kernel} UBUNTU18.04 wrong kernel config

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Kernel config 4.15.0-13-generic #14 (and same for 4.15.0-15-generic)
  is not OK, because both security mechanisms nobp AND expoline are
  enabled:

  CONFIG_KERNEL_NOBP=y
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  If the kernel is compiled with a gcc that can generate expoline thunks
  the correct config is as follows:

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  # CONFIG_EXPOLINE_MEDIUM is not set
  CONFIG_EXPOLINE_FULL=y

  Alternatively the auto-detection patch can be used which is upstream
  as of today:

  commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

  s390: add automatic detection of the spectre defense
  
  Automatically decide between nobp vs. expolines if the spectre_v2=auto
  kernel parameter is specified or CONFIG_EXPOLINE_AUTO=y is set.
  
  The decision made at boot time due to CONFIG_EXPOLINE_AUTO=y being set
  can be overruled with the nobp, nospec and spectre_v2 kernel parameters.
  
  If this patch is used, then the correct config is

  # CONFIG_KERNEL_NOBP is not set
  CONFIG_EXPOLINE=y
  # CONFIG_EXPOLINE_OFF is not set
  CONFIG_EXPOLINE_AUTO=y
  # CONFIG_EXPOLINE_FULL is not set

  This patch goes together with three others, so a total of four patches
  would be needed for the latest-and-greated solution:

  b2e2f43a01bace1a25bdbae04c9f9846882b727a
  6e179d64126b909f0b288fa63cdbf07c531e9b1d
  bc035599718412cfba9249aa713f90ef13f13ee9
  d424986f1d6b16079b3231db0314923f4f8deed1

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

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

[Kernel-packages] [Bug 1762755] Re: Support cq/rq record doorbell for RDMA on HSilicon hip08 systems

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Support cq/rq record doorbell for RDMA on HSilicon hip08 systems

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  HiSilicon hip08 systems support a cq/rq record feature for RDMA that
  is currently not supported by the kernel.

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

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

[Kernel-packages] [Bug 1759791] Re: NFS + sec=krb5 is broken

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  NFS + sec=krb5 is broken

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  I am testing the development branch of Bionic Beaver.
  With the latest update to kernel 4.15.0-13 my nfs-mounts in a university 
network are broken.

  > sudo mount -vvv -t nfs4 my_server:/my/share  /nfs -osoft,sec=krb5
  > mount.nfs4: timeout set for Mon Mar 26 16:29:56 2018
  > mount.nfs4: trying text-based options 
'soft,sec=krb5,nfsvers=4.0,addr=10.162.229.2,clientaddr=10.152.249.189'
  > mount.nfs4: mount(2): Input/output error
  > mount.nfs4: mount system call failed

  > kernel: NFS: nfs4_discover_server_trunking unhandled error -5. Exiting with 
error EIO
  > kernel: RPC: couldn't encode RPC header, exit EIO
  > kernel: gss_marshal: gss_get_mic FAILED (851968)

  
  Known good version: linux-image-4.15.0-10

  I think it is the same bug like in 
https://bugzilla.redhat.com/show_bug.cgi?id=1558977
  The bug was introduced in the mainline kernel 4.15.4 with commit 
"[46e8d06e423c4f35eac7a8b677b713b3ec9b0684] crypto: hash - prevent using keyed 
hashes without setting key"

  This bug should be fixed before releasing ubuntu18.04 by either reverting the 
commit or using a fixed mainline kernel.
  --- 
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1340 F pulseaudio
   /dev/snd/controlC0:  gdm1340 F pulseaudio
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-22 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046a:b091 Cherry GmbH 
   Bus 001 Device 002: ID 0bf8:101e Fujitsu Siemens Computers 
   Bus 001 Device 004: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: FUJITSU ESPRIMO D757
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=463c4c1b-7771-40dd-833f-f4d68a5fd914 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  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.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UnreportableReason: Der Bericht gehört zu einem nicht installierten Paket.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 10/12/2017
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V5.0.0.12 R1.14.0 for D3531-A1x
  dmi.board.name: D3531-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3531-A1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.14.0forD3531-A1x:bd10/12/2017:svnFUJITSU:pnESPRIMOD757:pvr:rvnFUJITSU:rnD3531-A1:rvrS26361-D3531-A1:cvnFUJITSU:ct3:cvr:
  dmi.product.family: ESPRIMO-FTS
  dmi.product.name: ESPRIMO D757
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1815451] Re: Move bionic/linux-azure to 4.18

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Move bionic/linux-azure to 4.18

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Xenial:
  In Progress
Status in linux-azure source package in Bionic:
  In Progress

Bug description:
  The azure kernel in Bionic will be moved to 4.18 for the point
  release.

  That also affects linux-azure-edge (that will be a meta only package)
  and xenial/linux-azure as well, since it will not be a backport of
  bionic/linux-azure anymore.

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

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

[Kernel-packages] [Bug 1815776] Re: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed
  to build

Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  fails on latest kernel 134 on get_user_pages calls.  Arguments changed
  for the function between -142 and -143 kernels.

  common/inc/nv-mm.h includes a macro to deal with this problem, but it
  is not working.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-384 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-143-generic
  Date: Wed Feb 13 10:15:20 2019
  DuplicateSignature: 
dkms:nvidia-384:384.130-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-384/384.130/build/common/inc/nv-mm.h:49:35:
 error: too few arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2011-08-11 (2743 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageVersion: 384.130-0ubuntu0.16.04.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-384_hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1815776/+subscriptions

-- 
Mailing list: https://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 1815561] Re: touchpad not recognized

[ktb]

Yes the touchpad works now by inserting hid.ignore_special_drivers=1
 just after "quite splash"

Thanks.

On Thu, 14 Feb 2019, 10:45 am Anthony Wong  Can you attach dmesg output to this bug when you boot with that kernel
> param added?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1815561
>
> Title:
>   touchpad not recognized
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   touchpad not recognized.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.15.0-45-generic 4.15.0-45.48
>   ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
>   Uname: Linux 4.15.0-45-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p',
> '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1',
> '/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p',
> '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit
> code 1:
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Feb 12 02:25:52 2019
>   MachineType: I-Life Digital Technologies LLC ZED AIR
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
> root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash vt.handoff=1
>   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.15.0-45-generic N/A
>linux-backports-modules-4.15.0-45-generic  N/A
>linux-firmware 1.173.3
>   RfKill:
>0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/20/2016
>   dmi.bios.vendor: INSYDE Corp.
>   dmi.bios.version: ilife.Wi314.NANNEBN09
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: ZED AIR
>   dmi.board.vendor: I-Life Digital Technologies LLC
>   dmi.board.version: Type2 - Board Version
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Chassis Manufacturer
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnINSYDECorp.:bvrilife.Wi314.NANNEBN09:bd08/20/2016:svnI-LifeDigitalTechnologiesLLC:pnZEDAIR:pvrV1.00.01:rvnI-LifeDigitalTechnologiesLLC:rnZEDAIR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
>   dmi.product.family: 10.1 Tablet PC
>   dmi.product.name: ZED AIR
>   dmi.product.version: V1.00.01
>   dmi.sys.vendor: I-Life Digital Technologies LLC
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815561/+subscriptions
>

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

Title:
  touchpad not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  touchpad not recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 02:25:52 2019
  MachineType: I-Life Digital Technologies LLC ZED AIR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=8e451b7e-1777-4606-a6af-3218b2a90d72 ro quiet splash vt.handoff=1
  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.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2016
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: ilife.Wi314.NANNEBN09
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZED AIR
  dmi.board.vendor: I-Life Digital Technologies LLC
  dmi.board.version: Type2 - Board Version
  

[Kernel-packages] [Bug 1814325] Re: Keyboard light fn does not works for Asus VivoBook S14 X430UA on Ubuntu 18.04

[Anthony Wong]

Looks like this feature has been added to linux kernel after v4.19.
Do you know how many levels of backlit the keyboard has?

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

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

Title:
  Keyboard light fn does not works for Asus VivoBook S14 X430UA on
  Ubuntu 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I started using Ubuntu in my new Asus VivoBook S14 X430UA laptop. But
  it is very disappointing that the keyboard light cannot be controlled
  using the dedicated switch (fn + f7). Similarly fn + f8 also not
  working, which is for screen toggling.

  echo 3 | sudo tee /sys/class/leds/asus::kbd_backlight/brightness

  command to switch on the keyboard light is working fine. Is there any
  solution for this issue?

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajithabhks   1491 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  2 01:25:22 2019
  HibernationDevice: RESUME=UUID=29048cc5-d306-4844-8f70-c87fc7a20081
  InstallationDate: Installed on 2019-01-31 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:56c1 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook S14 X430UA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=911bc958-ea13-4f07-9757-ce3a56799271 ro quiet splash acpi_osi=Linux 
acpi_backlight=vendor vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X430UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X430UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX430UA.204:bd06/06/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookS14X430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook S
  dmi.product.name: VivoBook S14 X430UA
  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/1814325/+subscriptions

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

[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport

[Putatieve Prins]

Hi Guilherme,

Thanks for your response. I was under the impression that there would
also be fix in 'proposed' for Xenial-HWE.

I can confirm that the issue is fixed in 4.4.0-143 (and indeed present
in 4.4.0-142).

Best,

W;-)

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

Title:
  Userspace break as a result of missing patch backport

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Hi,

  The most recent set of Ubuntu kernels applied a variety of tty patches
  including:
  
https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b

  But have not applied the more recent
  
https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0
  patch.

  This second patch is required to prevent a rather serious regression
  where userspace applications reading from stdin can receive EAGAIN
  when they should not.

  I will try to link correspondence from the mailing list archives once
  they are available, but for now if you have access to the linux-
  console mailing list you can find discussion under the thread
  "Userspace break? read from STDIN returns EAGAIN if tty is "touched"".

  I would appreciate it if this could be examined soon as it is a
  regression on userspace.

  Thanks
  Michael

  
  Good:
  4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018

  
  Bad:
  4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019

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

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

[Kernel-packages] [Bug 1814759] Re: linux-gcp: 4.18.0-1007.8 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
- phase: Packaging
- phase-changed: Friday, 08. February 2019 01:08 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 14. February 2019 09:09 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete

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

Title:
  linux-gcp: 4.18.0-1007.8 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814749
  phase: Holding before Promote to Proposed
  phase-changed: Thursday, 14. February 2019 09:09 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete

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

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

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

[Brad Figg]

** Changed in: kernel-sru-workflow/upload-to-ppa-dnu
   Status: New => Invalid

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814645
  phase: Packaging
  phase-changed: Thursday, 07. February 2019 14:34 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  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-dnu series:
  Invalid
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:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814645
  phase: Packaging
  phase-changed: Thursday, 07. February 2019 14:34 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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

[Kernel-packages] [Bug 1814644] Re: linux: -proposed tracker

[Kleber Sacilotto de Souza]

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Invalid

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-lbm series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid

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

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

  backports: 
  derivatives:
  -- swm properties --
  phase: Packaging
  phase-changed: Tuesday, 05. February 2019 10:01 UTC
  reason:
prepare-package: Pending -- version not specified

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

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

[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"

[Guilherme G. Piccoli]

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira 
(halves)

** Changed in: makedumpfile (Ubuntu Bionic)
 Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira 
(halves)

** Changed in: makedumpfile (Ubuntu Cosmic)
 Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira 
(halves)

** Changed in: makedumpfile (Ubuntu Disco)
 Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira 
(halves)

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

Title:
  Replace "nousb" option in kdump command-line for the newer
  "usbcore.nousb"

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Disco:
  Confirmed

Bug description:
  Since kernel v4.5, the correct parameter to disable USB subsystem
  initialization is "usbcore.nousb" always (instead of "nousb" in case
  the subsystem is built-in). This was changed by commit 097a9ea0e48
  ("usb: make "nousb" a clear module parameter").

  We need to take this into account in kdump-tools, or else we may boot
  with USB in kdump even the command-line saying the opposite.

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

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

[Kernel-packages] [Bug 1813866] Re: CONFIG_SECURITY_SELINUX_DISABLE should be disabled on 4.15/4.18 Azure

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  CONFIG_SECURITY_SELINUX_DISABLE should be disabled on 4.15/4.18 Azure

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  The test_081_config_security_selinux_disable test failed on the Trusty
  Azure kernel:

  FAIL: test_081_config_security_selinux_disable 
(__main__.KernelSecurityConfigTest)
  Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
  --
  Traceback (most recent call last):
  File "./test-kernel-security.py", line 2152, in 
test_081_config_security_selinux_disable
  self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
  File "./test-kernel-security.py", line 209, in assertKernelConfig
  self.assertKernelConfigUnset(name)
  File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
  '%s option was expected to be unset in the kernel config' % name)
  AssertionError: SECURITY_SELINUX_DISABLE option was expected to be unset in 
the kernel config

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813866/+subscriptions

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

[Kernel-packages] [Bug 1808353] Re: Blacklist Realtek Virtual IPMI device

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1807333] Re: Add support for 0cf3:535b QCA_ROME device

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1806850] Re: Fix Terminus USB hub that may breaks connected USB devices after S3

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1806818] Re: Fix Intel I210 doesn't work when ethernet cable gets plugged

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1762353] Re: [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed' when setting up a second end-to-end encrypted disk

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on  failed'
  when setting up a second end-to-end encrypted disk

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  Environment: z14 VM Guest system with one CEX6C CCA coprocessor
  in toleration mode (i.e. CEX6 HW presented as CEX5)
  OS: Ubuntu 18.04 Prerelease
  Setting up a second dm-crypt device using protected CCA paes-xts keys fails.
  The problem is reproducible.

  Details
  ===
  Setting up two or more plain end-to-end encrypted disks using 'cryptsetup'
  fails when using a cipher based on the protected key mechanism.
  The setup needs the paes and pkey modules loaded, the former providing the
  paes-xts-plain64 cipher (cat /proc/crpyto |grep paes).

  A second attempt to establish an end-to-end encrypted disk fails
  with : "device-mapper: reload ioctl on failed: No such file or directory."

  The problem is independent of the second encrypted disk being based on
  a second DASD or second partition on one DASD.

  ---uname output---
  Linux s3514004 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:56 UTC 2018 
s390x s390x s390x GNU/Linux

  ---Steps to Reproduce---
  1.) The following cryptsetup statement works, and is the first one I issued.
  cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher 
paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part1 enc-pv1
  2.) After this successful statement, I issued the following:
  cryptsetup plainOpen --key-file securekey.bin --key-size 1024 --cipher 
paes-xts-plain64 /dev/disk/by-path/ccw-0.0.-part2 enc-pv2
  device-mapper: reload ioctl on failed: No such file or directory.

  See attached patch (comment #1) as fix.

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

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

[Kernel-packages] [Bug 1756094] Re: [Bionic][ARM64] PCI and SAS driver patches for hip08 SoCs

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [Bionic][ARM64] PCI and SAS driver patches for hip08 SoCs

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Following patches are required to boot and install Bionic on hip08 soc
  based server reference board.

  Bjorn Helgaas (4):
PCI/ASPM: Calculate LTR_L1.2_THRESHOLD from device characteristics
PCI/ASPM: Enable Latency Tolerance Reporting when supported
PCI/ASPM: Unexport internal ASPM interfaces
PCI: Make PCI_SCAN_ALL_PCIE_DEVS work for Root as well as Downstream 
Ports

  Keith Busch (2):
PCI/AER: Return error if AER is not supported
PCI/DPC: Enable DPC only if AER is available

  Rafael J. Wysocki (2):
PM / core: Add LEAVE_SUSPENDED driver flag
PCI / PM: Support for LEAVE_SUSPENDED driver flag

  Tyler Baicar (1):
PCI/AER: Skip recovery callbacks for correctable errors from ACPI APEI

  Wei Yongjun (1):
scsi: hisi_sas: make local symbol host_attrs static

  Xiang Chen (8):
scsi: hisi_sas: fix dma_unmap_sg() parameter
scsi: hisi_sas: modify hisi_sas_dev_gone() for reset
scsi: hisi_sas: change ncq process for v3 hw
scsi: hisi_sas: add some print to enhance debugging
scsi: hisi_sas: fix SAS_QUEUE_FULL problem while running IO
scsi: hisi_sas: re-add the lldd_port_deformed()
scsi: hisi_sas: add v3 hw suspend and resume
scsi: hisi_sas: fix a bug in hisi_sas_dev_gone()

  Xiaofei Tan (11):
scsi: hisi_sas: relocate clearing ITCT and freeing device
scsi: hisi_sas: optimise port id refresh function
scsi: hisi_sas: some optimizations of host controller reset
scsi: hisi_sas: add an mechanism to do reset work synchronously
scsi: hisi_sas: add RAS feature for v3 hw
scsi: hisi_sas: improve int_chnl_int_v2_hw() consistency with v3 hw
scsi: hisi_sas: add v2 hw port AXI error handling support
scsi: hisi_sas: use an general way to delay PHY work
scsi: hisi_sas: do link reset for some CHL_INT2 ints
scsi: hisi_sas: judge result of internal abort
scsi: hisi_sas: add internal abort dev in some places
  chenxiang (4):
scsi: ata: enhance the definition of SET MAX feature field value
scsi: hisi_sas: Change frame type for SET MAX commands
UBUNTU: SAUCE: scsi: hisi_sas: config for hip08 ES
UBUNTU: SAUCE: scsi: hisi_sas: export device table of v3 hw to userspace

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

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

[Kernel-packages] [Bug 1783964] Re: Please make CONFIG_PWM_LPSS_PCI and CONFIG_PWM_LPSS_PLATFORM built in to make brightness adjustment working on various BayTrail/CherryTrail-based devices

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Please make CONFIG_PWM_LPSS_PCI and CONFIG_PWM_LPSS_PLATFORM built in
  to make brightness adjustment working on various BayTrail/CherryTrail-
  based devices

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Hello!

  Building kernel with following option should make brightness
  adjustment working on various Intel BayTrail and CherryTrail-based
  devices such as HP Stream 7 Tablet, Microsoft Surface 3, and quite a
  few tablets from ASUS, and many no-name Chinese companies.

  CONFIG_PWM_LPSS=y
  CONFIG_PWM_LPSS_PCI=y
  CONFIG_PWM_LPSS_PLATFORM=y

  I tested this change on HP Stream 7, by installing Linux 4.18rc6 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/ and then
  installing same kernel, but with built in CONFIG_PWM_LPSS modules
  listed above.

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

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

[Kernel-packages] [Bug 1751021] Re: retpoline abi files are empty on i386

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  retpoline abi files are empty on i386

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  The .retpoline files in the current abi are actually blank.
  This is due to incorrect handling in retpoline-extract.

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

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

[Kernel-packages] [Bug 1755158] Re: Fix ARC hit rate

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Fix ARC hit rate

Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  Upstream commit:
  
https://github.com/zfsonlinux/zfs/pull/6989/commits/e0014d56c3c21d53a71c436d54e10a456acb190d

  "When the compressed ARC feature was added in commit d3c2ae1
  the method of reference counting in the ARC was modified.  As
  part of this accounting change the arc_buf_add_ref() function
  was removed entirely.

  This would have be fine but the arc_buf_add_ref() function
  served a second undocumented purpose of updating the ARC access
  information when taking a hold on a dbuf.  Without this logic
  in place a cached dbuf would not migrate its associated
  arc_buf_hdr_t to the MFU list.  This would negatively impact
  the ARC hit rate, particularly on systems with a small ARC."

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

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

[Kernel-packages] [Bug 1814393] Re: "make: write error: stdout" on parallel builds

[Leo Soares]

I can confirm that this does not happen via ssh.

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

Title:
  "make: write error: stdout" on parallel builds

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  - Release of Ubuntu: 18.04.1 LTS (Kubuntu).
  - Package version: linux-image-4.15.0-44-generic, 
linux-image-4.15.0-45-generic.
  - Expected outcome: Large parallel make build completing properly.
  - What happened instead: Build stops with "make: write error: stdout".

  Full explanation:

  Since the update to kernel 4.15.0-44 (linux-image-4.15.0-44-generic)
  in Kubuntu Bionic I'm experiencing issues in my ThinkPad P52 laptop
  during large parallel builds of source code (eg: a buildroot full
  rebuild for a work project). Note that this reports isn't about kernel
  builds, but about large project builds in general.

  I don't think it's relevant, but I'm running those builds in an
  schroot with the same Ubuntu Bionic distro I'm also using as main host
  distro.

  The specific error I get is this (in Spanish):

make[4]: error al escribir: stdout

  I call Buildroot's make like this from KDE Konsole with "infinite
  history buffer" enabled (uses a tmp file to store the logs):

V=1 make ...some stuff... 2>&1

  However, the error is reproducible in Konsole even if I call make
  without options and also if I use "limited (in-memory) history buffer"
  as well as "no history buffer". Buildroot autoselects a
  parallelization level (-j) automatically. In my case, I'm using a Xeon
  E-2176 CPU with 12 threads.

  Searching on the Internet I found a thread[1] where people from the
  GNU Make project say that the error may be coming from the C runtime
  library (and I suspect originating from the kernel).

  I can NOT reproduce the issue on linux-image-4.15.0-43-generic
  (selected from grub at boot), but I experience it with linux-
  image-4.15.0-44-generic and linux-image-4.15.0-45-generic. That's why
  I'm reporting this bug against the linux package.

  Interestingly enough, I can NOT reproduce the issue on linux-
  image-4.15.0-45-generic (haven't tried previous versions) when
  building from xterm instead of Konsole. Unfortunately, this laptop has
  a 4K screen and xterm isn't an option for me.

  If I build redirecting stdout and stderr to different files to avoid
  terminal output and then watching the stdout file with tail -f, the
  tail command eventually finishes although the build continues and I
  can keep watching it by running tail again. An infinite build loop
  never finishes with this redirection (error not reproducible). Same
  results with the 2>&1 redirection to a single file.

  All this looks a bit like a poltergeist, but the only thing I'm sure
  about is that it all started with the upgrade from 4.15.0-43 to -44
  and it continues on -45.

  Thank you.

  
  [1] 
http://gnu-make.2324884.n4.nabble.com/Spurious-quot-write-error-quot-on-parallel-builds-td15695.html

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

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

[Kernel-packages] [Bug 1785822] Re: linux-azure: make sure CONFIG_MLX{4, 5}_INFINIBAND stays as "y"

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  linux-azure: make sure CONFIG_MLX{4,5}_INFINIBAND stays as "y"

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released

Bug description:
  The recent change "infiniband: mlx5: fix build errors when
  INFINIBAND_USER_ACCESS=m" in bionic/linux 4.15.0-31.33 caused bionic
  /linux-azure to revert CONFIG_MLX5_INFINIBAND to "m".

  Additional changes need to be included in order to keep
  CONFIG_MLX5_INFINIBAND=y as requested by Bug #1759656.

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

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

[Kernel-packages] [Bug 1814651] Re: linux-aws: 4.4.0-1076.86 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1814647
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 14. February 2019 11:31 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 14. February 2019 12:34 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Promote to Proposed
  phase-changed: Thursday, 14. February 2019 12:34 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1756103] Re: [bionic][arm64] d-i: add hisi_sas_v3_hw to scsi-modules

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [bionic][arm64] d-i: add hisi_sas_v3_hw to scsi-modules

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Add hisi_sas_v3_hw to scsi-modules so that d-i can detect the drive 
  during install.

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

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

[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

[Mauricio Faria de Oliveira]

Hi @lazamarius1,

The fix for linux generic should be applied in the next kernel SRU cycle.
The current cycle ends on late February [1].

[1] https://kernel.ubuntu.com/

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes srcu_gp_start() acquire the srcu_data
  structure's ->lock across the calls to rcu_segcblist_advance() and
  rcu_segcblist_accelerate(), thus preventing this corruption.

  Please investigate this issue and evaluate the proposed fix.

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

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

[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

[overlord]

Hi @brad-figg,

Can we get a proposed fix for Xenial linux(-generic) package?
Or that is planned after the bionic one?

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes srcu_gp_start() acquire the srcu_data
  structure's ->lock across the calls to rcu_segcblist_advance() and
  rcu_segcblist_accelerate(), thus preventing this corruption.

  Please investigate this issue and evaluate the proposed fix.

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

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

[Kernel-packages] [Bug 1814733] Re: linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Wednesday, 13. February 2019 14:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-azure: 4.18.0-1009.9~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Wednesday, 13. February 2019 14:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-beta: Pending -- snap not in 18/beta channel
snap-release-to-edge: Pending -- snap not in 18/edge channel
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

[Kernel-packages] [Bug 1753288] Re: ZFS setgid broken on 0.7

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  ZFS setgid broken on 0.7

Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  Hey there,

  We've had one of our LXD users report that setting the setgid bit
  inside a container using ZFS on Ubuntu 18.04 (zfs 0.7) is silently
  failing. This is not a LXD bug as the exact same operation works on
  other filesystems.

  There are more details available here:
  https://github.com/lxc/lxd/issues/4294

  Reproducer looks something like:

  ```
  root@c1:~# touch a
  root@c1:~# chmod g+s a
  root@c1:~# touch b
  root@c1:~# chown 0:117 b
  root@c1:~# chmod g+s b
  root@c1:~# stat a
File: a
Size: 0 Blocks: 1  IO Block: 131072 regular empty file
  Device: 43h/67d   Inode: 33890   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
  Access: 2018-03-02 03:32:47.019430367 +
  Modify: 2018-03-02 03:32:47.019430367 +
  Change: 2018-03-02 03:32:49.459445015 +
   Birth: -
  root@c1:~# stat b
File: b
Size: 0 Blocks: 1  IO Block: 131072 regular empty file
  Device: 43h/67d   Inode: 34186   Links: 1
  Access: (0644/-rw-r--r--)  Uid: (0/root)   Gid: (  117/postdrop)
  Access: 2018-03-02 03:32:50.907453706 +
  Modify: 2018-03-02 03:32:50.907453706 +
  Change: 2018-03-02 03:33:01.299516054 +
   Birth: -
  root@c1:~# 
  ```

  And for confirmation, using a tmpfs in the same container:

  ```
  root@c1:~# mkdir tmpfs
  root@c1:~# mount -t tmpfs tmpfs tmpfs
  root@c1:~# cd tmpfs/
  root@c1:~/tmpfs# touch a
  root@c1:~/tmpfs# chmod g+s a
  root@c1:~/tmpfs# touch b
  root@c1:~/tmpfs# chown 0:117 b
  root@c1:~/tmpfs# chmod g+s b
  root@c1:~/tmpfs# stat a
File: a
Size: 0 Blocks: 0  IO Block: 4096   regular empty file
  Device: 65h/101d  Inode: 3   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (0/root)
  Access: 2018-03-02 03:33:35.783722623 +
  Modify: 2018-03-02 03:33:35.783722623 +
  Change: 2018-03-02 03:33:40.507750883 +
   Birth: -
  root@c1:~/tmpfs# stat b
File: b
Size: 0 Blocks: 0  IO Block: 4096   regular empty file
  Device: 65h/101d  Inode: 4   Links: 1
  Access: (2644/-rw-r-Sr--)  Uid: (0/root)   Gid: (  117/postdrop)
  Access: 2018-03-02 03:33:42.131760597 +
  Modify: 2018-03-02 03:33:42.131760597 +
  Change: 2018-03-02 03:33:46.227785091 +
   Birth: -
  root@c1:~/tmpfs# 
  ```

  This is particularly troubling because there are no errors returned to
  the user, so we now have containers that will have broken binaries and
  permissions applied to them with no visible way to detect the problem
  short of scanning the entire filesystem against a list of known
  permissions.

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

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

[Kernel-packages] [Bug 1800566] Re: Make the reset_devices parameter default for kdump kernels

[Guilherme G. Piccoli]

** Changed in: makedumpfile (Ubuntu Trusty)
 Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira 
(halves)

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)

** Changed in: makedumpfile (Ubuntu Bionic)
 Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)

** Changed in: makedumpfile (Ubuntu Cosmic)
 Assignee: (unassigned) => Heitor R. Alves de Siqueira (halves)

** Changed in: makedumpfile (Ubuntu Disco)
 Assignee: Mauricio Faria de Oliveira (mfo) => Heitor R. Alves de Siqueira 
(halves)

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

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

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

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

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

Title:
  Make the reset_devices parameter default for kdump kernels

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  Confirmed
Status in makedumpfile source package in Xenial:
  Confirmed
Status in makedumpfile source package in Bionic:
  Confirmed
Status in makedumpfile source package in Cosmic:
  Confirmed
Status in makedumpfile source package in Disco:
  Confirmed

Bug description:
  Kernel has the "reset_devices" parameter that drivers can opt-in, and
  perform special activity in case this parameter is parsed from
  command-line. For example, in kdump kernels it hints the drivers that
  they (maybe) are booting from a non-healthy condition and needs to
  issue some reset to the adapter. Users currently (kernel v4.19) are:
  hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.

  This should be enabled by default in the kdump config file to be added
  in the kdump kernel command-line for all versions.

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

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

[Kernel-packages] [Bug 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

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

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

[Kernel-packages] [Bug 1761534] Re: "ip a" command on a guest VM shows UNKNOWN status

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  "ip a" command on a guest VM shows UNKNOWN status

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  
  [Impact] 

  "ip a" command on a guest VM shows UNKNOWN status.

  [Test Case]

  * Environment : Running a guest VM with a virtio-net adaptor interface, 
running on DPDK.
  * Perform "ip a" inside the guest VM shows state "UNKNOWN" as follow example:

  2: eth0:  mtu 1500 qdisc pfifo_fast state 
UNKNOWN group default qlen 1000
  .

  [Regression Potential]

   * Regression is low, the patch fix the operstate logic for virtio when no 
VIRTIO_NET_F_STATUS.[1]
   * The patch has been first accepted in net-next, then move into Linus's git.

  [1] - VIRTIO_NET_F_STATUS
  Allow the host to inform us that the link is down by adding a 
VIRTIO_NET_F_STATUS which indicates that device status is available in 
virtio_net config.

  [Other Info]
   
   * Linus: 
https://github.com/torvalds/linux/commit/bda7fab54828bbef2164bb23c0f6b1a7d05cc718

   * Net-next:
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=bda7fab54828bbe
 

  [Original Description]
  It has been brought to our attention the following bug :

  
  Environment: The guest VM is using a canonical ubuntu image, and the eth0 is 
a virtio-net adaptor, running on DPDK.

  Background: "ip a" command relies on the operstate variable of the
  net_device structure maintained by the kernel. This is based on the
  operational state as defined in the IF MIB (RFC 2863). Device drivers
  are expected to update this member. But many older drivers don’t seem
  to be using this. So in general, IF_OPER_UP and IF_OPER_UNKNOWN are
  treated as equal, in some sense, to maintain backward compatibility.
  Even if we look at https://elixir.free-
  electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468,
  the function to check if interface is up, is written as follows, which
  says that OPER_UNKNOWN is not something to be alarmed about, and just
  reflective of a state that some drivers don’t care to update about.

  static inline bool netif_oper_up(const struct net_device *dev)
  {
  return (dev->operstate == IF_OPER_UP ||
  dev->operstate == IF_OPER_UNKNOWN /* backward compat */);
  }

  Code Ref:

  1. 
https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L1739
  2. 
https://elixir.free-electrons.com/linux/v4.15-rc2/source/include/linux/netdevice.h#L3468
  3. https://www.kernel.org/doc/Documentation/networking/operstates.txt

  Now, for traditional kernel mode network adapter drivers, this state is 
supposed to be manipulated by the driver. And we can safely assume that most 
current kernel model drivers do keep this updated.
  

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

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

[Kernel-packages] [Bug 1752655] Re: retpoline: ignore %cs:0xNNN constant indirections

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  retpoline: ignore %cs:0xNNN constant indirections

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  These are paravirt style indirections and can be ignored.

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

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

[Kernel-packages] [Bug 1788308] Re: [Regression] Colour banding appears on Lenovo B50-80 integrated display

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [Regression] Colour banding appears on Lenovo B50-80 integrated
  display

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The problem affects the integrated display on a Lenovo B50-80
  notebook.

  Colour banding is visible everywhere on the system, as dithering seems
  not to be enabled on this 6bpp display. This issue was not present on
  non-HWE Ubuntu 16.04, and it showed up after I upgraded to Ubuntu
  18.04. There was already a very similar bug #1749420 that had a fix
  released, however, because the make and model of an LCD screen in that
  case was different, the quirk added to the kernel did not address the
  problem that affects my machine. The cause of this issue is probably
  the same, since I have checked that pre-4.8.0-rc2 kernels handled
  dithering correctly, and 4.8.0-rc2 and later kernels already had the
  bug described. I believe that adding quirk for an another type of
  display may fix the problem.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  and
  sudo get-edid | edid-decode in a file named edid-decoded.txt.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1245 F pulseaudio
   /dev/snd/controlC1:  me 1245 F pulseaudio
  Date: Wed Aug 22 00:26:15 2018
  HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e
  InstallationDate: Installed on 2018-08-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80EW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=a1cd5b8c-2707-4840-858b-3ca12517193b ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN54WW(V3.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80EW
  dmi.product.version: Lenovo B50-80
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1753424] Re: s390/crypto: Fix kernel crash on aes_s390 module remove

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  s390/crypto: Fix kernel crash on aes_s390 module remove

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Upstream patch to fix the aes_s390 kernel module remove crash,
  introduced with kernel 4.15 rc1.

  Here is the patch to fix the kernel crash on aes_s390 kernel module removal.
  Please note that this patch is as of now not upstream available but in the 
s390 pipe for the next merge window (and so may be visible upstream with the 
start of the 4.17 development kernels).

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

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

[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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

[Kernel-packages] [Bug 1796647] Re: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Shared folders cannot be mounted in ubuntu/cosmic64 due to missing
  vbox modules

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Vagrant environments are no longer able to use virtualbox
  feartures like shared folders. This is due to Ubuntu Cosmic kernels
  currently shipping the upstream vboxguest module and not importing
  modules from the virtualbox-guest-dkms package.

  Fix: One solution would be to use the dkms modules for Vagrant, but
  this is not ideal. At this late stage the simplest solution is to go
  back to importing the out-of-tree modules.

  Regression Potential: Minimal. Will have no impact outside of
  virtualbox environments, and the drivers being imported come from the
  virtualbox-guest-dkms package in cosmic and are thus expected to work
  well.

  ---

  In bionic, the vboxsf module was included in linux-
  modules-...-generic:

  $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep 
vboxsf.ko
  -rw-r--r-- root/root 63238 2018-09-24 10:08 
./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko

  In cosmic, it isn't:

  $ dpkg -c ~/Downloads/linux-
  modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko

  This results in shared folders no longer being mountable in Ubuntu
  Vagrant boxes (and, as the other vbox modules are also missing,
  probably has other effects that haven't yet been reported).

  [Original Report]

  Just tried to test out the new cosmic64 vagrant box and get the
  following error;

  ```
  Vagrant was unable to mount VirtualBox shared folders. This is usually
  because the filesystem "vboxsf" is not available. This filesystem is
  made available via the VirtualBox Guest Additions and kernel module.
  Please verify that these guest additions are properly installed in the
  guest. This is not a bug in Vagrant and is usually caused by a faulty
  Vagrant box. For context, the command attempted was:

  mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant

  The error output from the command was:

  /sbin/mount.vboxsf: mounting failed with the error: No such device
  ```

  I tried with ubuntu/bionic64 and it worked fine.

  I've got;
  $ vagrant version
  Installed Version: 2.1.5
  Latest Version: 2.1.5

  You're running an up-to-date version of Vagrant!
  $ VBoxManage --version
  5.2.18r124319
  $

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

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

[Kernel-packages] [Bug 1805248] Re: Regression: hinic performance degrades over time

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Regression: hinic performance degrades over time

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Bug 1800664 introduced checksum offload and TSO support for HiNIC adapters. 
While that did improve performance in short iperf runs, longer runs were later 
found to show a significant regression in performance:
    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800664/comments/3

  [Test Case]
  iperf -c 192.168.99.1 -P5

  [Fix]
  Revert the offending patch.

  [Regression Risk]
  This is reverting a patch, returning the driver to 18.10 GA behavior.

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

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

[Kernel-packages] [Bug 1759547] Re: Use med_power_with_dipm SATA LPM to save more power for mobile platforms

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Use med_power_with_dipm SATA LPM to save more power for mobile
  platforms

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  In order to let CPU Package gets deeper C-state, we need to use power-
  saving SATA LPM to achieve that.

  This commit introduce a new config, SATA_MOBILE_LPM_POLICY:

  commit ebb82e3c79d2a956366d0848304a53648bd6350b
  Author: Hans de Goede 
  Date:   Mon Dec 11 17:52:16 2017 +0100

  ahci: Allow setting a default LPM policy for mobile chipsets

  On many laptops setting a different LPM policy then unknown /
  max_performance can lead to power-savings of 1.0 - 1.5 Watts (when idle).

  Modern ultrabooks idle around 6W (at 50% screen brightness), 1.0 - 1.5W
  is a significant chunk of this.

  There are some performance / latency costs to enabling LPM by default,
  so it is desirable to make it possible to set a different LPM policy
  for mobile / laptop variants of chipsets / "South Bridges" vs their
  desktop / server counterparts. Also enabling LPM by default is not
  entirely without risk of regressions. At least min_power is known to
  cause issues with some disks, including some reports of data corruption.

  This commits adds a new ahci.mobile_lpm_policy kernel cmdline option,
  which defaults to a new SATA_MOBILE_LPM_POLICY Kconfig option so that
  Linux distributions can choose to set a LPM policy for mobile chipsets
  by default.

  The reason to have both a kernel cmdline option and a Kconfig default
  value for it, is to allow easy overriding of the default to allow
  trouble-shooting without needing to rebuild the kernel.

  Signed-off-by: Hans de Goede 
  Signed-off-by: Tejun Heo 

  "3 => Medium power with Device Initiated PM enable" is a well-balanced
  that can let Package enters deeper C-state.

  Also, Fedora already set SATA_MOBILE_LPM_POLICY=3 for their latest
  kernel.

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

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

[Kernel-packages] [Bug 1814759] Re: linux-gcp: 4.18.0-1007.8 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1814749
- phase: Holding before Promote to Proposed
- phase-changed: Thursday, 14. February 2019 09:09 UTC
+ phase: Promote to Proposed
+ phase-changed: Thursday, 14. February 2019 13:14 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux-gcp: 4.18.0-1007.8 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Promote to Proposed
  phase-changed: Thursday, 14. February 2019 13:14 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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

[Kernel-packages] [Bug 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

[David Coronel]

[VERIFICATION BIONIC]

I can modprobe the mq-deadline, kyber and bfq schedulers but it looks
like doing a modprobe of the cfq and deadline schedulers doesn't list
them as choices in the available schedulers:

# uname -r
4.18.0-1009-azure

# modprobe bfq
# modprobe cfq-iosched
# modprobe mq-deadline
# modprobe kyber-iosched
# modprobe deadline-iosched

# tail /sys/block/sda/queue/scheduler
[none] mq-deadline kyber bfq 

I have these 4.18 kernel packages installed:

# dpkg -l | grep 4.18 | grep linux
ii  linux-azure 4.18.0.1009.9
ii  linux-azure-cloud-tools-4.18.0-1009 4.18.0-1009.9~18.04.1
ii  linux-azure-headers-4.18.0-1009 4.18.0-1009.9~18.04.1
ii  linux-azure-tools-4.18.0-1009   4.18.0-1009.9~18.04.1
ii  linux-cloud-tools-4.18.0-1009-azure 4.18.0-1009.9~18.04.1
ii  linux-cloud-tools-azure 4.18.0.1009.9
ii  linux-headers-4.18.0-1009-azure 4.18.0-1009.9~18.04.1
ii  linux-headers-azure 4.18.0.1009.9
ii  linux-image-4.18.0-1009-azure   4.18.0-1009.9~18.04.1
ii  linux-image-azure   4.18.0.1009.9
ii  linux-modules-4.18.0-1009-azure 4.18.0-1009.9~18.04.1
ii  linux-tools-4.18.0-1009-azure   4.18.0-1009.9~18.04.1
ii  linux-tools-azure   4.18.0.1009.9

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

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

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

[Kernel-packages] [Bug 1814730] Re: linux-oem: 4.15.0-1034.39 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/upload-to-ppa-dnu
   Status: New => Invalid

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814726
  phase: Packaging
  phase-changed: Wednesday, 06. February 2019 10:38 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

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

Title:
  linux-oem: 4.15.0-1034.39 -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:
  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-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814726
  phase: Packaging
  phase-changed: Wednesday, 06. February 2019 10:38 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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

[Kernel-packages] [Bug 1814730] Re: linux-oem: 4.15.0-1034.39 -proposed tracker

[Timo Aaltonen]

** Summary changed:

- linux-oem:  -proposed tracker
+ linux-oem: 4.15.0-1034.39 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux-oem: 4.15.0-1034.39 -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:
  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-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814726
  phase: Packaging
  phase-changed: Wednesday, 06. February 2019 10:38 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

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

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

[Kernel-packages] [Bug 1811337] Re: To reduce the Realtek USB cardreader power consumption

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1814241] Re: linux-oem: 4.15.0-1033.38 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1811421] Re: linux-oem: 4.15.0-1032.37 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove 

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

[bugproxy]

--- Comment From cborn...@de.ibm.com 2019-02-14 08:22 EDT---
Can this be reproduced with the upstream qemu? If yes, can you also report this 
to the  qemu-s390x mailing list?

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

Title:
  Guest crashed when detaching the ovs interface device

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  
   When detaching one openvswitch interface device with virsh detach-device, if 
the port has been deleted from the ovs and the interface device has been 
deleted. The virsh detach-device will fail with "error: Unable to read from 
monitor: Connection reset by peer", the qemu is terminated and the log shows " 
UNSETVNETLE ioctl() failed, File descriptor in bad state".  

  
  [Background] This error is originally found from the openstack KVM CI tempest 
test.  By investigating I found it's introduced by one ovs-vif patch, which 
deletes the ovs port and delete the interface before detaching the device.  You 
can find the commit from https://bugs.launchpad.net/os-vif/+bug/1801072

  
  Reproduced:

  
     root@:~#  ovs-vsctl del-port br0 tap9273235a-dd
     root@:~#  ip link del tap9273235a-dd

  
  The interface device tap9273235a-dd has been removed from the host(ifconfg, 
ovs-vsctl show)  and can be found in the guest.(logon the guest, ip a  it's in 
down state)

  
  root@:~# virsh detach-device kvm net.xml
  error: Failed to detach device from net.xml
  error: Unable to read from monitor: Connection reset by peer

  
  The qemu has terminated and the log in /var/log/libvirt/qemu/kvm.log
  TUNSETVNETLE ioctl() failed: File descriptor in bad state.
  2019-01-18 08:16:11.304+: shutting down, reason=crashed

  
  It seems the qemu tried to handle this interface, but in fact it has been 
deleted. qemu couldn't read the file and give the error.
  But I don't think the guest should be crashed directly for the file 
descriptor error. 



  
  Environment:
  Ubuntu 16.04.5 LTS
  Linux (EC12) 4.4.0-141-generic
  QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5~cloud0)
  libvirtd (libvirt) 4.0.0


  
  net.xml

  
   
      
      
      
    
      
      
    
    
    
    
    


  
  kvm.xml

  
  
    kvm
    59f71b47-16e4-401d-9d33-30bc1605a84a
    524288
    524288
    1
    
      /machine
    
    
      hvm
      
    
    
      
    
    
    destroy
    restart
    destroy
    
      /usr/bin/qemu-system-s390x
      
    
    
    
    
    
    
      
      
    
    
    
      
      
    
    
      
      
    
    
      libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a
      libvirt-59f71b47-16e4-401d-9d33-30bc1605a84a
    
    
      +0:+0
      +0:+0
    
  

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

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

[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

[P.D.]

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

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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

[Kernel-packages] [Bug 1799393] Re: Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  
  == SRU Justification ==
  The requested commit fixes a regression introduce by mainline commit
  3a2f70331226, in v4.18-rc1.  The commit is only needed in Cosmic.  Do to
  the regression, A Mellanox CX5 stops pinging with rx_wqe_err (mlx5_core)

  == Fix ==
  37fdffb217a4 ("net/mlx5: WQ, fixes for fragmented WQ buffers API")

  == Regression Potential ==
  Low. This commit has been cc'd to stable, so it has had additional
  upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  == Comment: #0 - Michael Ranweiler  - 2018-10-18 11:34:40 ==

  ---Problem Description---
  At the system if u do
  ethtool -S enP48p1s0f0 | grep wqe_err
   rx_wqe_err: 1
   rx0_wqe_err: 0
   rx1_wqe_err: 0
   rx2_wqe_err: 0
   rx3_wqe_err: 1
   rx4_wqe_err: 0
   rx5_wqe_err: 0
   rx6_wqe_err: 0
   rx7_wqe_err: 0
   rx8_wqe_err: 0
   rx9_wqe_err: 0
   rx10_wqe_err: 0
   rx11_wqe_err: 0
   rx12_wqe_err: 0
   rx13_wqe_err: 0
   rx14_wqe_err: 0
   rx15_wqe_err: 0

  Will see that rx side is hitting issue.

  ---Additional Hardware Info---
  Mellanox CX5 Ethernet 100G
  lspci
  0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]

  Machine Type = P9

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
  Using a CX5 Ethernet 100G card
  lspci
  0030:01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  0030:01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]

  just configure IP
  ifconfig enP48p1s0f0 33.33.33.33 netmask 255.255.255.0 up
  then partner system configure IP and then try ping -f
  ping -f 33.33.33.33
  PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data.
  ^C
  --- 33.33.33.33 ping statistics ---
  5413 packets transmitted, 5373 received, 0% packet loss, time 934ms
  rtt min/avg/max/mdev = 0.015/0.019/0.669/0.010 ms, ipg/ewma 0.172/0.020 ms
  # ping 33.33.33.33
  PING 33.33.33.33 (33.33.33.33) 56(84) bytes of data.
  ^C
  --- 33.33.33.33 ping statistics ---
  2 packets transmitted, 0 received, 100% packet loss, time 1071ms

  then at the recv system then do
  ethtool -S enP48p1s0f0 | grep wqe_err
   rx_wqe_err: 1
   rx0_wqe_err: 0
   rx1_wqe_err: 0
   rx2_wqe_err: 0
   rx3_wqe_err: 1
   rx4_wqe_err: 0
   rx5_wqe_err: 0
   rx6_wqe_err: 0
   rx7_wqe_err: 0
   rx8_wqe_err: 0
   rx9_wqe_err: 0
   rx10_wqe_err: 0
   rx11_wqe_err: 0
   rx12_wqe_err: 0
   rx13_wqe_err: 0
   rx14_wqe_err: 0
   rx15_wqe_err: 0
  you will see rx_wqe_err with a counter non-zero.

  This is fixed by this patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=37fdffb217a45609edccbb8b407d031143f551c0

  == Comment: #1 - Carol L. Soto  - 2018-10-18 11:46:00 ==
  I did a git clone to the cosmic tree and loaded the kernel in a system.

  kernel 4.18.12 and I can recreate it.

  lspci | grep Mell | grep ConnectX-5
  :01:00.0 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  :01:00.1 Ethernet controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  0030:01:00.0 Infiniband controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  0030:01:00.1 Infiniband controller: Mellanox Technologies MT28800 Family 
[ConnectX-5 Ex]
  :~# ethtool -S enp1s0f0 | grep wqe_err
   rx_wqe_err: 2
   rx0_wqe_err: 1
   rx1_wqe_err: 1
   rx2_wqe_err: 0
   rx3_wqe_err: 0
   rx4_wqe_err: 0
   rx5_wqe_err: 0
   rx6_wqe_err: 0
   rx7_wqe_err: 0
   rx8_wqe_err: 0
   rx9_wqe_err: 0
   rx10_wqe_err: 0
  

[Kernel-packages] [Bug 1762448] Re: Enable Tunneled Operations on POWER9

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Enable Tunneled Operations on POWER9

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Philippe Bergheaud  - 2018-04-09 09:15:22 ==
  ---Problem Description---
  PCI and CAPI Tunneled operations for POWER9 do not operate

  ---uname output---
  Linux zzfp088p01 4.16.0-rc7-00062-g0b41260-dirty #5 SMP Wed Apr 4 14:48:53 
CEST 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  POWER9 + CAPI card with MemCpy 2.0 Directed Mode AFU for PSL9 

   
  Machine Type = power9 ppc64le 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   AFU sends as_notify message ; host thread does not wake up
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.

  == Comment: #1 - Philippe Bergheaud  - 2018-04-09 09:20:35 ==
  The following mainline linux patches solve the issue:

  https://github.com/torvalds/linux/commit/d6a90bb83b50 powerpc/powernv:
  Enable tunneled operations

  https://github.com/torvalds/linux/commit/9dbcbfa1fe0c cxl: read PHB
  indications from the device tree

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

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

[Kernel-packages] [Bug 1771245] Re: [ICL] Touch support

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [ICL] Touch support

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Description:

  Icelake is using for touch screen USB2 and I2C.
  Precise touch will be via SPI.

  Up to 2 independent screens
  Pen Report Rate: 300Hz
  Active pen latency <20ms
  BL impact < 5%

  Target Kernel:4.19
  Target Release: 18.10

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

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

[Kernel-packages] [Bug 1794387] Re: Colour banding in HP Pavilion 15-n233sl integrated display

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Colour banding in HP Pavilion 15-n233sl integrated display

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Colour bandind is visible everywhere in the system, and it appeared
  after I had my integrated monitor replaced. I believe it's not a
  hardware problem, since booting with 'nomodeset' works as expected.

  There were already two similar bugs,
  https://bugs.launchpad.net/bugs/1749420 and
  https://bugs.launchpad.net/bugs/1788308, but the fixes provided for
  those bugs did not work for my specific monitor.

  I'm running Ubuntu 18.04 with kernel linux-image-4.15.0-34-generic,
  installing linux-image-4.18.8 with UKUU didn't help.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  sudo get-edid | edid-decode in a file named edid-decoded.txt
  cat /proc/version_signature in version.log
  sudo lspci -vnvn in lspci-vnvn.log.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   1796 F pulseaudio
   /dev/snd/controlC1:  matt   1796 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2018-09-27 (0 days ago)
  InstallationMedia: neon devunstable "Bionic" - Build amd64 LIVE Binary 
20180924-13:08
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=c3f61207-d13e-474b-a499-98030ddef8e1 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UnreportableReason: Questa segnalazione riguarda un pacchetto che non è 
installato.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 03/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.71
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2166
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.71:bd03/13/2017:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1795493] Re: netfilter: nf_conntrack: resolve clash for matching conntracks

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  netfilter: nf_conntrack: resolve clash for matching conntracks

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  Per https://www.weave.works/blog/racy-conntrack-and-dns-lookup-
  timeouts Kubernetes users are seeing DNS lookups from Pods taking 5 or
  more seconds.

  Please pick up the following patches to netfilter:
  http://patchwork.ozlabs.org/patch/937963/
  http://patchwork.ozlabs.org/patch/952939/

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

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

[Kernel-packages] [Bug 1806419] Re: linux-raspi2: 4.18.0-1008.10 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-raspi2 - 4.18.0-1009.11

---
linux-raspi2 (4.18.0-1009.11) cosmic; urgency=medium

  * linux-raspi2: 4.18.0-1009.11 -proposed tracker (LP: #1811412)

  * Cosmic update: 4.18.19 upstream stable release (LP: #1810820)
- [Config] Update config after 4.18.0-14.15 rebase

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

  * Replaced on rebase by version from 4.18.20
- sc16is7xx: Fix for multi-channel stall

  [ Ubuntu: 4.18.0-14.15 ]

  * linux: 4.18.0-14.15 -proposed tracker (LP: #1811406)
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * [Regression] crashkernel fails on HiSilicon D05 (LP: #1806766)
- efi: honour memory reservations passed via a linux specific config table
- efi/arm: libstub: add a root memreserve config table
- efi: add API to reserve memory persistently across kexec reboot
- irqchip/gic-v3-its: Change initialization ordering for LPIs
- irqchip/gic-v3-its: Simplify LPI_PENDBASE_SZ usage
- irqchip/gic-v3-its: Split property table clearing from allocation
- irqchip/gic-v3-its: Move pending table allocation to init time
- irqchip/gic-v3-its: Keep track of property table's PA and VA
- irqchip/gic-v3-its: Allow use of pre-programmed LPI tables
- irqchip/gic-v3-its: Use pre-programmed redistributor tables with kdump
  kernels
- irqchip/gic-v3-its: Check that all RDs have the same property table
- irqchip/gic-v3-its: Register LPI tables with EFI config table
- irqchip/gic-v3-its: Allow use of LPI tables in reserved memory
- arm64: memblock: don't permit memblock resizing until linear mapping is up
- efi/arm: Defer persistent reservations until after paging_init()
- efi: Permit calling efi_mem_reserve_persistent() from atomic context
- efi: Prevent GICv3 WARN() by mapping the memreserve table before first use
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * iptables connlimit allows more connections than the limit when using
multiple CPUs (LP: #1811094)
- netfilter: nf_conncount: don't skip eviction when age is negative
  * CVE-2018-16882
- KVM: Fix UAF in nested posted interrupt processing
  * Cannot initialize ATA disk if IDENTIFY command fails (LP: #1809046)
- scsi: libsas: check the ata device status by ata_dev_enabled()
  * scsi: libsas: fix a race condition when smp task timeout (LP: #1808912)
- scsi: libsas: fix a race condition when smp task timeout
  * CVE-2018-14625
- vhost/vsock: fix use-after-free in network stack callers
  * Fix and issue that LG I2C touchscreen stops working after reboot
(LP: #1805085)
- HID: i2c-hid: Disable runtime PM for LG touchscreen
  * Drivers: hv: vmbus: Offload the handling of channels to two workqueues
(LP: #1807757)
- Drivers: hv: vmbus: check the creation_status in vmbus_establish_gpadl()
- Drivers: hv: vmbus: Offload the handling of channels to two workqueues
  * Disable LPM for Raydium Touchscreens (LP: #1802248)
- USB: quirks: Add 

[Kernel-packages] [Bug 1730836] Re: [Feature] Optimize huge page clear/copy cache behavior

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [Feature] Optimize huge page clear/copy cache behavior

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description

  Huge page helps to reduce TLB miss rate, but it has higher cache
  footprint, sometimes this may cause some issue. For example, when
  clearing huge page on x86_64 platform, the cache footprint is 2M. But
  on a Xeon E5 v3 2699 CPU, there are 18 cores, 36 threads, and only 45M
  LLC (last level cache). That is, in average, there are 2.5M LLC for
  each core and 1.25M LLC for each thread. If the cache pressure is
  heavy when clearing the huge page, and we clear the huge page from the
  begin to the end, it is possible that the begin of huge page is
  evicted from the cache after we finishing clearing the end of the huge
  page. And it is possible for the application to access the begin of
  the huge page after clearing the huge page.

  To help the above situation, when we clear or copy a huge page, the
  order to clear or copy the sub-pages can be changed to clear or copy
  the sub-page to access last.

  Target Kernel: 4,19
  Target Release: 18.10

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

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

[Kernel-packages] [Bug 1736393] Re: [Artful][Wyse 3040] System hang when trying to enable an offlined CPU core

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [Artful][Wyse 3040] System hang when trying to enable an offlined CPU
  core

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-oem source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Invalid

Bug description:
  1. disable cpu[1-3] $ echo 0 > /sys/devices/system/cpu/cpu[1-3]/online
  2. enable cpu[1-3] $ echo 1 > /sys/devices/system/cpu/cpu[1-3]/online

  System will hang on step 2.

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

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

[Kernel-packages] [Bug 1685712] Re: [Featire] CNL: Enable RAPL support

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [Featire] CNL: Enable RAPL support

Status in intel:
  Fix Released
Status in intel trunk series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  enable RAPL on Cannon Lake Client Platforms

  Kernel Release: 4.17
  Target Release: 18.04

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

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

[Kernel-packages] [Bug 1734130] Re: [18.04 FEAT] Add kvm_stat from kernel tree

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [18.04 FEAT] Add kvm_stat from kernel tree

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Improves RAS characterics of systems running KVM by providing kvm_stat script:
  https://github.com/torvalds/linux/tree/master/tools/kvm/kvm_stat

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

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

[Kernel-packages] [Bug 1751796] Re: zed process consuming 100% cpu

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  zed process consuming 100% cpu

Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  I logged in this morning and found system kind of sluggish.
  A 'top' showed 'zed' process spinning 100% of a cpu.
  I didn't feel like worrying about it, so I simply rebooted.

  System came back up into the same state.
  Running 'strace -p 2002' shows repeated:

  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)
  ioctl(5, _IOC(0, 0x5a, 0x81, 0), 0x7ffccbb054b0) = -1 EBADF (Bad file 
descriptor)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: zfs-zed 0.7.5-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:34:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.zfs.zed.d.zed-functions.sh: [deleted]

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

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

[Kernel-packages] [Bug 1805607] Re: Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1806818] Re: Fix Intel I210 doesn't work when ethernet cable gets plugged

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1805775] Re: PC SN720 NVMe WDC 256GB consumes more power in S2Idle than during long idle

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1806335] Re: Enable new Realtek card reader

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1789146] Re: [Bug][CLX]assertion failure with util_range_rw using libpmemlog, possible kernel DAX bug

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [Bug][CLX]assertion failure with util_range_rw using libpmemlog,
  possible kernel DAX bug

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  On Mon, Apr 16, 2018 at 8:20 AM, Czurylo, Krzysztof
   wrote:
  >
  > I suspect the problem is caused by a bug in the kernel.
  >
  > I did a few experiments and it looks like the issue occurs only if the
  > filesystem is mounted with "-o dax". I can reproduce is both for xfs
  > and ext4, so it's not FS-specific, but rather DAX-specific. It also
  > reproduces on an emulated PMEM - no need to use real AEP DIMMs.
  >
  > Using the latest kernel (4.16.0) does not help.
  >
  > What happens:
  >
  > In debug version of libpmemlog (but also libpmemblk), the entire pool
  > is by default write-protected with mprotect(..., PROT_READ).
  >
  > When the program attempts to write some data to the pool (i.e.
  > pmemlog_append, pmemblk_write, ...), the library unprotects the pages
  > to be modified (usually just one or two pages) and once the data is
  > stored, the pages are protected again.
  >
  > Inside the kernel, mprotect splits the memory region associated with
  > the pool into 3 regions: the read-only head and tail + one r/w page in
  > the middle.
  >
  > The problem is that after the last step, the memory region associated
  > with the modified page is not merged with the adjacent regions having
  > the same protection flags (ro) to form one big read-only region again.
  > This leads to the situation where we have thousands of 4K memory
  > mappings per process that are tracked by the kernel separately. When
  > the number of maps exceeds the limit (default is 65536 - see:
  > /proc/sys/vm/max_map_count), mprotect fails with ENOMEM, which aborts
  > the program.

  Commitid: e1fb4a0864958fac2fb1b23f9f4562a9f90e3e8f
  dax: remove VM_MIXEDMAP for fsdax and device dax

  Target Kernel: 4.19

  Target Release: 18.10

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

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

[Kernel-packages] [Bug 1805607] Re: Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make 

[Kernel-packages] [Bug 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux-oem - 4.15.0-1033.38

---
linux-oem (4.15.0-1033.38) bionic; urgency=medium

  * linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)

  * Packaging resync (LP: #1786013)
- [Packaging] update update.conf

  [ Ubuntu: 4.15.0-45.48 ]

  * linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
  * External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
  * kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()

linux-oem (4.15.0-1032.37) bionic; urgency=medium

  * linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)

  * Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"

  * Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47

  [ Ubuntu: 4.15.0-44.47 ]

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't 
support
  1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion 
detection
- memstick: Prevent memstick host from getting runtime suspended during card
  detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
  * Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
  * Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi 
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
  resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling 
roce
  callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
  function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of 
notifying
  roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove 

[Kernel-packages] [Bug 1788308] Re: [Regression] Colour banding appears on Lenovo B50-80 integrated display

[Wojciech]

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

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

Title:
  [Regression] Colour banding appears on Lenovo B50-80 integrated
  display

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The problem affects the integrated display on a Lenovo B50-80
  notebook.

  Colour banding is visible everywhere on the system, as dithering seems
  not to be enabled on this 6bpp display. This issue was not present on
  non-HWE Ubuntu 16.04, and it showed up after I upgraded to Ubuntu
  18.04. There was already a very similar bug #1749420 that had a fix
  released, however, because the make and model of an LCD screen in that
  case was different, the quirk added to the kernel did not address the
  problem that affects my machine. The cause of this issue is probably
  the same, since I have checked that pre-4.8.0-rc2 kernels handled
  dithering correctly, and 4.8.0-rc2 and later kernels already had the
  bug described. I believe that adding quirk for an another type of
  display may fix the problem.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  and
  sudo get-edid | edid-decode in a file named edid-decoded.txt.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1245 F pulseaudio
   /dev/snd/controlC1:  me 1245 F pulseaudio
  Date: Wed Aug 22 00:26:15 2018
  HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e
  InstallationDate: Installed on 2018-08-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80EW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=a1cd5b8c-2707-4840-858b-3ca12517193b ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN54WW(V3.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80EW
  dmi.product.version: Lenovo B50-80
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  zfs system process hung on container stop/delete

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in zfs-linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request [Xenial][Artful] ==

  == Justification ==

  It is possible to hang zfs asynchronous reads if a read to a page that
  is mmap'd onto the the file being read is the same offset in the
  mapping as in the file. This is caused by two lock operations on the
  page.

  == Fix ==

  Upstream ZFS fix to ensure the page is not double-locked during async
  I/O of one or more pages.

  == Testing ==

  Create a zfs pool + zfs file system, run the reproducer program in
  comment #28 on the zfs filesystem.  Without the fix this can lock up,
  with the fix this runs to completion.

  == Regression Potential ==

  Minimal, the locking fix addresses a fundamental bug in the locking
  and this should not affect ZFS read/write I/O with this fix.

  --

  Summary:
  On a Bionic system running 4.15.0-10-generic, after attempting to build 
libaio in a Bionic daily container I cannot stop or delete the container. dmesg 
shows a variety of hung tasks

  Steps to Reproduce:
  Use the following script and watch for the the hang. At that point attempt to 
stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/

  Originally filed against LXD: https://github.com/lxc/lxd/issues/4314

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj2414 F pulseaudio
   /dev/snd/controlC0:  powersj2414 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 09:19:11 2018
  HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
  InstallationDate: Installed on 2018-02-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  Lsusb:
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20BSCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET42W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  ---
  

[Kernel-packages] [Bug 1793386] Re: [Hyper-V] Enable NVME devices

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [Hyper-V] Enable NVME devices

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  Please ensure the following are set in linux-azure kernels:

  CONFIG_BLK_DEV_NVME = y  (currently not set, but we need NVME devices)
  CONFIG_EDAC_DECODE_MCE = y  (already done in LP #1751123)
  CONFIG_EDAC_AMD64 = m  (already set, but we should ensure it stays that 
way)

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

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

[Kernel-packages] [Bug 1763062] Re: LSM stacking patches for bionic

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  LSM stacking patches for bionic

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  LSM stacking patches for bionic

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

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

[Kernel-packages] [Bug 1800664] Re: Add checksum offload and TSO support for HiNIC adapters

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Add checksum offload and TSO support for HiNIC adapters

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Increases throughput by more than 2x, as measured by the iperf benchmark.

  [Test Case]
  iperf -c 192.168.122.10 -P5

  [Fix]
  cc18a7543d2f6 net-next/hinic: add checksum offload and TSO support

  [Regression Risk]
  Clean cherry-pick restricted to a single driver that has been explicitly 
tested. A regression risk is that these bugs in these new features, which are 
enabled by default, could impact existing deployments. These features can, 
however, be disabled by ethtool which helps mitigate that risk.

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

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

[Kernel-packages] [Bug 1787089] Re: [AEP-bug] ext4: more rare direct I/O vs unmap failures

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  [AEP-bug] ext4: more rare direct I/O vs unmap failures

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Description:
  Even with the ext4_break_layouts() support added by "ext4: handle layout 
changes to pinned DAX mappings" Still seeing occasional cases with unit test 
where we are truncating a page that has an elevated reference count. 
Investigate.

  —

  The root cause of this issue is that while the ei->i_mmap_sem provides
  synchronization between ext4_break_layouts() and page faults, it doesn't
  provide synchronize us with the direct I/O path. This exact same issue exists
  in XFS AFAICT, with the synchronization tool there being the XFS_MMAPLOCK.

  This allows the direct I/O path to do I/O and raise & lower page->_refcount
  while we're executing a truncate/hole punch. This leads to us trying to free
  a page with an elevated refcount.

  Here's one instance of the race:

  CPU 0 CPU 1
  - -
  ext4_punch_hole()
  ext4_break_layouts() # all pages have refcount=1

  ext4_direct_IO()
  ... lots of layers ...
  follow_page_pte()
  get_page() # elevates refcount

  truncate_pagecache_range()
  ... a few layers ...
  dax_disassociate_entry() # sees elevated refcount, WARN_ON_ONCE()

  A similar race occurs when the refcount is being dropped while we're running
  ext4_break_layouts(), and this is the one that my test was actually hitting:

  CPU 0 CPU 1
  - -
  ext4_direct_IO()
  ... lots of layers ...
  follow_page_pte()
  get_page()

  elevates refcount of page X
  ext4_punch_hole()
  ext4_break_layouts() # two pages, X & Y, have refcount == 2
  __wait_var_event() # called for page X
  __put_devmap_managed_page()

  drops refcount of X to 1
  __wait_var_events() checks X's refcount in "if (condition)", and breaks.
  We never actually called ext4_wait_dax_page(), so 'retry' in
  ext4_break_layouts() is still false. Exit do/while loop in
  ext4_break_layouts, never attempting to wait on page Y which still has an
  elevated refcount of 2.
  truncate_pagecache_range()
  ... a few layers ...
  dax_disassociate_entry() # sees elevated refcount for Y, WARN_ON_ONCE()

  Essentially the solution will most likely involve adding
  synchronization between the direct I/O path and truncate/hole punch
  type operations, and it'll need to happen for both ext4 and XFS, so
  the filesystem folks need to be involved.

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

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

[Kernel-packages] [Bug 1790652] Re: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Oracle cosmic image does not find broadcom network device in Shape
  VMStandard2.1

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  I tried to register and boot a cosmic image to verify new changes in it and 
in cloud-init.
  The image failed to bring up networking in the initramfs, and thus failed to 
find iscsi root.
  this could be user error.

  Here is what I did to publish the image.

   - use oci build tool [1].
 following
 
https://docs.cloud.oracle.com/iaas/Content/Compute/Tasks/imageimportexport.htm#ImportinganImage
   - Download a livefs build from cloudware
 https://launchpad.net/~cloudware/+livefs/ubuntu/cosmic/cpc/
 example: livecd.ubuntu-cpc.oracle_bare_metal.img
 My image had version 20180821.1

   - oci os bucket create --name=smoser-devel
   - oci os object put \
--parallel-upload-count=4 \
--part-size=10 \
--bucket-name=smoser-devel \
--file=/tmp/livecd.ubuntu-cpc.oracle_bare_metal.img \
--name=cosmic-20180821.1.img

   - import the object
  $ oci compute image import from-object \
  --display-name=smoser-cosmic-20180821.1.img \
  --launch-mode=NATIVE \
  --namespace=intcanonical \
  --bucket-name=smoser-devel \
  --name=cosmic-20180821.1.img \
  --source-image-type=QCOW2

  Then I launched from the web UI a VM.Standard2.1.

  --
   https://docs.cloud.oracle.com/iaas/Content/API/Concepts/cliconcepts.htm

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

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

[Kernel-packages] [Bug 1762695] Re: Backport USB core quirks

[Brad Figg]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Backport USB core quirks

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Currently we need to recompile the entire kernel if we want try quirks
  in usbcore.

  [Test]
  Use kernel parameter "usbcore.quirks=" in conjunction with dynamic debug
  for usbcore, we can see that usb quirks successfully enabled for USB
  devices dynamically.
   
  [Fix]
  Introduce a new module parameter, "usbcore.quirks=". Users now can try
  different quirks without compiling anything.

  [Regression Potential]
  Low. It doesn't change any behavior of usb driver per se, it simply adds
  new logic to detect quirks.

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

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