Re: [Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Steve Langasek]

On Thu, Feb 15, 2018 at 12:06:04AM -, Crashbit wrote:
> I have a problem with tinc and netplan.

> I've using Ubuntu 17.10 server. When I try to start tincd daemon with 
> systemd, it doesn't start. 
> When start tinc daemon without systemd, it runs correct. 

Then that doesn't sound related to netplan.  You should file a separate bug
against tinc.

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  New
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  New
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  New
Status in ifmetric package in Ubuntu:
  New
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  New
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Committed
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  New
Status in vzctl package in Ubuntu:
  New
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 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: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748565] Re: Bluetooth: hci0: last event is not cmd complete (0x0f)

[Daniel van Vugt]

Is bluetooth working for you? I mean are you only reporting the log
message, or is bluetooth also not working?


** Summary changed:

- Bluetooth: hci0: last event is not cmd complete (0x0f)
+ [Intel 6235] Bluetooth: hci0: last event is not cmd complete (0x0f)

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

Title:
  [Intel 6235] Bluetooth: hci0: last event is not cmd complete (0x0f)

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

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1811 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 20:35:29 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1749592] Re: [Intel 6235] Bluetooth: hci0: last event is not cmd complete (0x0f)

[Daniel van Vugt]

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

Is bluetooth working for you? I mean are you only reporting the log
message, or is bluetooth also not working?

** Summary changed:

- Bluetooth: hci0: last event is not cmd complete (0x0f)
+ [Intel 6235] Bluetooth: hci0: last event is not cmd complete (0x0f)

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

Title:
  [Intel 6235] Bluetooth: hci0: last event is not cmd complete (0x0f)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [  153.651709] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  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
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1771 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Wed Feb 14 18:06:04 2018
  InstallationDate: Installed on 2017-10-13 (124 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-10-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1749592] Re: [Intel 6235] Bluetooth: hci0: last event is not cmd complete (0x0f)

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1748565, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1748565
   Bluetooth: hci0: last event is not cmd complete (0x0f)

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

Title:
  [Intel 6235] Bluetooth: hci0: last event is not cmd complete (0x0f)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [  153.651709] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  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
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1771 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Wed Feb 14 18:06:04 2018
  InstallationDate: Installed on 2017-10-13 (124 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-10-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

[Daniel van Vugt]

Or maybe pipe_bpp is some other weird value...

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

Title:
  Colour banding and artefacts appear system-wide on an Asus Zenbook
  UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

[Daniel van Vugt]

if (intel_dp->compliance.test_data.bpc != 0)
  this seems like a simple bug per above;
else
  it's some other problem;

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

Title:
  Colour banding and artefacts appear system-wide on an Asus Zenbook
  UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

[Daniel van Vugt]

Wait a minute... it sounds like dithering is always going to be disabled
(since commit 611032bfa71a7) for the case of (pipe_config->pipe_bpp ==
6*3).

index 5a9da484bb23..ef65b4be5e56 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -13060,8 +13060,11 @@ intel_modeset_pipe_config(struct drm_crtc *crtc,
}

/* Dithering seems to not pass-through bits correctly when it should, so
-* only enable it on 6bpc panels. */
-   pipe_config->dither = pipe_config->pipe_bpp == 6*3;
+* only enable it on 6bpc panels and when its not a compliance
+* test requesting 6bpc video pattern.
+*/
+   pipe_config->dither = (pipe_config->pipe_bpp == 6*3) &&
+   !pipe_config->dither_force_disable;
DRM_DEBUG_KMS("hw max bpp: %i, pipe bpp: %i, dithering: %i\n",
  base_bpp, pipe_config->pipe_bpp, pipe_config->dither);

diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index e245802c5727..0fafbec6dacf 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -28,8 +28,10 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -1593,6 +1595,13 @@ static int intel_dp_compute_bpp(struct intel_dp 
*intel_dp,
if (bpc > 0)
bpp = min(bpp, 3*bpc);

+   /* For DP Compliance we override the computed bpp for the pipe */
+   if (intel_dp->compliance.test_data.bpc != 0) {
+   pipe_config->pipe_bpp = 3*intel_dp->compliance.test_data.bpc;
+   pipe_config->dither_force_disable = pipe_config->pipe_bpp == 
6*3;
+   DRM_DEBUG_KMS("Setting pipe_bpp to %d\n",
+ pipe_config->pipe_bpp);
+   }
return bpp;
 }

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

Title:
  Colour banding and artefacts appear system-wide on an Asus Zenbook
  UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Colour banding and artefacts appear system-wide on an Asus Zenbook
  UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

[Daniel van Vugt]

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

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

Title:
  Colour banding and artefacts appear system-wide on an Asus Zenbook
  UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

[Daniel van Vugt]

Judging by the dates, this change might be related:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915/intel_display.c?h=v4.16-rc1=611032bfa71a7634e801142016f2d41485f8638f

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

Title:
  Colour banding and artefacts appear system-wide on an Asus Zenbook
  UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

[Daniel van Vugt]

** Tags added: visual-quality

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

Title:
  Colour banding and artefacts appear system-wide on an Asus Zenbook
  UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA with Intel HD 4400 graphics

[Daniel van Vugt]

Yes, based on what I can find, the Haswell UX303LA has about 61% sRGB
coverage so it sounds likely to be a 6-bit (AKA 18-bit) panel, which
makes it sound even more likely that comment #5 is the cause of the
problem.

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

Title:
  Colour banding and artefacts appear system-wide on an Asus Zenbook
  UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Asus Zenbook UX303 with Intel HD 4400 graphics

[Daniel van Vugt]

Oh, it's UX303LA to be exact :)

** Summary changed:

- Colour banding and artefacts appear system-wide on an Asus Zenbook UX303 with 
Intel HD 4400 graphics
+ Colour banding and artefacts appear system-wide on an Asus Zenbook UX303LA 
with Intel HD 4400 graphics

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

Title:
  Colour banding and artefacts appear system-wide on an Asus Zenbook
  UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Asus Zenbook UX303 with Intel HD 4400 graphics

[Daniel van Vugt]

It seems "Asus Zenbook UX303" covers many different models over the
years. Do you know which specific model (extra letters) the UX303 is?

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

Title:
  Colour banding and artefacts appear system-wide on an Asus Zenbook
  UX303LA with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

[Bug Watch Updater]

** Changed in: gnome-bluetooth
   Status: Unknown => Confirmed

** Changed in: gnome-bluetooth
   Importance: Unknown => Low

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions

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

[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Lucas Zanella]

Everything is ok with this new kernel. No erros.

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

Title:
  Samsung SSD corruption (fsck needed)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.13.0-21.24-generic 4.13.13

  
  I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 
17.04, which gave me this error after 2 weeks of usage. After that, I installed 
16.04 and used it for MONTHS without any problems, until it produced the same 
error this week. I think it has to do with the ubuntu updates, because I did 
one recently and one today, just before this problem. Could be a coincidence 
though.

  I notice the error when I try to save something on disk and it says me
  that the disk is in read-only mode:

  lz@lz:/var/log$ touch something
  touch: cannot touch 'something': Read-only file system

  
  lz@lz:/var/log$ cat syslog
  Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): 
ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming 
directory block 0

  
  lz@lz:/var/log$ dmesg
  [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.377374] Aborting journal on device nvme0n1p2-8.
  [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
  [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode 
#26607929: comm updatedb.mlocat: checksumming directory block 0
  [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" 
capability=12  capname="net_admin"

  Rebooting the ubuntu will give me a black terminal where I can run
  fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of
  orphaned inodes. The majority of time it boots back to the Ubuntu
  working good, but some times it boots to a broken ubuntu (no images,
  lots of things broken). I have to reinstall ubuntu then.

  Every time I reinstall my Ubuntu, I have to try lots of times until it
  installs without an Input/Output error. When it installs, I can use it
  for some hours without having the problem, but if I run the software
  updates, it ALWAYS crashes and enters in read-only mode, specifically
  in the part that is installing kernel updates.

  I noticed that Ubuntu installs updates automatically when they're for
  security reasons. Could this be the reason my Ubuntu worked for months
  without the problem, but then an update was applied and it broke?

  I thought that this bug was happening:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried
  different nvme_core.default_ps_max_latency_us= combinations, all them
  gave errors. I just changed to 0 and I had no error while using ubuntu
  (however I didn't test for a long time) but I still had the error
  after trying to update my ubuntu.

  My Samsung 512gb SSD is:

  SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q

  on a Razer Blade Stealth.

  I also asked this on ask ubuntu, without success:
  https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
  corruption-fsck-needed-probably-samsung-ssd-bug-afte

  Please help me, as I need this computer to work on lots of things :c
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lz 1088 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Razer Blade Stealth
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Intel HD Graphics 4400 system

[Daniel van Vugt]

Another possibility is that LCD panel dithering (controlled by the i915
kernel driver) has changed between kernel versions.

If your LCD panel is natively 6-bits per channel then the kernel should
be turning on dithering for you, since the shell is typically rendered
as 8-bits per channel. If dithering is not enabled then you will see
banding and effectively see a loss of 75% of your colours and gradients.

But the tricky part is for a developer to find a machine with the same
problem. The problem will be specific to your GPU model (the dithering
logic in i915 varies between generations), and specific to the LCD panel
type in that laptop. Effectively we will need to find a similar Haswell
laptop with a similar LCD type, which is the hard part...

** Summary changed:

- Colour banding and artefacts appear system-wide on an Intel HD Graphics 4400 
system
+ Colour banding and artefacts appear system-wide on an Asus Zenbook UX303 with 
Intel HD 4400 graphics

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

Title:
  Colour banding and artefacts appear system-wide on an Asus Zenbook
  UX303 with Intel HD 4400 graphics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  dmi.product.version: 1.0
  

[Kernel-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

[Daniel van Vugt]

** Bug watch added: GNOME Bug Tracker #775376
   https://bugzilla.gnome.org/show_bug.cgi?id=775376

** Also affects: gnome-bluetooth via
   https://bugzilla.gnome.org/show_bug.cgi?id=775376
   Importance: Unknown
   Status: Unknown

** Also affects: gnome-bluetooth (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-bluetooth (Ubuntu)
   Status: New => Confirmed

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions

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

[Kernel-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

[Daniel van Vugt]

** Summary changed:

- bluetooth does not turn on; settings interfaces are nonsensical
+ Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

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

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Kernel-packages] [Bug 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react

[Daniel van Vugt]

@brian-aljex,

That sounds like a potentially unrelated bug. Please log a separate bug
for that.

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

Title:
  [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then
  don't react

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

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

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

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

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

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

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

[Kernel-packages] [Bug 1749221] Re: kernel crash / BUG: unable to handle kernel paging request at fffffe3ed8000020

[Scott Moser]

Tetsuo,
Thanks for the info.  Removing 'apparmor=0' isn't an option right now both 
because MAAS doesn't let you control that and because it is there to work 
around other bugs (originally bug 1677336).

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

Title:
   kernel crash / BUG: unable to handle kernel paging request at
  fe3ed820

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  Booted under maas in rescue mode system console has the attached failure.
  First bit is

  [ 440.196466] BUG: unable to handle kernel paging request at
  fe3ed820

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic (not installed)
  ProcVersionSignature: User Name 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 33 Feb 13 15:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed 
with exit code 1:
  CRDA: N/A
  Date: Tue Feb 13 15:34:40 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=username/amd64/generic/xenial/daily/boot-kernel 
nomodeset 
root=squash:http://10.247.16.6:5248/images/username/amd64/generic/xenial/daily/squashfs
 ro ip=hostname:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc 
cloud-config-url=http://10.247.16.6:5240/MAAS/metadata/latest/by-id/sbgyxn/?op=get_preseed
 apparmor=0 log_host=10.247.16.6 log_port=514 --- console=ttyS1 
BOOTIF=01-ec:b1:d7:7f:2a:6c
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd03/05/2015:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"

[helm12]

It appears the issue is not occuring in 4.16-rc1

** Tags added: kernel-fixed-upstream

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

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

Title:
  Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in
  smb2_get_dfs_refer rc=-2"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 17.10 artful
  Kernel: x86_64 Linux 4.13.0-32.35-generic
  cifs-utils 2:6.7-1
  smbclient  2:4.6.7+dfsg-1ubuntu3.1

  Mounting an SMB share with
  
sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777

  in /etc/fstab gives the error: "CIFS VFS: ioctl error in
  smb2_get_dfs_refer rc=-2" in dmesg.

  Shares mounted this way are readable, but writing data to them (or using 
programs such as EasyTAG to write to them) ultimately fails. This bug did not 
occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the 
error, but this is a haphazard fix as SMB v3.0 carries many security features 
with it not avaliable in SMB 1.0.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago)
  UserGroups: libvirt libvirtd sudo wireshark
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-E/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

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

[Nick Reynolds]

I believe I have a workaround to this. I had exactly the same on 17.10
on an Acer Aspire One, reinstalled 16.04 and still had it. I also had it
clear up if the machine suspended and resumed.

It looked to me like it was related to the grub splash screen, just
based on it messing up before the GUI starts and the portion of the
screen that got corrupted.

I changed the grub config in /etc/default/grub to the following...

GRUB_CMDLINE_LINUX_DEFAULT="" <- edit the existing line
GRUB_GFXPAYLOAD_LINUX=text <- add this line

Then updated grub with sudo update-grub and rebooted.

Now it has a 100% text boot and no corruption of the screen.

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

Title:
  Desktop (screen) corrupted after upgrade to 17.10

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

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

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

  Computer is a Samsung NP-NC10 with 1GB RAM and Intel Atom CPU.
  (Sorry I didn't find time to test the beta!!!)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brian  2834 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=cf3c8f13-558d-4354-9a47-39b9837475b8
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=5a407644-80ca-4e5e-9d15-2fac5a1ad8d4 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-30 (19 days ago)
  UserGroups: audio dialout sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 11CA.M015.20090908.RHU
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: No Asset Tag
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr11CA.M015.20090908.RHU:bd09/08/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrNoAssetTag:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1742502] Re: 108 and 109 kernel hangs

[Joey Stanford]

Joe,

116 puts VMWARE into a loop. It forces a hard reboot somewhere during
the init process (scrolls by too fast). If I had NOPTI it boots
normally.  So I would say, no, 116 does not fix this.

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

Title:
  108 and 109 kernel hangs

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

Bug description:
  Overnight I had 2 of 12  16.04 servers brick with the 108 kernel. They
  also do not work with 109.  They work fine with 104. The other 10
  worked fine on both 108 and 109.

  All are hosted on VMWARE. The two broken ones stop at the same place.
  I was able to go back to the 104 kernel to get them working and pin
  the kernel version.

  Just for fun, I set zswap.enabled=0 and they both crashed with kthread
  starved for jiffies. They are both multi-processor with lots of ram
  and disk.

  I have a task from the Ubuntu Kernel team to try this with 'nopti'.
  I'll report back.

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

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

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Crashbit]

I have a problem with tinc and netplan.

I've using Ubuntu 17.10 server. When I try to start tincd daemon with systemd, 
it doesn't start. 
When start tinc daemon without systemd, it runs correct. 

Fail:
crashbit@sun:~$ sudo systemctl start tinc
crashbit@sun:~$ sudo systemctl status tinc
● tinc.service - Tinc VPN
   Loaded: loaded (/lib/systemd/system/tinc.service; enabled; vendor preset: 
enabled)
   Active: active (exited) since Thu 2018-02-15 00:58:30 CET; 20s ago
  Process: 26868 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 26868 (code=exited, status=0/SUCCESS)
  CPU: 1ms

feb 15 00:58:30 sun systemd[1]: Starting Tinc VPN...
feb 15 00:58:30 sun systemd[1]: Started Tinc VPN.

crashbit@sun:~$ ifconfig | grep cephnet
crashbit@sun:~$ 



Succes:

crashbit@sun:~$ sudo tincd -c /etc/tinc/cephnet/ -n cephnet
Both netname and configuration directory given, using the latter...
crashbit@sun:~$ ifconfig | grep cephnet
cephnet: flags=4305  mtu 1500
crashbit@sun:~$ 

---

crashbit@sun:/etc/netplan$ cat 01-netcfg.yaml 
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
enp129s0f0:
dhcp4: false

  bridges:
lxdbr0:
interfaces: [enp129s0f0]
addresses: [172.26.0.2/24]
gateway4: 172.26.0.1
parameters:
stp: false
forward-delay: 0
nameservers:
addresses: [172.26.0.5]   
crashbit@sun:/etc/netplan$

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  New
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  New
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  New
Status in ifmetric package in Ubuntu:
  New
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  New
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Committed
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  New
Status in vzctl package in Ubuntu:
  New
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: 

[Kernel-packages] [Bug 1738334] Re: hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn callback")

[Daniel Axtens]

Hi,

I installed 4.13.0-35-generic from artful-proposed. The kernel boots and
X starts fine, so this has passed verification.

Regards,
Daniel

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

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

Title:
  hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add
  io_mem_pfn callback")

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

Bug description:
  [SRU Justification]

  [Impact]
  On Artful kernels, X fails to start and a kernel splat is printed.

  This is cbecause ea642c3216cb ("drm/ttm: add io_mem_pfn callback") is
  incomplete: the hisilicon hibmc driver does not contain the callback
  and so the kernel tries to execute code at NULL.

  [Fix]
  There is a discussion and potential fix at 
https://lists.freedesktop.org/archives/dri-devel/2017-November/159002.html The 
fix hasn't landed yet and it looks like they're going to re-engineer the entire 
section instead.

  Rather than wait for that and deal with the massive regression
  potential, the fix I have picked to submit is very very minimal and
  touches only hibmc.

  [Regression Potential]
  Minimal - fix only touches hibmc driver. Tested on D05 board.

  [Testcase]
  Install patched kernel, try to start X. If it succeeds, the fix works. If 
there's a kernel splat, the fix does not work.

  [Notes]
  HiSilicon would really like this fix in Artful in such time so that when the 
next 16.04 point release ships in February, the HWE kernel will work with Xorg.

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

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

[Kernel-packages] [Bug 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29

[Joseph Salisbury]

** Tags added: pti

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

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

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

Title:
  [regression] hibernation (freezes on resume) since 4.13.0-25.29

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  After hibernating the system and than resuming it the system reboots
  notifying that it is resuming and than stops/freezes. The system does
  not respond to anything (no tty's other notifying textg are
  available).

  
  After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep 
functions as proposed.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jb 1717 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478
  InstallationDate: Installed on 2017-12-10 (34 days ago)
  InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124
  MachineType: Acer Aspire S3-391
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-26-generic N/A
   linux-backports-modules-4.13.0-26-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Hummingbird2
  dmi.board.vendor: Acer
  dmi.board.version: V2.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S3-391
  dmi.product.version: V2.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1746058] Re: CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

[Joseph Salisbury]

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

** This bug has been marked a duplicate of bug 1743812
   CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

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

Title:
  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  I'm checking:
  https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/

  :~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh
  [...]

  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
  * Mitigation 1
* Kernel is compiled with IBRS/IBPB support:  YES 
* Currently enabled features
  * IBRS enabled for Kernel space:  NO 
  * IBRS enabled for User space:  NO 
  * IBPB enabled:  NO 
  * Mitigation 2
* Kernel compiled with retpoline option:  NO 
* Kernel compiled with a retpoline-aware compiler:  NO 
* Retpoline enabled:  NO 
  > STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with 
retpoline are needed to mitigate the vulnerability)

  [...]

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1296 F pulseaudio
caravena   1698 F pulseaudio
  Date: Mon Jan 29 15:03:34 2018
  InstallationDate: Installed on 2017-10-13 (108 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-32-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ 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.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-10-13 (118 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  Tags:  bionic
  Uname: Linux 4.15.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 

[Kernel-packages] [Bug 1742675] Re: after upgrade to linux-image-extra-4.13.0-26-generic the system does not start at all

[Joseph Salisbury]

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

** Tags removed: pti

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

Title:
  after upgrade to linux-image-extra-4.13.0-26-generic  the system does
  not start at all

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to linux-image-extra-4.13.0-26-generic  the system does not 
start at all.
  Only restart through Advanced Options with 
linux-image-extra-4.10.0-42-generic helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Jan 11 15:20:26 2018
  InstallationDate: Installed on 2017-06-23 (201 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2017-06-24T18:05:02.372991

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

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

[Kernel-packages] [Bug 1743812] Re: CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

[Joseph Salisbury]

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

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

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

Title:
  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

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

Bug description:
  Hello,

  I'm testing script:
  https://www.tecmint.com/check-and-patch-meltdown-cpu-vulnerability-in-linux/



  :~/spectre-meltdown-checker$ sudo ./spectre-meltdown-checker.sh
  [sudo] password for caravena: 
  Spectre and Meltdown mitigation detection tool v0.31

  Checking for vulnerabilities against running kernel Linux 4.13.0-30-generic 
#33-Ubuntu SMP Mon Jan 15 19:45:48 UTC 2018 x86_64
  CPU is Intel(R) Core(TM) i3-2377M CPU @ 1.50GHz

  CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
  * Checking count of LFENCE opcodes in kernel:  YES 
  > STATUS:  NOT VULNERABLE  (114 opcodes found, which is >= 70, heuristic to 
be improved when official patches become available)

  CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
  * Mitigation 1
  *   Hardware (CPU microcode) support for mitigation
  * The SPEC_CTRL MSR is available:  NO 
  * The SPEC_CTRL CPUID feature bit is set:  NO 
  *   Kernel support for IBRS:  YES 
  *   IBRS enabled for Kernel space:  NO 
  *   IBRS enabled for User space:  NO 
  * Mitigation 2
  *   Kernel compiled with retpoline option:  NO 
  *   Kernel compiled with a retpoline-aware compiler:  NO 
  > STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with 
retpoline are needed to mitigate the vulnerability)

  CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
  * Kernel supports Page Table Isolation (PTI):  YES 
  * PTI enabled and active:  YES 
  * Checking if we're running under Xen PV (64 bits):  NO 
  > STATUS:  NOT VULNERABLE  (PTI mitigates the vulnerability)

  A false sense of security is worse than no security at all, see
  --disclaimer

  
  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-30-generic 4.13.0-30.33
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 13:18:45 2018
  InstallationDate: Installed on 2017-10-13 (96 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-30-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-30-generic N/A
   linux-backports-modules-4.13.0-30-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1748470] Re: Spectre V2 : System may be vulnerable to spectre v2

[Joseph Salisbury]

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

** This bug has been marked a duplicate of bug 1743812
   CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS 

[Kernel-packages] [Bug 1742502] Re: 108 and 109 kernel hangs

[Joseph Salisbury]

Can you see if this bug still occurs with the 116 kernel in -proposed?

https://launchpad.net/ubuntu/+source/linux/4.4.0-116.140

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

Title:
  108 and 109 kernel hangs

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

Bug description:
  Overnight I had 2 of 12  16.04 servers brick with the 108 kernel. They
  also do not work with 109.  They work fine with 104. The other 10
  worked fine on both 108 and 109.

  All are hosted on VMWARE. The two broken ones stop at the same place.
  I was able to go back to the 104 kernel to get them working and pin
  the kernel version.

  Just for fun, I set zswap.enabled=0 and they both crashed with kthread
  starved for jiffies. They are both multi-processor with lots of ram
  and disk.

  I have a task from the Ubuntu Kernel team to try this with 'nopti'.
  I'll report back.

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

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

[Kernel-packages] [Bug 1743156] Re: [regression] 4.4.0-110 doesn't load AMD microcode

[Joseph Salisbury]

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

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

Title:
  [regression] 4.4.0-110 doesn't load AMD microcode

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

Bug description:
  When booting my AMD system with 4.4.0-109.132, the microcode is
  updated:

  root@ocelot:~# journalctl -k | grep microcode
  Jan 13 15:26:36 ocelot kernel: microcode: CPU0: patch_level=0x0500010d
  Jan 13 15:26:36 ocelot kernel: microcode: CPU1: patch_level=0x0500010d
  Jan 13 15:26:36 ocelot kernel: microcode: Microcode Update Driver: v2.01 
, Peter Oruba
  Jan 13 15:26:36 ocelot kernel: microcode: CPU0: new patch_level=0x05000119
  Jan 13 15:26:36 ocelot kernel: microcode: CPU1: new patch_level=0x05000119

  However, with 4.4.0-110.133, no microcode is loaded:

  root@ocelot:~# journalctl -k | grep microcode
  # nothing

  Extra information on the system:

  root@ocelot:~# sed -n '1,/^$/ p' /proc/cpuinfo 
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 20
  model : 2
  model name: AMD C-60 APU with Radeon(tm) HD Graphics
  stepping  : 0
  microcode : 0x5000119
  cpu MHz   : 800.000
  cache size: 512 KB
  physical id   : 0
  siblings  : 2
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 6
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb 
rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni 
monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch ibs skinit wdt cpb hw_pstate kaiser vmmcall arat npt 
lbrv svm_lock nrip_save pausefilter
  bugs  : fxsave_leak sysret_ss_attrs
  bogomips  : 1999.97
  TLB size  : 1024 4K pages
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management: ts ttp tm stc 100mhzsteps hwpstate cpb

  root@ocelot:~# lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  root@ocelot:~# apt-cache policy amd64-microcode
  amd64-microcode:
Installed: 2.20160316.1
Candidate: 2.20160316.1
Version table:
   *** 2.20160316.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-110-generic 4.4.0-110.133
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 13 15:26 seq
   crw-rw 1 root audio 116, 33 Jan 13 15:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sat Jan 13 15:30:51 2018
  HibernationDevice: RESUME=UUID=cfe87834-be9d-4a32-93d1-3f2b655e58af
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: System manufacturer System Product Name
  PciMultimedia:
   
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=9696399d-3bed-4126-b203-7672f2ea0576 ro hugepages=3072 kaslr 
nmi_watchdog=0 possible_cpus=2 pti=on transparent_hugepage=never vsyscall=none
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0502
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: C60M1-I
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

[Joseph Salisbury]

** Tags removed: kernel-key pti

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

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

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

[Kernel-packages] [Bug 1749592] Re: Bluetooth: hci0: last event is not cmd complete (0x0f)

[Joseph Salisbury]

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

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

Title:
  Bluetooth: hci0: last event is not cmd complete (0x0f)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [  153.651709] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  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
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1771 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Wed Feb 14 18:06:04 2018
  InstallationDate: Installed on 2017-10-13 (124 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-10-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1747625] Re: [v4.13, mlx5_core] Oops: 0000 [#1] SMP PTI

[Joseph Salisbury]

Please ignore the request for testing of the mainline kernel in comment
#12.  It would be best to test the 4.13 -proposed kernel, which can be
downloaded from:

https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/14341641

** Tags added: kernel-key

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

Title:
  [v4.13,mlx5_core] Oops:  [#1] SMP PTI

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

Bug description:
  PowerEdge R730
  4.13.0-26-generic #29~16.04.2-Ubuntu
  mlx5_core firmware version: 14.20.1820

  kernel trace: https://pastebin.ubuntu.com/26529021/

  Issue happened when I issued "reboot" command. Other nodes with same
  specifications and software versions didn't hit this bug.

  A new "reboot" on the node that panic'ed didn't hit the bug.

  I've set "pti=off" on all of them for now.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb  5 13:07 seq
   crw-rw 1 root audio 116, 33 Feb  5 13:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=2344957a-f5ed-46a7-87a5-255ab83876fb ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200 panic=30 raid=noautodetect 
modprobe.blacklist=floppy
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd netdev plugdev sudo 
video
  _MarkForUpload: False
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.5
  dmi.board.name: 04N3DF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.5:bd09/06/2016:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn04N3DF:rvrA10:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1749221] Re: kernel crash / BUG: unable to handle kernel paging request at fffffe3ed8000020

[Joseph Salisbury]

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

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

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

Title:
   kernel crash / BUG: unable to handle kernel paging request at
  fe3ed820

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  Booted under maas in rescue mode system console has the attached failure.
  First bit is

  [ 440.196466] BUG: unable to handle kernel paging request at
  fe3ed820

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic (not installed)
  ProcVersionSignature: User Name 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 33 Feb 13 15:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed 
with exit code 1:
  CRDA: N/A
  Date: Tue Feb 13 15:34:40 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=username/amd64/generic/xenial/daily/boot-kernel 
nomodeset 
root=squash:http://10.247.16.6:5248/images/username/amd64/generic/xenial/daily/squashfs
 ro ip=hostname:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc 
cloud-config-url=http://10.247.16.6:5240/MAAS/metadata/latest/by-id/sbgyxn/?op=get_preseed
 apparmor=0 log_host=10.247.16.6 log_port=514 --- console=ttyS1 
BOOTIF=01-ec:b1:d7:7f:2a:6c
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd03/05/2015:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1747625] Re: [v4.13, mlx5_core] Oops: 0000 [#1] SMP PTI

[Joseph Salisbury]

Also, if possible, it would be great if we could get access to the HW
for debugging.  Feel free to reach out on #stable-kernel on
IRC(Canonical server) or by email.

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

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

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

Title:
  [v4.13,mlx5_core] Oops:  [#1] SMP PTI

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

Bug description:
  PowerEdge R730
  4.13.0-26-generic #29~16.04.2-Ubuntu
  mlx5_core firmware version: 14.20.1820

  kernel trace: https://pastebin.ubuntu.com/26529021/

  Issue happened when I issued "reboot" command. Other nodes with same
  specifications and software versions didn't hit this bug.

  A new "reboot" on the node that panic'ed didn't hit the bug.

  I've set "pti=off" on all of them for now.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb  5 13:07 seq
   crw-rw 1 root audio 116, 33 Feb  5 13:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=2344957a-f5ed-46a7-87a5-255ab83876fb ro console=tty0 
console=ttyS0,115200 console=ttyS1,115200 panic=30 raid=noautodetect 
modprobe.blacklist=floppy
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy libvirtd netdev plugdev sudo 
video
  _MarkForUpload: False
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.5
  dmi.board.name: 04N3DF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.5:bd09/06/2016:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn04N3DF:rvrA10:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R730
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1749250] Re: linux: 4.15.0-10.11 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the 4.15.0-10.11 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  phase: Uploaded
+ kernel-phase-changed:Wednesday, 14. February 2018 21:30 UTC
+ kernel-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 4.15.0-10.11 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- phase: Uploaded
- kernel-phase-changed:Wednesday, 14. February 2018 21:30 UTC
- kernel-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.15.0-10.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

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

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1748470] Re: Spectre V2 : System may be vulnerable to spectre v2

[Cristian Aravena Romero]

Hello Joseph,

Thanks for you work :-)


Linux version: Ubuntu 4.15.0-10.11-generic 4.15.3

$tail /sys/devices/system/cpu/vulnerabilities/*
==> /sys/devices/system/cpu/vulnerabilities/meltdown <==
Mitigation: PTI

==> /sys/devices/system/cpu/vulnerabilities/spectre_v1 <==
Mitigation: __user pointer sanitization

==> /sys/devices/system/cpu/vulnerabilities/spectre_v2 <==
Mitigation: Full generic retpoline

Regards,
--
Cristian

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Bluetooth: hci0: last event is not cmd complete (0x0f)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  dmesg:
  [  153.651709] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  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
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1771 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Wed Feb 14 18:06:04 2018
  InstallationDate: Installed on 2017-10-13 (124 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-10-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1749592] [NEW] Bluetooth: hci0: last event is not cmd complete (0x0f)

[Cristian Aravena Romero]

Public bug reported:

Hello,

dmesg:
[  153.651709] Bluetooth: hci0: last event is not cmd complete (0x0f)

Regards,
--
Cristian

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
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   1771 F pulseaudio
CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
Date: Wed Feb 14 18:06:04 2018
InstallationDate: Installed on 2017-10-13 (124 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-10-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-10-generic N/A
 linux-backports-modules-4.15.0-10-generic  N/A
 linux-firmware 1.170
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug bionic package-from-proposed

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

Title:
  Bluetooth: hci0: last event is not cmd complete (0x0f)

Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [  153.651709] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  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
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1771 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Wed Feb 14 18:06:04 2018
  InstallationDate: Installed on 2017-10-13 (124 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-10-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1739891] Re: hisi_sas: Add ATA command support for SMR disks

[dann frazier]

I don't have an SMR disk to test, but I have regression tested on a non-
SMR disk by running iozone3 while resetting the bus (using sg_reset),
and observed no errors.


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

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

Title:
  hisi_sas: Add ATA command support for SMR disks

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  SATA SMR disks are not supported.

  [Test Case]
  Connect and use a SATA SMR disk

  [Regression Risk]
  The fix is restricted to a single driver, adding only new command support, 
mitigating the regression risk of previous commands.

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

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

[Kernel-packages] [Bug 1739807] Re: hisi_sas: driver robustness fixes

[dann frazier]

artful verification - I've completed the iozone test on a filesystem
atop a disk connected to a hisi sas controller w/o error.

** Description changed:

  [Impact]
  There are several bugs in the driver that can cause it to fail during 
teardown/error recovery.
  
  [Test Case]
  Regression tested by issuing sg_reset commands in a loop during an iozone3 
run on a disk attached to a hisi_sas controller.
  
- $ iozone -i &
+ $ iozone -a &
  $ while :; do sudo sg_reset --device /dev/sda; sleep 5; done
  
  [Regression Risk]
  All fixes are encapsulated within a single driver which was explicitly tested 
for regressions.

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

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

Title:
  hisi_sas: driver robustness fixes

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

Bug description:
  [Impact]
  There are several bugs in the driver that can cause it to fail during 
teardown/error recovery.

  [Test Case]
  Regression tested by issuing sg_reset commands in a loop during an iozone3 
run on a disk attached to a hisi_sas controller.

  $ iozone -a &
  $ while :; do sudo sg_reset --device /dev/sda; sleep 5; done

  [Regression Risk]
  All fixes are encapsulated within a single driver which was explicitly tested 
for regressions.

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

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

[Kernel-packages] [Bug 1746613] Re: freezes after resuming from disk hibernation

[Eduardo]

4.15 is not yet in xenial-updates, so it is risky to test it in a
production computer.

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

Title:
  freezes after resuming from disk hibernation

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Resuming from disk hibernation works fine with previous kernel
  4.10.0-32. Now the computer freezes on a black screen at the end, just
  after decompressing the image.

  I am using uswsuspc and s2disk to hibernate successfully with the
  previous kernel 4.10.-32

  Output from lsb_release -rd:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Output from uname -r:
  4.13.0-32-generic

  (If I boot with 4.10.0-28-generic from advanced options in grub,
  resuming works fine)

  Output from lspci:
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB xHCI Host Controller (rev 04)
  00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 1 (rev c4)
  00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 2 (rev c4)
  00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 3 (rev c4)
  00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller 
(rev 04)
  00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port 
SATA Controller [AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus 
Controller (rev 04)
  03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter 
(rev 01)
  04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785 Gigabit 
Ethernet PCIe (rev 10)
  04:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card 
Reader (rev 10)

  Please tell me what else can I provide to help with this. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Wed Jan 31 16:44:27 2018
  InstallationDate: Installed on 2018-01-28 (3 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2018-01-28T01:19:21.792226
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eguerras   2172 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=b933b9cf-bad2-4f44-a703-b408e19a611a
  InstallationDate: Installed on 2018-01-28 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Acer V5-171
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=4a50e1e8-56d9-413e-9954-5564a31d ro intel_pstate=disable 
resume=/dev/sda2
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Mimic
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.08
  dmi.modalias: 
dmi:bvnAcer:bvrV2.08:bd11/06/2012:svnAcer:pnV5-171:pvrV2.08:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.08:
  dmi.product.family: Type1Family
  

[Kernel-packages] [Bug 1743529] Re: ISST-LTE:PowerNV:Ubuntu1804:Witherspoon:whip: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

[Joseph Salisbury]

** Also affects: linux (Ubuntu Bionic)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

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

Title:
  ISST-LTE:PowerNV:Ubuntu1804:Witherspoon:whip: System hung with Kernel
  panic -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  
  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the crash 
kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

  root@whip:~# kdump-config status
  current state   : ready to kdump

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048 
  [   85.731745] NUMA 
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast 
i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core 
syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme 
devlink nvme_core
  [   85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   85.732764] task: c03fcb141700 task.stack: c03fc2374000
  [   85.732858] NIP: c078f588 LR: c07904b8 CTR: 
c078f560
  [   85.732977] REGS: c03fc23779f0 TRAP: 0300   Not tainted  
(4.13.0-17-generic)
  [   85.733066] MSR: 90009033 
  [   85.733075]   CR: 2842  XER: 2004
  [   85.733201] CFAR: c07904b4 DAR:  DSISR: 4200 
SOFTE: 1 
  [   85.733201] GPR00: c07904b8 c03fc2377c70 c15f6000 
0063 
  [   85.733201] GPR04: c03feedfade8 c03feee12068 90009033 
000a 
  [   85.733201] GPR08: 0007 0001  
90001003 
  [   85.733201] GPR12: c078f560 c7a66900 10180df8 
10189e30 
  [   85.733201] GPR16: 10189ea8 10151210 1018bd58 
1018de48 
  [   85.733201] GPR20: 321168d8 0001 10164590 
10163bb0 
  [   85.733201] GPR24: 7fffcfa6e7d4 7fffcfa6e7d0 c14fa570 
0002 
  [   85.733201] GPR28: 0063 0004 c14822f4 
c14fa910 
  [   85.734116] NIP 

[Kernel-packages] [Bug 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react

[KEYofR]

I have this on numerous 4.13 and 4.14 kernels from synaptic (17.10 repos) and 
ubuntu-mainline ppa.
IE today: 
4.14.17-041417-generic #201802031230 SMP Sat Feb 3 17:31:50 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

This is on a 5th get lenovo x1 carbon using the built-in bluetooth and a
few different bt mice, IE HP and Verbatim.

The rfkill block/unblock commands above did nothing for me.

cpu is eating my battery and the only process is "kworker"

 2615 root  20   0   0  0  0 R  85.3  0.0   6:02.78 kworker/0:2 

 3365 root  20   0   45376   3928   3260 R   0.3  0.0   0:00.04 top 

1 root  20   0  220176   8432   6316 S   0.0  0.1   0:02.59 systemd 

2 root  20   0   0  0  0 S   0.0  0.0   0:00.00 kthreadd

4 root   0 -20   0  0  0 I   0.0  0.0   0:00.00 
kworker/0:0H
6 root   0 -20   0  0  0 I   0.0  0.0   0:00.00 
mm_percpu_wq

powertop says...

The battery reports a discharge rate of 18.6 W
The estimated remaining time is 2 hours, 26 minutes

Summary: 655.9 wakeups/second,  0.0 GPU ops/seconds, 0.0 VFS ops/sec and
5.6% CPU use

Usage   Events/sCategory   Description
 80.0%  Device Display backlight
  6.1 ms/s 256.3Interrupt  [9] acpi
 23.8 ms/s 233.4kWork  acpi_os_execute_deferred
  2.7 ms/s  67.4Process/usr/lib/xorg/Xorg -core 
:0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolis
  1.0 ms/s  25.4Processlxterminal
445.6 µs/s  13.9Interrupt  PS/2 Touchpad / Keyboard 
/ Mouse
 42.0 µs/s  13.5Process[xfsaild/nvme0n1]
442.2 µs/s  12.2Processlxpanel --profile Lubuntu
...

I have to reboot to clear it!

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

Title:
  [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then
  don't react

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

Bug description:
  SRU Justification

  Impact: Bluetooth peripherals work initially but stop working shortly
  with Linux 4.13.

  Fix: Updated firmware from Intel containing a fix for the issue.

  Regression Potential: Any firmware updates may bring regressions,
  however this is a bug fix update and therefore regression potential is
  expected to be minimal.

  ---

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

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  ---
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp.
   Bus 001 Device 005: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5664 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: 

[Kernel-packages] [Bug 1746988] Re: [Ubuntu 18.04 FEAT] OpenCAPI enabling

[Joseph Salisbury]

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

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

Title:
  [Ubuntu 18.04 FEAT] OpenCAPI enabling

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  [FEATURE] OpenCAPI enabling

  OpenCAPI is an Open Interface Architecture that allows any
  microprocessor to attach to

*  Coherent user-level accelerators and I/O devices
*  Advanced memories accessible via read/write or user-level DMA semantics
*  Agnostic to processor architecture

  
  This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be 
included in 4.16 and it will need to be backported to 4.15:

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

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

[Kernel-packages] [Bug 1732238] Re: arm64: Unfair rwlock can stall the system

[dann frazier]

Artful verification: I was able to successfully run the above stress-ng
commmand w/o any errors on the console.

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

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

Title:
  arm64: Unfair rwlock can stall the system

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

Bug description:
  [Impact]
  There is a long-standing upstream bug with the ARM64 specific implementation 
of RW locks. The implementation can starve writers under lock contention 
leading to RCU stalls, driver timeouts and general system instability.

  [Test Case]
  $ stress-ng --kill 0 -t 300 -v

  You'll see the console fill with messages like:

  [ 2534.423119] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 2534.428606]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=6770
  [ 2534.437029](detected by 0, t=15005 jiffies, g=1479, c=1478, q=473)
  [ 2714.623691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [ 2714.629181]192-...: (1 ticks this GP) idle=b6e/140/0 
softirq=578/578 fqs=12819
  [ 2714.637692](detected by 116, t=60058 jiffies, g=1479, c=1478, 
q=1736)
  [ 2747.216955] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[kworker/0:5:1464]
  [ 2775.399061] watchdog: BUG: soft lockup - CPU#13 stuck for 123s! 
[systemd-network:2936]

  [Regression Risk]
  The proposed fix for this comprises clean cherry-picks from the v4.15 merge 
window. The code modified for this fix is restricted to x86 & arm64, as they 
are the only Ubuntu architectures that define ARCH_USE_QUEUED_LOCKS. Fix 
verified on a 228 CPU arm64 (ThunderX2) server and regression tested on a 
128-cpu x86 system using stress-ng and locktorture.

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

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

[Kernel-packages] [Bug 1738073] Re: thunderx2: i2c driver PEC and ACPI clock fixes

[dann frazier]

artful verification:
ubuntu@starbuck:~$ dmesg | grep xlp9xx
[   46.890471] ipmi_ssif: Trying SPMI-specified SSIF interface at i2c address 
0x10, adapter xlp9xx-i2c, slave address 0x0


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

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

Title:
  thunderx2: i2c driver PEC and ACPI clock fixes

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

Bug description:
  [Impact]
  The i2c input frequency is currently hardcoded in the driver. This may not 
match the actual frequency used by the platform. Upstream has updated the 
driver to pull the frequency from firmware.

  [Test Case]
  The updated driver will detect the CAV9007 ACPI ID:

  ubuntu@starbuck:~$ dmesg | grep xlp9xx-i2c
  [   47.723562] xlp9xx-i2c CAV9007:02: i2c transfer timed out!
^^^
  The old driver will not claim this device.

  [Regression Risk]
  The changes are restricted to a driver that appears to be only used on MIPS 
platforms (which we don't support) and Cavium ThunderX2 systems that we've 
specifically tested upon.

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

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

[Kernel-packages] [Bug 1749143] Re: BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad address

[Joseph Salisbury]

I'll mark this bug as "Fix Released" since the linux-
image-4.4.0-116-generic kernel solves it.  If the bug re-appears, change
the status back to "Confirmed".

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

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

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

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

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

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

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

Bug description:
  Hello,

  We test the -proposed packages before our ±25000 user servers get a
  chance to download it when it's in stable and we have an issue since
  the package linux-image-4.4.0-113-generic and linux-
  image-4.4.0-115-generic.

  We tried on KVM virtual machines

  To reproduce the problem, execute:

  # fping -t50 -r2 127.0.0.1
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1 is unreachable

  We have no problem with ping:

  # ping -c 1 127.0.0.1
  PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
  64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.046 ms
  
  --- 127.0.0.1 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.046/0.046/0.046/0.000 ms

  fping is working fine under kernel 4.4.0-112:

  # fping -t50 -r2 127.0.0.1
  127.0.0.1 is alive

  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 févr. 13 16:40 seq
   crw-rw 1 root audio 116, 33 févr. 13 16:40 timer
  AplayDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/eolebase--vg-swap_1
  IwConfig: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-115-generic 
root=/dev/mapper/hostname--vg-root ro rootdelay=90
  ProcVersionSignature: Ubuntu 4.4.0-115.139-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-115-generic N/A
   linux-backports-modules-4.4.0-115-generic  N/A
   linux-firmware 1.157.16
  RfKill: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Tags:  xenial
  Uname: Linux 4.4.0-115-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1749329] Re: BUG: Bad rss-counter state mm:ffff9ac8374f39c0 idx:1 val:1

[BertN45]

Up to now it has been a one time event.

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

Title:
  BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No additional information.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1204 F pulseaudio
bertadmin   1928 F pulseaudio
  Date: Tue Feb 13 20:59:15 2018
  Failure: oops
  InstallationDate: Installed on 2017-12-22 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Intel HD Graphics 4400 system

[Øystein Alværvik]

I just installed the 4.15.0-10 kernel that you provided and rebooted.
The colours didn't improve; the same artefacts and banding still appear
like they did on kernel 4.13.

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

Title:
  Colour banding and artefacts appear system-wide on an Intel HD
  Graphics 4400 system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1749329] Re: BUG: Bad rss-counter state mm:ffff9ac8374f39c0 idx:1 val:1

[Joseph Salisbury]

Do you have a way to reproduce this bug, or was it a one time event?

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

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

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

Title:
  BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No additional information.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1204 F pulseaudio
bertadmin   1928 F pulseaudio
  Date: Tue Feb 13 20:59:15 2018
  Failure: oops
  InstallationDate: Installed on 2017-12-22 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1749422] Re: kvm-unit-test failed to build on s390x Artful

[Joseph Salisbury]

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

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

** Tags added: kernel-da-key

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

Title:
  kvm-unit-test failed to build on s390x Artful

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This is not a regression, this error could be found in 4.13.0-30.33
  test report as well.

  This test was not started before 4.13.0-22.25, not sure why.

  
  gcc -std=gnu99 -ffreestanding -I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-O2 -march=z900 -fno-delete-null-pointer-checks -g -MMD -MF 
lib/s390x/.asm-offsets.d -Wall -Wwrite-strings -Wclobbered -Wempty-body 
-Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Werror 
-fomit-frame-pointer -Wno-frame-address -fno-pic -no-pie 
-Wmissing-parameter-type -Wold-style-declaration -Woverride-init -fverbose-asm 
-S -o lib/s390x/asm-offsets.s lib/s390x/asm-offsets.c
  (set -e; echo "#ifndef __ASM_OFFSETS_H__"; echo "#define __ASM_OFFSETS_H__"; 
echo "/*"; echo " * Generated file. DO NOT MODIFY."; echo " *"; echo " */"; 
echo ""; sed -ne "/^->/{s:->#\(.*\):/* \1 */:; s:^->\([^ ]*\) [\$#]*\([-0-9]*\) 
\(.*\):#define \1 \2 /* \3 */:; s:^->\([^ ]*\) [\$#]*\([^ ]*\) \(.*\):#define 
\1 \2 /* \3 */:; s:->::; p;}" lib/s390x/asm-offsets.s; echo ""; echo "#endif" ) 
> lib/s390x/asm-offsets.h
  cp -f lib/s390x/asm-offsets.h lib/generated/
  gcc -std=gnu99 -ffreestanding -I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-O2 -march=z900 -fno-delete-null-pointer-checks -g -MMD -MF s390x/.selftest.d 
-Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized 
-Wignored-qualifiers -Wunused-but-set-parameter -Werror -fomit-frame-pointer 
-Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type 
-Wold-style-declaration -Woverride-init -c -o s390x/selftest.o s390x/selftest.c
  gcc -std=gnu99 -ffreestanding -I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-O2 -march=z900 -fno-delete-null-pointer-checks -g -MMD -MF lib/.argv.d -Wall 
-Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers 
-Wunused-but-set-parameter -Werror -fomit-frame-pointer -Wno-frame-address 
-fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration 
-Woverride-init -c -o lib/argv.o lib/argv.c
  gcc -std=gnu99 -ffreestanding -I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-O2 -march=z900 -fno-delete-null-pointer-checks -g -MMD -MF lib/.printf.d -Wall 
-Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers 
-Wunused-but-set-parameter -Werror -fomit-frame-pointer -Wno-frame-address 
-fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration 
-Woverride-init -c -o lib/printf.o lib/printf.c
  gcc -std=gnu99 -ffreestanding -I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-O2 -march=z900 -fno-delete-null-pointer-checks -g -MMD -MF lib/.string.d -Wall 
-Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers 
-Wunused-but-set-parameter -Werror -fomit-frame-pointer -Wno-frame-address 
-fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration 
-Woverride-init -c -o lib/string.o lib/string.c
  gcc -std=gnu99 -ffreestanding -I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-O2 -march=z900 -fno-delete-null-pointer-checks -g -MMD -MF lib/.abort.d -Wall 
-Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers 
-Wunused-but-set-parameter -Werror -fomit-frame-pointer -Wno-frame-address 
-fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration 
-Woverride-init -c -o lib/abort.o lib/abort.c
  gcc -std=gnu99 -ffreestanding -I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-O2 -march=z900 -fno-delete-null-pointer-checks -g -MMD -MF lib/.report.d -Wall 
-Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers 
-Wunused-but-set-parameter -Werror -fomit-frame-pointer -Wno-frame-address 
-fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration 
-Woverride-init -c -o lib/report.o lib/report.c
  gcc -std=gnu99 -ffreestanding -I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-O2 -march=z900 -fno-delete-null-pointer-checks -g -MMD -MF lib/.stack.d -Wall 
-Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers 
-Wunused-but-set-parameter -Werror -fomit-frame-pointer -Wno-frame-address 
-fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration 
-Woverride-init -c -o lib/stack.o lib/stack.c
  gcc -std=gnu99 -ffreestanding -I 
/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib 
-O2 -march=z900 

[Kernel-packages] [Bug 1749420] Re: Colour banding and artefacts appear system-wide on an Intel HD Graphics 4400 system

[Joseph Salisbury]

Can you see if this bug still happens with the latest bionic kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/14347009

To test this kernel, install both the linux-image and linux-image-extra
.deb packages.

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

** Tags added: needs-bisect

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

Title:
  Colour banding and artefacts appear system-wide on an Intel HD
  Graphics 4400 system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  - Ubuntu 18.04 (with updates as of 14 Feb 2018).
  - Laptop: Asus Zenbook UX303
  - CPU: Intel i5 4210U
  - Graphics: Intel HD 4400

  Problem description: Colour artefacts and banding in all apps.
  Graphics, photos and videos display as though the colour range is
  improperly configured.

  See this photo of a 1080p video taken with a camera (poor quality, but
  illustrates the issue): https://ubuntucommunity.s3-us-
  
east-2.amazonaws.com/original/2X/c/c8f266715226953c6a77db6367ff9b7895784e35.jpg

  Look at the sky’s light colours. They display with smooth gradients on
  Ubuntu 16.04, but as the photo illustrates 18.04 seems to display the
  video with a smaller range of white colours. This is the most apparent
  with either very dark or very light colours. Even on window titlebars
  the banding is visible (displayed as lines with different shades of
  grey/black).

  Compared with a PrtSc shot of the same image:
  https://i.imgur.com/VkOSCaQ.png

  The artefacts are not present on PrtSc shots that are taken on Ubuntu
  18.04 but viewed on a different system (16.04 and Windows).

  Installing a previous kernel version fixes the issue completely. I
  used UKUU Update Utility to install kernel 4.4 (the same that I use in
  Ubuntu 16.04 without issues) and upon a reboot with 4.4 running on
  18.04 everything displayed smoothly. So this indicates that the system
  might be using a sub-optimal colour depth with the newer kernel?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ystein 1344 F pulseaudio
   /dev/snd/controlC1:  ystein 1344 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 11:25:43 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d0bae648-a4d8-454c-b9fc-4cc04874d6c1
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX303LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=25279d7b-cc8a-4fee-9088-cfc69607cbca ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LA
  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.:bvrUX303LA.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LA
  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/1749420/+subscriptions

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

[Kernel-packages] [Bug 1749427] Re: Unable to create KVM with uvtool on Moonshot arm64 system

[Joseph Salisbury]

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

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

** Tags added: kernel-da-key

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

Title:
  Unable to create KVM with uvtool on Moonshot arm64 system

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Not sure if this is related to bug 1452016, or just a HW issue:

  With the uvt-kvm create command on this Artful system, it returns:
  uvt-kvm: error: libvirt: unsupported configuration: ACPI requires UEFI on 
this architecture

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 14 11:01 seq
   crw-rw 1 root audio 116, 33 Feb 14 11:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed Feb 14 11:09:44 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748901] Re: System hang with Virtualbox & kernel 4.13.0-32-generic

[Joseph Salisbury]

It sounds like the latest mainline kernel might not be testable then.
It might be good to test the latest bionic kernel:

https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/bootstrap/+build/14347009

If it does not fix the bug, we can try bisecting the 4.13 kernel to see
what commit introduced this.

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

Title:
  System hang with Virtualbox & kernel 4.13.0-32-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  Some (maybe all) kernels in the 4.13.0 series are hanging with
  Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a
  Virtualbox VM, the VM's window appears, clears to black, and then the
  mouse freezes. I do NOT see any BIOS/EFI information or boot loader in
  the VM; the hang occurs before those messages appear. (I've tried this
  with the VM set for both BIOS and EFI booting with no difference.) The
  host computer also stops responding to pings or anything else; the
  only solution seems to be to do a cold reset. I've tested this on a
  different computer running the same kernel and the latest Ubuntu 18.04
  alpha and had no problems there. Here's some data from the affected
  computer:

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

  $ cat /proc/version_signature 
  Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13

  $ dpkg -s virtualbox | grep Version
  Version: 5.0.40-dfsg-0ubuntu1.16.04.2

  This problem does NOT occur with earlier kernels, such as those in the 4.4.0 
series.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   2661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2014-05-02 (1382 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro 
root=/dev/mapper/hostname-trusty_crypt  quiet splash  
initrd=\initrd.img-4.13.0-32-generic
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago)
  UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare 
sbuild sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AFZ.015.161206.KS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP740U5M-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: SAMSUNG ATIV
  dmi.product.name: 740U5M
  dmi.product.version: P02AFZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1749401] Re: package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to install/upgrade: package linux-image-4.4.0-83-generic is not ready for configuration cannot configure (c

[Joseph Salisbury]

You may need to run the following from a terminal:

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

Then re-install the package or updates.

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


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

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

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

Title:
  package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to
  install/upgrade: package linux-image-4.4.0-83-generic is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My computer failed to boot correctly a few weeks ago, and after
  restarting several times with no success, I booted with a previous
  line on the menu that comes up.  That seemed to work, but now there
  are further problems.

  I'm afraid I am not very tech-savvy, as you can probably tell.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic 4.4.0-83.106
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marilyn1628 F pulseaudio
  Date: Wed Feb 14 09:13:16 2018
  DuplicateSignature:
   package:linux-image-4.4.0-83-generic:4.4.0-83.106
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package linux-image-4.4.0-83-generic (--configure):
package linux-image-4.4.0-83-generic is not ready for configuration
  ErrorMessage: package linux-image-4.4.0-83-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  HibernationDevice: RESUME=UUID=4789a4e3-ea9b-4a41-b54d-bb38c94dbe83
  InstallationDate: Installed on 2016-05-15 (639 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire 5735
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=2b4b8588-9bb8-4846-a576-3c3c4db4a618 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.16
  SourcePackage: linux
  Title: package linux-image-4.4.0-83-generic 4.4.0-83.106 failed to 
install/upgrade: package linux-image-4.4.0-83-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.07
  dmi.board.name: CathedralPeak
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.07:bd08/27/2008:svnAcer:pnAspire5735:pvr0100:rvnAcer:rnCathedralPeak:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5735
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1749428] Re: Unable to create KVM with uvtool on Moonshot arm64 system

[Joseph Salisbury]

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

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

** Tags added: kernel-da-key

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

Title:
  Unable to create KVM with uvtool on Moonshot arm64 system

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Not sure if this is related to bug 1452016, or just a HW issue:

  With the uvt-kvm create command on this Artful system, it returns:
  uvt-kvm: error: libvirt: unsupported configuration: ACPI requires UEFI on 
this architecture

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 14 11:01 seq
   crw-rw 1 root audio 116, 33 Feb 14 11:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Wed Feb 14 11:09:44 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

[dann frazier]

Marking failed due to LP: #1749040

** Tags removed: verification-needed-artful
** Tags added: verification-failed-artful

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

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

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

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

[Kernel-packages] [Bug 1743638] Re: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

[dann frazier]

artful/linux verification:

$ dpkg -c nic-modules-4.13.0-35-generic-di_4.13.0-35.39_arm64.udeb | grep qed
drwxr-xr-x root/root 0 2018-02-12 10:28 
./lib/modules/4.13.0-35-generic/kernel/drivers/net/ethernet/qlogic/qed/
-rw-r--r-- root/root828494 2018-02-12 10:28 
./lib/modules/4.13.0-35-generic/kernel/drivers/net/ethernet/qlogic/qed/qed.ko
drwxr-xr-x root/root 0 2018-02-12 10:28 
./lib/modules/4.13.0-35-generic/kernel/drivers/net/ethernet/qlogic/qede/
-rw-r--r-- root/root171750 2018-02-12 10:28 
./lib/modules/4.13.0-35-generic/kernel/drivers/net/ethernet/qlogic/qede/qede.ko

xenial/linux-hwe verification:
$ dpkg -c nic-modules-4.13.0-35-generic-di_4.13.0-35.39~16.04.1_arm64.udeb | 
grep qed
drwxr-xr-x root/root 0 2018-02-12 19:26 
./lib/modules/4.13.0-35-generic/kernel/drivers/net/ethernet/qlogic/qede/
-rw-r--r-- root/root172326 2018-02-12 17:25 
./lib/modules/4.13.0-35-generic/kernel/drivers/net/ethernet/qlogic/qede/qede.ko
drwxr-xr-x root/root 0 2018-02-12 19:26 
./lib/modules/4.13.0-35-generic/kernel/drivers/net/ethernet/qlogic/qed/
-rw-r--r-- root/root828526 2018-02-12 17:25 
./lib/modules/4.13.0-35-generic/kernel/drivers/net/ethernet/qlogic/qed/qed.ko


** Tags removed: verification-needed-artful verification-needed-xenial
** Tags added: verification-done-artful verification-done-xenial

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

Title:
  Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

Status in debian-installer package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-hwe source package in Xenial:
  Fix Committed
Status in linux-hwe-edge source package in Xenial:
  Fix Committed
Status in debian-installer source package in Artful:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Committed
Status in linux-hwe source package in Artful:
  Invalid
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-edge source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Network installs over a QLogic QED 25/40/100Gb Ethernet NIC will not work.

  [Test Case]
  Attempt to use the netinst installer to install a system over this NIC.

  [Regression Risk]
  The fix is just add to add additional kernel modules and firmware to the 
installer to support this NIC. The biggest risk I see there is that it 
increases the size of the installer, which could potentially grow to bit for 
some smaller systems.

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

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

[Kernel-packages] [Bug 1744078] Re: linux < 4.8: x-netns vti is broken

[Joseph Salisbury]

Just replied to the SRU request in comment #4, asking for a second ACK.

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

Title:
  linux < 4.8: x-netns vti is broken

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

Bug description:
  The following upstream patch is missing:

  11d7a0bb95ea xfrm: Only add l3mdev oif to dst lookups 
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=11d7a0bb95ea

  There are several ways to reproduce this problem. Here an example:

  # Prepare netns
  ip netns add test
  ip netns exec test sysctl -q -w net.ipv4.conf.all.forwarding=1
  ip netns exec test ip link set lo up
  ip netns exec test ip addr add 172.16.1.1/24 dev lo

  # Create VTI iface and move it in netns test
  ip addr add 1.1.1.1/32 dev lo
  ip link add name vti_test type vti local 1.1.1.1 remote 2.2.2.2 key 0x1
  ip link set dev vti_test netns test

  # Configure IPsec
  ip xfrm state add src 1.1.1.1 dst 2.2.2.2 proto esp spi 1 mode tunnel enc 
'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' 
'0x' 96 flag  align4 mark 0x1
  ip xfrm state add src 2.2.2.2 dst 1.1.1.1 proto esp spi 2 mode tunnel enc 
'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' 
'0x' 96 flag  align4 mark 0x1
  ip xfrm policy add dir out tmpl src 1.1.1.1 dst 2.2.2.2 proto esp mode tunnel 
mark 0x1
  ip xfrm policy add dir in tmpl src 2.2.2.2 dst 1.1.1.1 proto esp mode tunnel 
mark 0x1

  # Configure SVTI
  ip netns exec test ip link set dev vti_test up

  # Add route
  ip netns exec test ip route add 172.16.2.0/24 dev vti_test

  # Run a tcpdump on the output interface (given by "ip route get 2.2.2.2")
  tcpdump -nei eth0 &

  # Ping from the netns
  ip netns exec test ping 172.16.2.1 -I 172.16.1.1 -c 4

  --

  On 4.4.0-109-generic:
  (ping) From 172.16.1.1 icmp_seq=1 Destination Host Unreachable
  (tcpdump) no IPsec packet

  => Problem

  On 4.8.0-58-generic:
  (ping): no error raised
  (tcpdump) 15:09:45.109776 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype 
IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x2), 
length 132
  (tcpdump) 15:10:05.422243 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype 
IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x3), 
length 132

  => No problem

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

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

[Kernel-packages] [Bug 1747890] Re: Update the source code location in the debian package for cloud kernels

[Thadeu Lima de Souza Cascardo]

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

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

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

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

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

** Also affects: linux-azure-edge (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  Update the source code location in the debian package for cloud
  kernels

Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-azure-edge source package in Xenial:
  New
Status in linux-gcp source package in Xenial:
  New
Status in linux-gke source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux-azure-edge source package in Bionic:
  New
Status in linux-gcp source package in Bionic:
  New
Status in linux-gke source package in Bionic:
  New
Status in linux-kvm source package in Bionic:
  New

Bug description:
  Currently we have a single git repository for each cloud kernel, which
  is used for xenial. With bionic, we will need to split those repos by
  series.

  For instance, linux-azure repository will move from:

  git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/

  To:

  
git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/xenial
  
git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/bionic

  Gcs-Git tag in the debian/control file needs to be updated
  accordingly.

  The same is valid for meta packages.

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

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

[Kernel-packages] [Bug 1744300] Re: bt_iter() crash due to NULL pointer

[Guilherme G. Piccoli]

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

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

Title:
  bt_iter() crash due to NULL pointer

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Committed

Bug description:
  SRU Justification:

  
  [Impact]
  The following crash was observed in Ubuntu 16.04 running linux-gcp kernel 
version 4.13 (specifically 4.13.0-1006.9):

  [ 10.972644] BUG: unable to handle kernel NULL pointer dereference at 
0030 
  [ 10.980708] IP: bt_iter+0x31/0x50 
  [ 10.984310] PGD 0 
  [ 10.984310] P4D 0 
  [ 10.986439] 
  [ 10.990190] Oops:  [#1] SMP PTI 
  [ 11.016282] Workqueue: kblockd blk_mq_timeout_work 
  [ 11.021196] task: 8e7c2e70 task.stack: b8d4c67a8000 
  [ 11.027234] RIP: 0010:bt_iter+0x31/0x50 
  [ 11.031187] RSP: 0018:b8d4c67abda0 EFLAGS: 00010206 
  [ 11.037730] RAX: b8d4c67abdd0 RBX: 0180 RCX: 
 
  [ 11.045172] RDX: 8e7c34c8d280 RSI:  RDI: 
8e7c32dd8000 
  [ 11.053321] RBP: b8d4c67abe20 R08:  R09: 
2100 
  [ 11.060582] R10: 0130 R11: fffee5bf R12: 
8e7c3572c790 
  [ 11.068094] R13: 8e7c3572c780 R14: 0008 R15: 
8e7c35e7c180 
  [ 11.075522] FS: () GS:8e7c3a4c() 
knlGS: 
  [ 11.083721] CS: 0010 DS:  ES:  CR0: 80050033 
  [ 11.089593] CR2: 0030 CR3: 9e20a003 CR4: 
001606e0 
  [ 11.096871] Call Trace: 
  [ 11.099468] ? blk_mq_queue_tag_busy_iter+0xe2/0x1f0 
  [ 11.104558] ? blk_mq_rq_timed_out+0x70/0x70 
  [ 11.109130] ? blk_mq_rq_timed_out+0x70/0x70 
  [ 11.114933] blk_mq_timeout_work+0xbb/0x170 
  [ 11.119408] process_one_work+0x156/0x410 
  [ 11.123641] worker_thread+0x4b/0x460 
  [ 11.127827] kthread+0x109/0x140 
  [ 11.131186] ? process_one_work+0x410/0x410 
  [ 11.135499] ? kthread_create_on_node+0x70/0x70 
  [ 11.140408] ret_from_fork+0x1f/0x30 
  [ 11.144110] Code: 89 d0 48 8b 3a 0f b6 48 18 48 8b 97 30 01 00 00 84 c9 75 
03 03 72 04 48 8b 92 80 00 00 00 89 f6 48 8b 34 f2 48 8b 97 c0 00 00 00 <48> 39 
56 30 74 06 b8 01 00 00 00 c3 55 48 8b 50 10 48 89 e5 ff 
  [ 11.167573] RIP: bt_iter+0x31/0x50 RSP: b8d4c67abda0 
  [ 11.173028] CR2: 0030 
  [ 11.176515] ---[ end trace 2f8e5b1cf4139fec ]--- 
  [ 11.182589] Kernel panic - not syncing: Fatal exception 

  Basically, we have a NULL pointer dereference while in bt_iter()
  function - this is caused because after the merge of blk-mq scheduler
  capability on Linux kernel , tags->rqs[] array has been dinamically
  assigned and there's a small window of time in which the bit is set
  but tags->rqs[] array wasn't allocated yet. This was reported to
  happen in about 5% of test runs (more details on test section).

  
  [Fix]
  The fix is small and simple, and it's upstream already. Basically, it adds a 
NULL pointer check on bt_iter() and bt_tags_iter() functions.

  The fix is: 7f5562d5ecc4 ("blk-mq-tag: check for NULL rq when iterating 
tags"), by Jens Axboe.
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7f5562d5ecc4)

  
  [Testcase] 
  Since the problem manifests in a small non-deterministic time window, there's 
no easy test to reproduce this. In our case, it was observed while testing a 
large number of CPU's and attached disks (>200 disks, >150 cores), trying to 
exercise all CPUs and disks (the disks with quick dd commands). In this test 
scenario, as already mentioned, issue occured in about 5% of the runs.

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

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

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

[bugproxy]

--- Comment From frederic.bar...@fr.ibm.com 2018-02-14 13:03 EDT---
The code for this feature is available in kernel 4.16-rc1, and we'd like to 
backport the following 13 patches for 18.04. They should apply cleanly on a 
4.15 kernel:

7f2c39e91f61 powerpc/powernv: Introduce new PHB type for opencapi links
228c2f410378 powerpc/powernv: Set correct configuration space size for opencapi 
devices
74d656d219b9 powerpc/powernv: Add opal calls for opencapi
6914c757118e powerpc/powernv: Add platform-specific services for opencapi
2cb3d64b2698 powerpc/powernv: Capture actag information for the device
5ef3166e8a32 ocxl: Driver code for 'generic' opencapi devices
aeddad1760ae ocxl: Add AFU interrupt support
280b983ce2b8 ocxl: Add a kernel API for other opencapi drivers
92add22e8478 ocxl: Add trace points
b97f02246e0d ocxl: Add Makefile and Kconfig
741ddae6c4c1 cxl: Remove support for "Processing accelerators" class
00b96c0e3c54 ocxl: Documentation
6385d6f85fec ocxl: add MAINTAINERS entry

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

Title:
  [Ubuntu 18.04 FEAT] OpenCAPI enabling

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  [FEATURE] OpenCAPI enabling

  OpenCAPI is an Open Interface Architecture that allows any
  microprocessor to attach to

*  Coherent user-level accelerators and I/O devices
*  Advanced memories accessible via read/write or user-level DMA semantics
*  Agnostic to processor architecture

  
  This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be 
included in 4.16 and it will need to be backported to 4.15:

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

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

[Kernel-packages] [Bug 1749089] Re: linux: 4.4.0-116.140 -proposed tracker

[Brad Figg]

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

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

Title:
  linux: 4.4.0-116.140 -proposed tracker

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

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

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

  backports: bug 1749090 (linux-aws), bug 1749091 (linux-lts-xenial)
  derivatives: bug 1749092 (linux-kvm), bug 1749093 (linux-aws), bug 1749094 
(linux-raspi2), bug 1749095 (linux-euclid), bug 1749096 (linux-snapdragon), bug 
1749097 (linux-gke)
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1744117] Re: ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu 16.04 LTS Kernel

[Jamie Nguyen]

I've let our QA (India-based) know about this.  I'll update as soon as
they've had a chance to verify.

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

Title:
  ALSA backport missing NVIDIA GPU codec IDs to patch table to Ubuntu
  16.04 LTS Kernel

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

Bug description:
  Add support for 4/6/8 channel sound in 16.04 LTS kernel for future
  GPUs.

  This commit[1] first introduced in "Thu Jul 13 19:27:39 2017"[2] has
  what is needed base on discussion we had with nvidia:

  [1] - Commit
   
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=74ec118152ea494a25ebb677cbc83a75c982ac5f

  ALSA: hda - Add missing NVIDIA GPU codec IDs to patch table

  Add codec IDs for several recently released, pending, and historical
  NVIDIA GPU audio controllers to the patch table, to allow the correct
  patch functions to be selected for them.

  [2] - git describe --contains 74ec118152ea494a25ebb677cbc83a75c982ac5f
  v4.13-rc3~21^2~5

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

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

[Kernel-packages] [Bug 1749089] Re: linux: 4.4.0-116.140 -proposed tracker

[Chris Wayne]

+1 to promote, results here: https://trello.com/c/Y9LW1c2P/199-pc-
kernel-440-116140-104

** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux: 4.4.0-116.140 -proposed tracker

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

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

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

  backports: bug 1749090 (linux-aws), bug 1749091 (linux-lts-xenial)
  derivatives: bug 1749092 (linux-kvm), bug 1749093 (linux-aws), bug 1749094 
(linux-raspi2), bug 1749095 (linux-euclid), bug 1749096 (linux-snapdragon), bug 
1749097 (linux-gke)
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Rafael David Tinoco]

# xenial - 4.4.0-112

[  OK  ] Reached target Shutdown.
[   70.272171]  connection3:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294907361, last ping 4294908612, now 4294909864
[   70.274189]  connection4:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294907361, last ping 4294908612, now 4294909864
[   70.288082]  connection5:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294907362, last ping 4294908614, now 4294909868
[   70.290066]  connection2:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294907363, last ping 4294908614, now 4294909868
[   70.292039]  connection1:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294907362, last ping 4294908614, now 4294909868



# xenial - 4.4.0-116

[  OK  ] Reached target Shutdown.
[   38.384175]  connection3:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294899386, last ping 4294900640, now 4294901892
[   38.386107]  connection1:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294899387, last ping 4294900640, now 4294901892
[   38.388023]  connection5:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294899387, last ping 4294900640, now 4294901892
[   38.388159]  connection4:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294899386, last ping 4294900640, now 4294901892
[   38.388159]  connection2:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294899387, last ping 4294900640, now 4294901892
[   89.825203] reboot: Restarting system

-> xenial-verification-done



# artful - 4.13.0-32

[  OK  ] Reached target Shutdown.
[  194.277712]  connection4:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294938304, last ping 4294939584, now 4294940864
[  194.279684]  connection2:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294938304, last ping 4294939584, now 4294940864
[  194.281483]  connection1:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294938304, last ping 4294939584, now 4294940864
[  194.283265]  connection5:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294938304, last ping 4294939584, now 4294940864
[  194.285067]  connection3:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294938304, last ping 4294939584, now 4294940864



# artful - 4.13.0-35

[  OK  ] Reached target Shutdown.
[  416.109989]  connection2:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294993856, last ping 4294995136, now 4294996416
[  416.111922]  connection1:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294993856, last ping 4294995136, now 4294996416
[  416.113869]  connection4:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294993856, last ping 4294995136, now 4294996416
[  416.115741]  connection3:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294993856, last ping 4294995136, now 4294996416
[  416.117650]  connection5:0: ping timeout of 5 secs expired, recv timeout 5, 
last rx 4294993856, last ping 4294995136, now 4294996416
[  469.614166] reboot: Restarting system

-> artful-verification-done

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

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  Fix Committed
Status in open-iscsi package in Ubuntu:
  Opinion
Status in linux source package in Trusty:
  Fix Committed
Status in open-iscsi source package in Trusty:
  Opinion
Status in linux source package in Xenial:
  Fix Committed
Status in open-iscsi source package in Xenial:
  Opinion
Status in linux source package in Artful:
  Fix Committed
Status in open-iscsi source package in Artful:
  Opinion
Status in linux source package in Bionic:
  Fix Committed
Status in open-iscsi source package in Bionic:
  Opinion

Bug description:
  [Impact]

   * open-iscsi users might face hangs during OS shutdown.
   * hangs can be caused by manual iscsi configuration/setup.
   * hangs can also be caused by bad systemd unit ordering.
   * if transport layer interface vanishes before lun is
 disconnected, then the hang will happen.
   * check comment #89 for the fix decision.
   
  [Test Case]

   * a simple way of reproducing the kernel hang is to disable
 the open-iscsi logouts. this simulates a situation when
 a service has shutdown the network interface, used by
 the transport layer, before proper iscsi logout was done.

 $ log into all iscsi luns

 $ systemctl edit --full open-iscsi.service
 ...
 #ExecStop=/lib/open-iscsi/logout-all.sh
 ...

 $ sudo reboot # this will make server to hang forever
   # on shutdown

  [Regression Potential]

   * the regression is low because the change acts on the iscsi
 transport layer code ONLY when the server is in 

[Kernel-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Rafael David Tinoco]

Checking if Trusty's fix is in -proposed (no comment given from Kernel
Team about it)

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in linux package in Ubuntu:
  Fix Committed
Status in open-iscsi package in Ubuntu:
  Opinion
Status in linux source package in Trusty:
  Fix Committed
Status in open-iscsi source package in Trusty:
  Opinion
Status in linux source package in Xenial:
  Fix Committed
Status in open-iscsi source package in Xenial:
  Opinion
Status in linux source package in Artful:
  Fix Committed
Status in open-iscsi source package in Artful:
  Opinion
Status in linux source package in Bionic:
  Fix Committed
Status in open-iscsi source package in Bionic:
  Opinion

Bug description:
  [Impact]

   * open-iscsi users might face hangs during OS shutdown.
   * hangs can be caused by manual iscsi configuration/setup.
   * hangs can also be caused by bad systemd unit ordering.
   * if transport layer interface vanishes before lun is
 disconnected, then the hang will happen.
   * check comment #89 for the fix decision.
   
  [Test Case]

   * a simple way of reproducing the kernel hang is to disable
 the open-iscsi logouts. this simulates a situation when
 a service has shutdown the network interface, used by
 the transport layer, before proper iscsi logout was done.

 $ log into all iscsi luns

 $ systemctl edit --full open-iscsi.service
 ...
 #ExecStop=/lib/open-iscsi/logout-all.sh
 ...

 $ sudo reboot # this will make server to hang forever
   # on shutdown

  [Regression Potential]

   * the regression is low because the change acts on the iscsi
 transport layer code ONLY when the server is in shutdown 
 state.

   * any error in logic would only appear during shutdown and
 would not cause any harm to data.

  [Other Info]
   
   * ORIGINAL BUG DESCRIPTION

  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Kernel-packages] [Bug 1748470] Re: Spectre V2 : System may be vulnerable to spectre v2

[Joseph Salisbury]

Sorry I missed your message on IRC.  Thanks for the report, Cristian.
I have tagged the bug with 'pti'.  This will ensure it is reviewed with
all of the other spectre mitigation bugs.

We are still working to address all of the spectre vulnerabilities.

One way to tell the current level of your system is with this command:
tail /sys/devices/system/cpu/vulnerabilities/*


** Tags added: kernel-da-key

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 

[Kernel-packages] [Bug 1748513] Re: BUG: unable to handle kernel paging request at 00007f29ec101010

[Simon Déziel]

I found a way to trigger the issue with 4.4.0-113.136 and am glad to
report that the -proposed kernel 4.4.0-116.140 fixes the issue, thanks!

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

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

Title:
  BUG: unable to handle kernel paging request at 7f29ec101010

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Got this bug/oops while running with the linux-image-4.4.0-113-generic
  (4.4.0-113.136) kernel from -proposed:

  BUG: unable to handle kernel paging request at 7f29ec101010
  IP: [] csum_and_copy_from_iter+0x55/0x4c0
  PGD 82fcef6f9067 PUD 2fd1615e067 PMD 2fcef77e067 PTE 82fd0009f867
  Oops: 0001 [#1] SMP 
  Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_
   fjes wmi
  CPU: 39 PID: 27347 Comm: fping Not tainted 4.4.0-113-generic #136-Ubuntu
  Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
  task: 88bd1125e200 ti: 897d0285 task.ti: 897d0285
  RIP: 0010:[]  [] 
csum_and_copy_from_iter+0x55/0x4c0
  RSP: 0018:897d02853a18  EFLAGS: 00010246
  RAX: 0018 RBX: 0006 RCX: 897d02853e98
  RDX: 897d02853a94 RSI: 0040 RDI: 8afcfba4ea24
  RBP: 897d02853a80 R08:  R09: 8afcfba4ea24
  R10: 8afcfba4ea24 R11: 8afcfba4ea00 R12: 897d02853e98
  R13:  R14: 1ee730fc3e9fb34c R15: 7f29ec101008
  FS:  7f29ec282700() GS:8afd7ec4() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f29ec101010 CR3: 02fce5462000 CR4: 00360670
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   88bd7ec07340 9772d1d7 8afcf02d8f00 897d02853aaf
   897d02853a94 01c0  1ee730fc3e9fb34c
   0040 8afcf02d8f00  897d02853d30
  Call Trace:
   [] ? __alloc_skb+0x87/0x1f0
   [] ip_generic_getfrag+0x56/0xe0
   [] raw_getfrag+0xaf/0x100
   [] __ip_append_data.isra.45+0x98a/0xb90
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ip_append_data.part.46+0x7a/0xe0
   [] ip_append_data+0x34/0x40
   [] raw_sendmsg+0x724/0xc00
   [] ? aa_sk_perm+0x70/0x210
   [] ? aa_sock_msg_perm+0x61/0x150
   [] inet_sendmsg+0x6b/0xa0
   [] sock_sendmsg+0x3e/0x50
   [] SYSC_sendto+0x101/0x190
   [] ? vm_mmap_pgoff+0xbb/0xe0
   [] ? __do_page_fault+0x1b4/0x400
   [] SyS_sendto+0xe/0x10
   [] entry_SYSCALL_64_fastpath+0x1c/0x93
  Code: f3 48 0f 47 de 48 85 db 0f 84 8b 01 00 00 8b 02 49 89 f9 49 89 cc 4c 8b 
71 08 89 45 c4 8b 01 a8 04 0f 85 79 01 00 00 4c 8b 79 18 <4d> 8b 6f 08 4d 29 f5 
49 39 dd 4c 0f 47 eb a8 02 0f 85 36 02 00 
  RIP  [] csum_and_copy_from_iter+0x55/0x4c0
   RSP 
  CR2: 7f29ec101010
  ---[ end trace 48102008d03cb384 ]---

  This is something new with the -proposed kernel.

  Additional information:

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

  $ apt-cache policy linux-image-4.4.0-113-generic
  linux-image-4.4.0-113-generic:
Installed: 4.4.0-113.136
Candidate: 4.4.0-113.136
Version table:
   *** 4.4.0-113.136 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-113-generic 4.4.0-113.136
  ProcVersionSignature: Ubuntu 4.4.0-113.136-generic 4.4.98
  Uname: Linux 4.4.0-113-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb  9 10:45 seq
   crw-rw 1 root audio 116, 33 Feb  9 10:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Fri Feb  9 13:41:20 2018
  HibernationDevice: RESUME=/dev/mapper/vghost-swap
  InstallationDate: Installed on 2017-04-01 (314 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R830
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: 

Re: [Kernel-packages] [Bug 1736593] Re: ThunderX: TX failure unless checksum offload disabled

[dann frazier]

On Wed, Feb 14, 2018 at 8:53 AM, Edward Vielmetti
 wrote:
> Thank you. We will be testing this new kernel at Packet and will report
> results.

Thanks Edward. Please beware of LP: #1749040 as you test. We're not
seeing it with the latest build, but it is not yet root-caused.

  -dann

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

Title:
  ThunderX: TX failure unless checksum offload disabled

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

Bug description:
  [Impact]
  Most attempts to use IPv6 on the ThunderX NIC will fail.

  [Test Case]
  Attempt an IPv6 TCP connection:

  $ wget -6 'http://www.kernel.org/'

  The connection will time out.

  [Regression Risk]
  The fix is upstream, and is limited to the ThunderX nicvf driver.

  [Workaround]
  Disable TX checksum offload:

  $ ethtool -K eth0 tx off

  [More Details]
  The issue first appears in Linux 4.12.  A fix from Cavium has been merged 
upstream:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/cavium/thunder/nicvf_queues.c?id=fa6d7cb5d76cf0467c61420fc9238045aedfd379

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

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

[Kernel-packages] [Bug 1744078] Re: linux < 4.8: x-netns vti is broken

[Julien Meunier]

Hi,

What is the status of this bug ? Regarding the patches, are they
integrated  ?

Thanks in advance.

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

Title:
  linux < 4.8: x-netns vti is broken

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

Bug description:
  The following upstream patch is missing:

  11d7a0bb95ea xfrm: Only add l3mdev oif to dst lookups 
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=11d7a0bb95ea

  There are several ways to reproduce this problem. Here an example:

  # Prepare netns
  ip netns add test
  ip netns exec test sysctl -q -w net.ipv4.conf.all.forwarding=1
  ip netns exec test ip link set lo up
  ip netns exec test ip addr add 172.16.1.1/24 dev lo

  # Create VTI iface and move it in netns test
  ip addr add 1.1.1.1/32 dev lo
  ip link add name vti_test type vti local 1.1.1.1 remote 2.2.2.2 key 0x1
  ip link set dev vti_test netns test

  # Configure IPsec
  ip xfrm state add src 1.1.1.1 dst 2.2.2.2 proto esp spi 1 mode tunnel enc 
'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' 
'0x' 96 flag  align4 mark 0x1
  ip xfrm state add src 2.2.2.2 dst 1.1.1.1 proto esp spi 2 mode tunnel enc 
'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' 
'0x' 96 flag  align4 mark 0x1
  ip xfrm policy add dir out tmpl src 1.1.1.1 dst 2.2.2.2 proto esp mode tunnel 
mark 0x1
  ip xfrm policy add dir in tmpl src 2.2.2.2 dst 1.1.1.1 proto esp mode tunnel 
mark 0x1

  # Configure SVTI
  ip netns exec test ip link set dev vti_test up

  # Add route
  ip netns exec test ip route add 172.16.2.0/24 dev vti_test

  # Run a tcpdump on the output interface (given by "ip route get 2.2.2.2")
  tcpdump -nei eth0 &

  # Ping from the netns
  ip netns exec test ping 172.16.2.1 -I 172.16.1.1 -c 4

  --

  On 4.4.0-109-generic:
  (ping) From 172.16.1.1 icmp_seq=1 Destination Host Unreachable
  (tcpdump) no IPsec packet

  => Problem

  On 4.8.0-58-generic:
  (ping): no error raised
  (tcpdump) 15:09:45.109776 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype 
IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x2), 
length 132
  (tcpdump) 15:10:05.422243 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype 
IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x3), 
length 132

  => No problem

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

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

[Kernel-packages] [Bug 1748489] Re: linux-aws: 4.4.0-1052.61 -proposed tracker

[Andy Whitcroft]

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

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

Title:
  linux-aws: 4.4.0-1052.61 -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-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 snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1748990
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1748990] Re: linux: 4.4.0-116.140 -proposed tracker

[Andy Whitcroft]

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

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

Title:
  linux: 4.4.0-116.140 -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-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed 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 snap-certification-testing series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

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

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

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

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

[Kernel-packages] [Bug 1748486] Re: linux-aws: 4.4.0-1014.14 -proposed tracker

[Andy Whitcroft]

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

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

Title:
  linux-aws: 4.4.0-1014.14 -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-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 series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  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
  -- swm properties --
  kernel-stable-master-bug: 1748990
  phase: Packaging

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

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

[Kernel-packages] [Bug 1748470] JournalErrors.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1748470/+attachment/5055194/+files/JournalErrors.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/1748470

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio

[Kernel-packages] [Bug 1748470] CurrentDmesg.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1748470/+attachment/5055192/+files/CurrentDmesg.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/1748470

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
  

[Kernel-packages] [Bug 1748470] Re: Spectre V2 : System may be vulnerable to spectre v2

[Cristian Aravena Romero]

apport information

** Tags added: apport-collected

** Description changed:

  Hello,
  
  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0
  
  Regards,
  --
  Cristian
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ --- 
+ ApportVersion: 2.20.8-0ubuntu10
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
+  /dev/snd/controlC0:  caravena   1797 F pulseaudio
+ CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-10-13 (123 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
+ MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
+ Package: linux (not 

[Kernel-packages] [Bug 1748470] ProcCpuinfoMinimal.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1748470/+attachment/5055198/+files/ProcCpuinfoMinimal.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/1748470

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m 

[Kernel-packages] [Bug 1748470] IwConfig.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1748470/+attachment/5055193/+files/IwConfig.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/1748470

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
   

[Kernel-packages] [Bug 1748470] ProcCpuinfo.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1748470/+attachment/5055197/+files/ProcCpuinfo.txt

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
   

[Kernel-packages] [Bug 1748470] RfKill.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1748470/+attachment/5055213/+files/RfKill.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/1748470

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
   

[Kernel-packages] [Bug 1748470] CRDA.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1748470/+attachment/5055191/+files/CRDA.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/1748470

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
   

[Kernel-packages] [Bug 1748470] Lsusb.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1748470/+attachment/5055196/+files/Lsusb.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/1748470

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
   

[Kernel-packages] [Bug 1748470] ProcEnviron.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1748470/+attachment/5055199/+files/ProcEnviron.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/1748470

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
   

[Kernel-packages] [Bug 1748470] Re: Spectre V2 : System may be vulnerable to spectre v2

[Cristian Aravena Romero]

Hello,

* Ubuntu 4.15.0-10.11-generic 4.15.3
* The VirtualBox message is no longer

dmesg:
[   19.054411] vboxdrv: loading out-of-tree module taints kernel.
[   19.054732] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
[   19.070696] vboxdrv: Found 4 processor cores
[   19.096198] vboxdrv: TSC mode is Invariant, tentative frequency 1496599865 Hz
[   19.096200] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
[   19.458556] VBoxNetFlt: Successfully started.
[   19.861542] VBoxNetAdp: Successfully started.
[   19.880738] VBoxPciLinuxInit
[   19.909522] vboxpci: IOMMU not found (not registered)

Regards,
--
Cristian

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  

[Kernel-packages] [Bug 1748470] UdevDb.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1748470/+attachment/5055214/+files/UdevDb.txt

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
   

[Kernel-packages] [Bug 1748470] ProcModules.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1748470/+attachment/5055201/+files/ProcModules.txt

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
   

[Kernel-packages] [Bug 1748470] ProcInterrupts.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1748470/+attachment/5055200/+files/ProcInterrupts.txt

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m 

[Kernel-packages] [Bug 1748470] PulseList.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1748470/+attachment/5055212/+files/PulseList.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/1748470

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
   

[Kernel-packages] [Bug 1748470] WifiSyslog.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1748470/+attachment/5055215/+files/WifiSyslog.txt

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
   

[Kernel-packages] [Bug 1748470] Lspci.txt

[Cristian Aravena Romero]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1748470/+attachment/5055195/+files/Lspci.txt

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1797 F...m pulseaudio
   

[Kernel-packages] [Bug 1736593] Re: ThunderX: TX failure unless checksum offload disabled

[Edward Vielmetti]

Thank you. We will be testing this new kernel at Packet and will report
results.

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

Title:
  ThunderX: TX failure unless checksum offload disabled

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

Bug description:
  [Impact]
  Most attempts to use IPv6 on the ThunderX NIC will fail.

  [Test Case]
  Attempt an IPv6 TCP connection:

  $ wget -6 'http://www.kernel.org/'

  The connection will time out.

  [Regression Risk]
  The fix is upstream, and is limited to the ThunderX nicvf driver.

  [Workaround]
  Disable TX checksum offload:

  $ ethtool -K eth0 tx off

  [More Details]
  The issue first appears in Linux 4.12.  A fix from Cavium has been merged 
upstream:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/cavium/thunder/nicvf_queues.c?id=fa6d7cb5d76cf0467c61420fc9238045aedfd379

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

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

[Kernel-packages] [Bug 1747069] Re: artful 4.13 i386 kernels crash after memory hotplug remove

[Colin Ian King]

Ran the tests against the i386 -proposed kernel, cannot reproduce the
issue with the fixed kernel.  Also ran the ADT tests and could not
reproduce the issue (and these run the memory hotplug tests too).

Tested, and verified.

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

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

Title:
  artful 4.13 i386 kernels crash after memory hotplug remove

Status in linux package in Ubuntu:
  In Progress

Bug description:
  == SRU Request, Artful ==

  Hotplug removal causes i386 crashes when exercised with the kernel
  selftest mem-on-off-test script.  

  == Fix ==

  Revert commit f1dd2cd13c4b (""mm, memory_hotplug: do not associate
  hotadded memory to zones until online")

  Note: A fix occurs in 4.15 however this requires a large set of
  changes that are way too large to be SRU'able and the least risky way
  forward is to revert the offending commit.

  == Testcase ==

  Running the kernel selftest script mem-on-off-test.sh, followed by a
  sync, followed by re-installing kernel packages will always trigger
  this issue. Simply running the mem-on-off-test.sh script sometimes
  won't trigger the problem.  I believe this is why we've not seen this
  happen too frequently with our ADT tests.  I can reproduce this in a
  VM with 4 CPUs and 2GB of memory.

  == Regression Potential ==

  Reverting this commit does remove some functionality, however this
  does not regress the kernel compared to previous releases and having a
  working reliable memory hotplug is the preferred option.  This fix
  does touch some memory hotplug, so there is a risk that this may break
  this functionality that is not covered by the kernel regression
  testing.

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

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

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

[ChristianEhrhardt]

On Xenial + HWE as-is:

ubuntu@wichita:~/kvm-unit-tests$ sudo ./run_tests.sh -v; cat 
logs/spapr_hcall.log
TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./powerpc/run powerpc/selftest.elf 
-smp 2 -m 256 -append 'setup smp=2 mem=256'
PASS selftest-setup 
TESTNAME=spapr_hcall TIMEOUT=90s ACCEL= ./powerpc/run powerpc/spapr_hcall.elf 
-smp 1
FAIL spapr_hcall 
TESTNAME=rtas-get-time-of-day TIMEOUT=5 ACCEL= ./powerpc/run powerpc/rtas.elf 
-smp 1 -append "get-time-of-day date=$(date +%s)"
PASS rtas-get-time-of-day 
TESTNAME=rtas-get-time-of-day-base TIMEOUT=5 ACCEL= ./powerpc/run 
powerpc/rtas.elf -smp 1 -rtc base="2006-06-17" -append "get-time-of-day 
date=$(date --date="2006-06-17 UTC" +%s)"
PASS rtas-get-time-of-day-base 
TESTNAME=rtas-set-time-of-day TIMEOUT=5 ACCEL= ./powerpc/run powerpc/rtas.elf 
-smp 1 -append "set-time-of-day"
PASS rtas-set-time-of-day 
TESTNAME=emulator TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1
FAIL emulator 
SKIP h_cede_tm (test marked as manual run only)
MIGRATION=yes TESTNAME=sprs TIMEOUT=90s ACCEL= ./powerpc/run powerpc/sprs.elf 
-smp 1 -append '-w'
FAIL sprs 
timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults -machine 
pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial stdio 
-kernel powerpc/spapr_hcall.elf -smp 1 # -initrd /tmp/tmp.mp3tm4K2lz
FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef
FAIL: hypercall: h_set_sprg0: sprg0 = 0x
FAIL: hypercall: h_set_sprg0: sprg0 = 0x419744
FAIL: hypercall: h_page_init: h_zero_page
FAIL: hypercall: h_page_init: h_copy_page
FAIL: hypercall: h_page_init: h_copy_page+h_zero_page
FAIL: hypercall: h_page_init: h_zero_page unaligned dst
FAIL: hypercall: h_page_init: h_copy_page unaligned src
XFAIL: hypercall: h_random: h-call available
SUMMARY: 9 tests, 8 unexpected failures, 1 expected failures

EXIT: STATUS=3
R


Upgrade to the version in proposed:
$ sudo apt install qemu-kvm qemu-block-extra qemu-system-ppc
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  qemu-system-common qemu-utils
Suggested packages:
  samba vde2 openbios-ppc openhackware debootstrap
The following packages will be upgraded:
  qemu-block-extra qemu-kvm qemu-system-common qemu-system-ppc qemu-utils
5 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
Need to get 3.276 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el 
qemu-system-common ppc64el 1:2.5+dfsg-5ubuntu10.21 [279 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el 
qemu-utils ppc64el 1:2.5+dfsg-5ubuntu10.21 [474 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el 
qemu-block-extra ppc64el 1:2.5+dfsg-5ubuntu10.21 [31,7 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el 
qemu-kvm ppc64el 1:2.5+dfsg-5ubuntu10.21 [6.662 B]
Get:5 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main ppc64el 
qemu-system-ppc ppc64el 1:2.5+dfsg-5ubuntu10.21 [2.485 kB]
Fetched 3.276 kB in 0s (3.806 kB/s)
(Reading database ... 67442 files and directories currently installed.)
Preparing to unpack 
.../qemu-system-common_1%3a2.5+dfsg-5ubuntu10.21_ppc64el.deb ...
Unpacking qemu-system-common (1:2.5+dfsg-5ubuntu10.21) over 
(1:2.5+dfsg-5ubuntu10.20) ...
Preparing to unpack .../qemu-utils_1%3a2.5+dfsg-5ubuntu10.21_ppc64el.deb ...
Unpacking qemu-utils (1:2.5+dfsg-5ubuntu10.21) over (1:2.5+dfsg-5ubuntu10.20) 
...
Preparing to unpack .../qemu-block-extra_1%3a2.5+dfsg-5ubuntu10.21_ppc64el.deb 
...
Unpacking qemu-block-extra:ppc64el (1:2.5+dfsg-5ubuntu10.21) over 
(1:2.5+dfsg-5ubuntu10.20) ...
Preparing to unpack .../qemu-kvm_1%3a2.5+dfsg-5ubuntu10.21_ppc64el.deb ...
Unpacking qemu-kvm (1:2.5+dfsg-5ubuntu10.21) over (1:2.5+dfsg-5ubuntu10.20) ...
Preparing to unpack .../qemu-system-ppc_1%3a2.5+dfsg-5ubuntu10.21_ppc64el.deb 
...
Unpacking qemu-system-ppc (1:2.5+dfsg-5ubuntu10.21) over 
(1:2.5+dfsg-5ubuntu10.20) ...
Processing triggers for systemd (229-4ubuntu21.1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up qemu-block-extra:ppc64el (1:2.5+dfsg-5ubuntu10.21) ...
Setting up qemu-system-common (1:2.5+dfsg-5ubuntu10.21) ...
Setting up qemu-utils (1:2.5+dfsg-5ubuntu10.21) ...
Setting up qemu-system-ppc (1:2.5+dfsg-5ubuntu10.21) ...
Setting up qemu-kvm (1:2.5+dfsg-5ubuntu10.21) ...


With proposed enabled:
$ sudo ./run_tests.sh -v; cat logs/spapr_hcall.log
TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./powerpc/run powerpc/selftest.elf 
-smp 2 -m 256 -append 'setup smp=2 mem=256'
PASS selftest-setup 
TESTNAME=spapr_hcall TIMEOUT=90s ACCEL= ./powerpc/run powerpc/spapr_hcall.elf 
-smp 1
PASS spapr_hcall 
TESTNAME=rtas-get-time-of-day TIMEOUT=5 ACCEL= ./powerpc/run powerpc/rtas.elf 
-smp 1 -append 

[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

[daniel CURTIS]

Here is a new, separate bug report about 'kASLR' and system booting
issues (v4.4.0-113.136 - v4.4.0-115-generic kernel versions):

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

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

Title:
  Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
  built-in shell (initramfs).

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

Bug description:
  Hello.

  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on an USB keyboard were in-
  active. After several seconds, the BusyBox shell screen appeared. It
  looks this way:

  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--

  Unfortunately, the USB keyboard does not work and does not respond.
  The only way to solve this issue is a "hard reset" and in GRUB menu
  choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
  everything works okay.

  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not
  contain PTI yet, right? I'm asking, because mentioned -proposed
  updates contains a couple of PTI-related patches and bugs in PTI can
  cause a few different signatures of crashes etc. For example:

  → Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
  → Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 

  NOTE: if it's about PCID, which is mentioned in a second point, there
  is one patch in -proposed update: "x86/mm/32: Move
  setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
  cause of a boot failure? There are no errors in log files, such as
  '/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
  series. So, I don't know if mentioned patches are good for this type
  of processor etc.? Especially on i386/x86_32 architecture.

  ● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for
  this issue. After booting the latest v4.4.0-115.139 kernel, I've had
  the same problems as described above. However, after removing 'kaslr'
  option from a command line via GRUB menu, system started normally etc.
  The latest, working kernel with 'kaslr' option is v4.4.0-112.135.
  According to all of this I think, that 'kaslr' is not compatible with
  some "Spectre & Meltdown" mitigation patches and fixes etc.

  ✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
  ✗ Architecture: i386/x86_32
  ✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 

  Thanks, regards.
  

  1. https://lists.ubuntu.com/archives/xenial-
  changes/2018-February/020108.html

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

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

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

[Simon Déziel]

The -proposed kernel 4.4.0-116.140 fixes the issue, thanks!

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

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

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

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

Bug description:
  Got this bug/oops while running with the linux-image-4.4.0-113-generic
  (4.4.0-113.136) kernel from -proposed:

  BUG: unable to handle kernel NULL pointer dereference at 0009
  IP: [] csum_and_copy_from_iter+0x55/0x4c0
  PGD 0 
  Oops:  [#1] SMP 
  Modules linked in: ctr ccm veth xt_CHECKSUM iptable_mangle xt_comment ec_sys 
bridge stp llc nf_log_ipv6 ip6table_filter ip6t_MASQUERADE 
nf_nat_masquerade_ipv6 ip6table_nat nf_nat_ipv6 ip6_tables nf_log_ip
   snd ghash_clmulni_intel soundcore r8169 psmouse input_leds cfg80211 rtsx_pci 
mii vhost_net vhost media ahci libahci macvtap macvlan mei_me mei kvm_intel kvm 
irqbypass tpm_crb i2c_hid intel_lpss_acpi inte
  CPU: 2 PID: 3997 Comm: dnsmasq Tainted: PW  O4.4.0-113-generic 
#136-Ubuntu
  Hardware name: System76Lemur/Lemur, BIOS 5.12 
02/17/2017
  task: 880830269e00 ti: 880035c44000 task.ti: 880035c44000
  RIP: 0010:[]  [] 
csum_and_copy_from_iter+0x55/0x4c0
  RSP: 0018:880035c47a18  EFLAGS: 00010246
  RAX: ab729fd0 RBX: 001c RCX: 880035c47e98
  RDX: 880035c47a94 RSI: 001c RDI: 8807ef1a7424
  RBP: 880035c47a80 R08:  R09: 8807ef1a7424
  R10: 8807ef1a7424 R11: 8807ef1a7400 R12: 880035c47e98
  R13:  R14: 00ffabea6920 R15: 0001
  FS:  7ff2b234d880() GS:88086ed0() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0009 CR3: 35c1e000 CR4: 00360670
  Stack:
   88084e001600 ab72d1d7 880830f18500 880035c47aaf
   880035c47a94 01c0  b0f4001fc4815eea
   001c 880830f18500  880035c47d30
  Call Trace:
   [] ? __alloc_skb+0x87/0x1f0
   [] ip_generic_getfrag+0x56/0xe0
   [] raw_getfrag+0xaf/0x100
   [] __ip_append_data.isra.45+0x98a/0xb90
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ip_append_data.part.46+0x7a/0xe0
   [] ip_append_data+0x34/0x40
   [] raw_sendmsg+0x724/0xc00
   [] ? aa_sk_perm+0x70/0x210
   [] ? aa_sock_msg_perm+0x61/0x150
   [] inet_sendmsg+0x6b/0xa0
   [] sock_sendmsg+0x3e/0x50
   [] SYSC_sendto+0x101/0x190
   [] ? sock_setsockopt+0x180/0x830
   [] ? apparmor_socket_setsockopt+0x22/0x30
   [] SyS_sendto+0xe/0x10
   [] entry_SYSCALL_64_fastpath+0x1c/0x93
  Code: f3 48 0f 47 de 48 85 db 0f 84 8b 01 00 00 8b 02 49 89 f9 49 89 cc 4c 8b 
71 08 89 45 c4 8b 01 a8 04 0f 85 79 01 00 00 4c 8b 79 18 <4d> 8b 6f 08 4d 29 f5 
49 39 dd 4c 0f 47 eb a8 02 0f 85 36 02 00 
  RIP  [] csum_and_copy_from_iter+0x55/0x4c0
   RSP 
  CR2: 0009
  ---[ end trace bdd9157c94a456b6 ]---

  The trigger is when I start an artful lxd container and it tries to
  get an IPv4/IPv6. Oddly enough, the same thing works perfectly for my
  xenial container. My lxd-bridge has dnsmasq contained by Apparmor
  which is non standard but always worked flawlessly.

  I can trigger the bug 100% of the time so validating any tentative fix
  should be easy.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-113-generic 4.4.0-113.136
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  7244 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sat Feb 10 16:45:26 2018
  HibernationDevice: RESUME=/dev/mapper/nvme0n1p3_crypt
  InstallationDate: Installed on 2016-12-06 (431 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
  MachineType: System76 Lemur
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=49432620-38ed-44bd-912a-7bc51eec3a35 ro quiet splash possible_cpus=4 
nmi_watchdog=0 kaslr vsyscall=none vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.16
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh