date:20180201

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1746874/+attachment/5047325/+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/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1746874] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1746874/+attachment/5047324/+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/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1746874] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1746874/+attachment/5047323/+files/Dependencies.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/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1746874] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1746874/+attachment/5047326/+files/ProcEnviron.txt

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

apport information

** Tags added: apport-collected

** Description changed:

  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).
  
  This is despite:
  
  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0
  
  So really there are two problems:
  
  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:
  
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.8-0ubuntu7
+ Architecture: amd64
+ CrashReports:
+  640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
+  640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
+  640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
+  640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
+  640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-12-12 (52 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
+ Package: mutter
+ PackageArchitecture: all
+ ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
+ Tags:  bionic
+ Uname: Linux 4.13.0-25-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "ApportLog.txt"
   
https://bugs.launchpad.net/bugs/1746874/+attachment/5047322/+files/ApportLog.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/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" -

[Kernel-packages] [Bug 1745747] Re: No USB support for Dell XPS 13 9370 running Bionic 18.04

@Mario,

The device I mentioned is a USB Type-C to HDMI UHD dongle, it uses a NXP
PTN5002 inside:

T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 2.01 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=1fc9 ProdID=5002 Rev=01.00
S:  Manufacturer=NXP
S:  Product=PTN5002
S:  SerialNumber=039e5595
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

I just tried to use this dongle under Windows 10, same result. So
probably a hardware/firmware issue.

The NXP PTN5002 works on Precision 3520's TBT port.

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

Title:
  No USB support for Dell XPS 13 9370 running Bionic 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently received an XPS 13 9370. After taking a backup for 16.04
  (in case this very thing happened), I installed the daily build of
  18.04 as it didn't really make sense for me to hold on to a distro
  that'll be replaced in a couple of months.

  I noticed there were a few Dell repositories in sources.list, but non
  of them have bionic endpoints (only xenial).

  I copied those, in case they would be useful and went to erasing the
  disk and installing 18.04. Everything seems to work fine, except the
  USB / Thunderbolt ports. Nothing I try works, whether it be USB or
  Thunderbolt 3.

  If I look in dmesg, I can see the controller is recognising something,
  but it never lands in userspace:

  [ 1807.837379] xhci_hcd :39:00.0: Host supports USB 3.1 Enhanced 
SuperSpeed
  [ 1807.837410] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
  [ 1807.837412] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [ 1807.837413] usb usb4: Product: xHCI Host Controller
  [ 1807.837414] usb usb4: Manufacturer: Linux 4.13.0-25-generic xhci-hcd
  [ 1807.837416] usb usb4: SerialNumber: :39:00.0
  [ 1807.837549] hub 4-0:1.0: USB hub found
  [ 1807.837558] hub 4-0:1.0: 2 ports detected
  --- 
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-19 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180118)
  Package: linux (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-041500-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

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

apport-collect 1746874

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

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

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

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

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-02-01 Thread ChristianEhrhardt

Also passed all regression tests on ppc without a hickup.
Other than waiting for the security update to pass we are ready.

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

Title:
  spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe
  kernel

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in qemu source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * Xenial with HWE kernel (matching new relesaes) and qemu without cloud
 archive (not matching new releases) could trigger hypercalls that are 
 not supported in xenials-qemu.

   * There is no "real" case other than kvm tests yet to trigger it yet, but 
 it is an easy and well contained fix, so we might fix proactively.

  [Test Case]

1. deploy xenial + HWE kernel on a ppc64el box
2. sudo apt-get install qemu-kvm -y
3. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
4. cd kvm-unit-tests
5. ./configure --endian=little; make
6. sudo ppc64_cpu --smt=off
7. sudo ./run_tests -v

  [Regression Potential]

   * The changes are all upstream since a long time now (lowering the risk 
 of silly mistakes)
   * The changes are isolated to ppc, so in the worst case only this arch 
 should regress.
   * We implement new hcalls, so if anything there might be a regression if 
 software expected them to fail, but now breaks by them working (don't 
 think so given the nature of these hcalls).

  [Other Info]
   
   * n/a

  ---

  kernel: 4.10.0-33.37~16.04.1

  I think this issue was introduced by the old qemu version (similar
  issue was spotted on Xenial before), will need to investigate this
  further.

  qemu-system-ppc64 -machine pseries,accel=kvm -bios powerpc/boot_rom.bin 
-display none -serial stdio -kernel powerpc/spapr_hcall.elf -smp 1
  FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x41a588
  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

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

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

[Kernel-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave ~/core files (not crash files)

I wonder - is this the default kernel behaviour if the pipe command
fails?

/proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P

** Summary changed:

- gnome-shell and Xwayland sometimes leave ~/core files (not crash files)
+ gnome-shell and Xwayland sometimes leave $HOME/core files (should be crash 
files)

** Description changed:

- gnome-shell and Xwayland sometimes leave ~/core files (not crash files)
+ gnome-shell and Xwayland sometimes leave $HOME/core files (should be
+ /var/crash files).
  
  This is despite:
  
  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0
  
  So really there are two problems:
  
  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:
-  
+ 
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- gnome-shell and Xwayland sometimes leave $HOME/core files (should be crash 
files)
+ gnome-shell and Xwayland sometimes leave $HOME/core files (should be 
/var/crash files)

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

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2018-02-01 Thread bugproxy

--- Comment From shriy...@in.ibm.com 2018-02-02 02:08 EDT---
(In reply to comment #7)
> I built a test kernel with commit 5aa04b3eb6fca.  The test kernel can be
> downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1746225
>
> Can you test this kernel and see if it resolves this bug?
>
> Note, to test this kernel, you need to install both the linux-image and
> linux-image-extra .deb packages.
>
> Thanks in advance!

Issue is resolved.

Verified the kernel provided in
http://kernel.ubuntu.com/~jsalisbury/lp1746225  fixes the issue.

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

Title:
  [P9,Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when
  grouping different pmu events using perf fuzzer . (perf:)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.

  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13


  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
  [78592.995982] SMP NR_CPUS=2048 
  [78592.995985] NUMA 
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
  [78592.996642] CFAR: c00e9b18 SOFTE: 1 
  [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 
 
  [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10 
  [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028 
  [78592.996642] GPR12:  c7a8d480  
 
  [78592.996642] GPR16:    
 
  [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98 
  [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0 
  [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190 
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c
  [78592.997568] Instruction dump:
  [78592.997597]        
 
  [78592.997664]        
 
  [78592.997733] ---[ end trace 57fb7542c4083583 ]---
  [78594.008780] 
  [78594.008932] Sending IP[78773.335857584,5] OPAL: Switch to big-endian OS
  I to other CPUs
  [78594.01029

  Steps to reproduce :
  

  #! /bin/bash
  set -x
  git clone https://github.com/deater/perf_event_tests.git
  cd perf_event_tests/include
  mkdir asm
  cd asm
  wget http://9.114.13.132/repo/shriya/perf_regs.h
  cd ../../lib
  make
  sleep 10
  cd ../fuzzer
  make
  sleep 10

  echo 0 > /proc/sys/kernel/nmi_watchdog
  echo 2 >

[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

Cool! Thanks a lot!

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

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

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

[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

> On Feb 2, 2018, at 1:59 PM, PeterPall <1746...@bugs.launchpad.net> wrote:
> 
>> Do you see "Set BT/WLAN RX diversity capability” in dmesg? Your wireless
>> chip doesn’t support bt_ant_diversity if you don’t see this message.
> Seems like my wireless chip doesn't support it: My dmesg starts with probing 
> the CPU on starting the kernel but doesn't contain this message.
> 
> => I would be happy with btcoex_enable=1 without using bt_ant_diversity=1.
> Hope that this method isn't a regression for wifi-only users. While bluetooth 
> is in use it enhances wifi performance a lot for me.

Okay, I’ll sent a patch to enable it and discuss with ath9k maintainers.

> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1746164
> 
> Title:
>  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
>  and network skip on Wifi activity)
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  By default BT audio works fine on Ubuntu - if there is no WiFi active:
>  Both work on the same frequency range, 2 WiFi channel is about 20
>  Bluetooth Channels wide and every time a WiFi package is sent
>  bluetooth risks a packet loss.
> 
>  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
>  following content:
> 
>  options ath9k btcoex_enable=1 bt_ant_diversity=1
> 
>  resolves the problem and drastically increases bluetooth throughput
>  for all other use cases (bluetooth networking that doesn't drop every
>  time the WiFi probes something, lower latency Bluetooth HIDs.
> 
>  We should ship things in a way that they work out-of-the-box => I am
>  all for providing this file with Ubuntu, possibly with Bluez.
> 
>  In the case of my laptop btcoex_enable=1 would already do the trick.
> 
> 
>  Technical background:
>   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
>   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: bluez 5.46-0ubuntu4
>  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
>  ApportVersion: 2.20.8-0ubuntu6
>  Architecture: amd64
>  CurrentDesktop: GNOME
>  Date: Tue Jan 30 06:40:12 2018
>  EcryptfsInUse: Yes
>  InterestingModules: rfcomm bnep btusb bluetooth
>  MachineType: Acer Aspire S7-391
>  ProcEnviron:
>   TERM=xterm-256color
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=de_DE.UTF-8
>   SHELL=/bin/bash
>  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
> root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
> acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
> nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
> intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
>  SourcePackage: bluez
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 11/16/2012
>  dmi.bios.vendor: Insyde Corp.
>  dmi.bios.version: V2.09
>  dmi.board.asset.tag: No Asset Tag
>  dmi.board.name: Storm
>  dmi.board.vendor: Acer
>  dmi.board.version: V2.09
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Acer
>  dmi.chassis.version: V2.09
>  dmi.modalias: 
> dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
>  dmi.product.family: ChiefRiver System
>  dmi.product.name: Aspire S7-391
>  dmi.product.version: V2.09
>  dmi.sys.vendor: Acer
>  hciconfig:
>   hci0:   Type: Primary  Bus: USB
>   BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
>   UP RUNNING PSCAN 
>   RX bytes:688 acl:0 sco:0 events:49 errors:0
>   TX bytes:3167 acl:0 sco:0 commands:49 errors:0
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164/+subscriptions


** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they

[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

> Do you see "Set BT/WLAN RX diversity capability” in dmesg? Your wireless
> chip doesn’t support bt_ant_diversity if you don’t see this message.
Seems like my wireless chip doesn't support it: My dmesg starts with probing 
the CPU on starting the kernel but doesn't contain this message.

=> I would be happy with btcoex_enable=1 without using bt_ant_diversity=1.
Hope that this method isn't a regression for wifi-only users. While bluetooth 
is in use it enhances wifi performance a lot for me.

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

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

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

[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

It should be "This will be a regression for people who only use WiFi but
not Bluetooth".

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

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

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

Re: [Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

> On Feb 2, 2018, at 12:56 PM, Daniel van Vugt  
> wrote:
> 
> "to let WiFi use two antennas when BT is off" is indeed nice to have
> too, yes.
> 
> However this bug is titled "Enable Bluetooth-Wifi coexistence by
> default". So it sounds like we need both:
> 
>  btcoex_enable=1 bt_ant_diversity=1
> 
> The problem we aim to solve here is fixing Bluetooth performance, not
> fixing wifi performance.

This will be a regression for people don’t use WiFi.

> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1746164
> 
> Title:
>  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
>  and network skip on Wifi activity)
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  By default BT audio works fine on Ubuntu - if there is no WiFi active:
>  Both work on the same frequency range, 2 WiFi channel is about 20
>  Bluetooth Channels wide and every time a WiFi package is sent
>  bluetooth risks a packet loss.
> 
>  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
>  following content:
> 
>  options ath9k btcoex_enable=1 bt_ant_diversity=1
> 
>  resolves the problem and drastically increases bluetooth throughput
>  for all other use cases (bluetooth networking that doesn't drop every
>  time the WiFi probes something, lower latency Bluetooth HIDs.
> 
>  We should ship things in a way that they work out-of-the-box => I am
>  all for providing this file with Ubuntu, possibly with Bluez.
> 
>  In the case of my laptop btcoex_enable=1 would already do the trick.
> 
> 
>  Technical background:
>   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
>   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: bluez 5.46-0ubuntu4
>  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
>  ApportVersion: 2.20.8-0ubuntu6
>  Architecture: amd64
>  CurrentDesktop: GNOME
>  Date: Tue Jan 30 06:40:12 2018
>  EcryptfsInUse: Yes
>  InterestingModules: rfcomm bnep btusb bluetooth
>  MachineType: Acer Aspire S7-391
>  ProcEnviron:
>   TERM=xterm-256color
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=de_DE.UTF-8
>   SHELL=/bin/bash
>  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
> root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
> acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
> nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
> intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
>  SourcePackage: bluez
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 11/16/2012
>  dmi.bios.vendor: Insyde Corp.
>  dmi.bios.version: V2.09
>  dmi.board.asset.tag: No Asset Tag
>  dmi.board.name: Storm
>  dmi.board.vendor: Acer
>  dmi.board.version: V2.09
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Acer
>  dmi.chassis.version: V2.09
>  dmi.modalias: 
> dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
>  dmi.product.family: ChiefRiver System
>  dmi.product.name: Aspire S7-391
>  dmi.product.version: V2.09
>  dmi.sys.vendor: Acer
>  hciconfig:
>   hci0:   Type: Primary  Bus: USB
>   BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
>   UP RUNNING PSCAN 
>   RX bytes:688 acl:0 sco:0 events:49 errors:0
>   TX bytes:3167 acl:0 sco:0 commands:49 errors:0
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164/+subscriptions

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   -

Re: [Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

> On Feb 2, 2018, at 1:14 PM, PeterPall <1746...@bugs.launchpad.net> wrote:
> 
> I had tried all combinations:
> 
> - btcoex_enable=0 and bt_ant_diversity=1 does help a little bit with 
> bluetooth. But not much

Do you see "Set BT/WLAN RX diversity capability” in dmesg? Your wireless
chip doesn’t support bt_ant_diversity if you don’t see this message.

> - btcoex_enable=1 and bt_ant_diversity=0 does solve the bluetooth problem for 
> me
> - btcoex_enable=1 and bt_ant_diversity=1 Here I have the feeling that it 
> makes changing files and fast-forward/fast-backward smoother in mplayer 
> (btcoex_enable=1 and bt_ant_diversity=0 in rare cases gives "bluetooth device 
> stuck" messages, but working audio).

BT antenna diversity won’t get set when btcoex_enable is 1. So both
bt_ant_diversity=[0,1] have the same effect.

> - btcoex_enable=0 and bt_ant_diversity=0: Bluetooth keeps hanging *and* low 
> wifi performance while using bluetooth.
> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1746164
> 
> Title:
>  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
>  and network skip on Wifi activity)
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  By default BT audio works fine on Ubuntu - if there is no WiFi active:
>  Both work on the same frequency range, 2 WiFi channel is about 20
>  Bluetooth Channels wide and every time a WiFi package is sent
>  bluetooth risks a packet loss.
> 
>  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
>  following content:
> 
>  options ath9k btcoex_enable=1 bt_ant_diversity=1
> 
>  resolves the problem and drastically increases bluetooth throughput
>  for all other use cases (bluetooth networking that doesn't drop every
>  time the WiFi probes something, lower latency Bluetooth HIDs.
> 
>  We should ship things in a way that they work out-of-the-box => I am
>  all for providing this file with Ubuntu, possibly with Bluez.
> 
>  In the case of my laptop btcoex_enable=1 would already do the trick.
> 
> 
>  Technical background:
>   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
>   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: bluez 5.46-0ubuntu4
>  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
>  ApportVersion: 2.20.8-0ubuntu6
>  Architecture: amd64
>  CurrentDesktop: GNOME
>  Date: Tue Jan 30 06:40:12 2018
>  EcryptfsInUse: Yes
>  InterestingModules: rfcomm bnep btusb bluetooth
>  MachineType: Acer Aspire S7-391
>  ProcEnviron:
>   TERM=xterm-256color
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=de_DE.UTF-8
>   SHELL=/bin/bash
>  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
> root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
> acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
> nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
> intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
>  SourcePackage: bluez
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 11/16/2012
>  dmi.bios.vendor: Insyde Corp.
>  dmi.bios.version: V2.09
>  dmi.board.asset.tag: No Asset Tag
>  dmi.board.name: Storm
>  dmi.board.vendor: Acer
>  dmi.board.version: V2.09
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Acer
>  dmi.chassis.version: V2.09
>  dmi.modalias: 
> dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
>  dmi.product.family: ChiefRiver System
>  dmi.product.name: Aspire S7-391
>  dmi.product.version: V2.09
>  dmi.sys.vendor: Acer
>  hciconfig:
>   hci0:   Type: Primary  Bus: USB
>   BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
>   UP RUNNING PSCAN 
>   RX bytes:688 acl:0 sco:0 events:49 errors:0
>   TX bytes:3167 acl:0 sco:0 commands:49 errors:0
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164/+subscriptions

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth

[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

I had tried all combinations:

 - btcoex_enable=0 and bt_ant_diversity=1 does help a little bit with 
bluetooth. But not much
 - btcoex_enable=1 and bt_ant_diversity=0 does solve the bluetooth problem for 
me
 - btcoex_enable=1 and bt_ant_diversity=1 Here I have the feeling that it makes 
changing files and fast-forward/fast-backward smoother in mplayer 
(btcoex_enable=1 and bt_ant_diversity=0 in rare cases gives "bluetooth device 
stuck" messages, but working audio).
 - btcoex_enable=0 and bt_ant_diversity=0: Bluetooth keeps hanging *and* low 
wifi performance while using bluetooth.

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

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

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

[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

"to let WiFi use two antennas when BT is off" is indeed nice to have
too, yes.

However this bug is titled "Enable Bluetooth-Wifi coexistence by
default". So it sounds like we need both:

  btcoex_enable=1 bt_ant_diversity=1

The problem we aim to solve here is fixing Bluetooth performance, not
fixing wifi performance.

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

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

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

[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver

Ok, just bootstrapped a Artful system, looks like you should remove
nvidia-381 and use nvidia-384.

nvidia-384 is built correctly on 4.13.0-32-generic.

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

Title:
  Kernel 4.13.0-25 broke nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.13.0-25-generic the binary nvidia
  driver 387.22 cannot be built. As a result the system does not boot
  into the desktop environment (in my case, KDE).

  I've attached the driver build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   3049 F pulseaudio
   /dev/snd/controlC2:  lastique   3049 F pulseaudio
   /dev/snd/controlC3:  lastique   3049 F pulseaudio
   /dev/snd/controlC1:  lastique   3049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:00:46 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

Re: [Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

> On Feb 2, 2018, at 10:05 AM, Daniel van Vugt  
> wrote:
> 
> It sounds like maybe @peterpall isn't doing what @kaihengfeng asked:
> 
>  btcoex_enable=0 bt_ant_diversity=1
> 
> But at the same time it also sounds like @kaihengfeng is trying to solve
> the wrong problem, judging by comment #20. Actually it sounds like the
> fix @peterpall needs is just:

Judging from the comment, bt_ant_diversity is what we want, to let WiFi
use two antennas when BT is off.

> 
>  btcoex_enable=1

IIUC, this will let WiFi uses single antenna all the time. Not something
user really want.

> 
> Which is what the title of the bug says too :)
> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1746164
> 
> Title:
>  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
>  and network skip on Wifi activity)
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  By default BT audio works fine on Ubuntu - if there is no WiFi active:
>  Both work on the same frequency range, 2 WiFi channel is about 20
>  Bluetooth Channels wide and every time a WiFi package is sent
>  bluetooth risks a packet loss.
> 
>  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
>  following content:
> 
>  options ath9k btcoex_enable=1 bt_ant_diversity=1
> 
>  resolves the problem and drastically increases bluetooth throughput
>  for all other use cases (bluetooth networking that doesn't drop every
>  time the WiFi probes something, lower latency Bluetooth HIDs.
> 
>  We should ship things in a way that they work out-of-the-box => I am
>  all for providing this file with Ubuntu, possibly with Bluez.
> 
>  In the case of my laptop btcoex_enable=1 would already do the trick.
> 
> 
>  Technical background:
>   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
>   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: bluez 5.46-0ubuntu4
>  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
>  ApportVersion: 2.20.8-0ubuntu6
>  Architecture: amd64
>  CurrentDesktop: GNOME
>  Date: Tue Jan 30 06:40:12 2018
>  EcryptfsInUse: Yes
>  InterestingModules: rfcomm bnep btusb bluetooth
>  MachineType: Acer Aspire S7-391
>  ProcEnviron:
>   TERM=xterm-256color
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=de_DE.UTF-8
>   SHELL=/bin/bash
>  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
> root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
> acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
> nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
> intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
>  SourcePackage: bluez
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 11/16/2012
>  dmi.bios.vendor: Insyde Corp.
>  dmi.bios.version: V2.09
>  dmi.board.asset.tag: No Asset Tag
>  dmi.board.name: Storm
>  dmi.board.vendor: Acer
>  dmi.board.version: V2.09
>  dmi.chassis.asset.tag: No Asset Tag
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: Acer
>  dmi.chassis.version: V2.09
>  dmi.modalias: 
> dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
>  dmi.product.family: ChiefRiver System
>  dmi.product.name: Aspire S7-391
>  dmi.product.version: V2.09
>  dmi.sys.vendor: Acer
>  hciconfig:
>   hci0:   Type: Primary  Bus: USB
>   BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
>   UP RUNNING PSCAN 
>   RX bytes:688 acl:0 sco:0 events:49 errors:0
>   TX bytes:3167 acl:0 sco:0 commands:49 errors:0
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164/+subscriptions

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In

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

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

apport-collect 1746860

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

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

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

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

** Tags added: trusty

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

Title:
  CPU Soft Lockup Causing Trusty (4.4.0-111-generic) to become
  unresponsive

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  qemu-system 2.0.0+dfsg-2ubuntu1.36

  3) What you expected to happen
  The system should not have crashed

  4) What happened instead
  The system crashed and reported CPU soft lockup errors.

  Hi,

  we had a system lock up completely today, we noticed the following in the 
logs:
  [84070301.087602] BUG: soft lockup - CPU#1 stuck for 23s! 
[qemu-system-x86:30908]
  [84070301.271530] BUG: soft lockup - CPU#8 stuck for 22s! [khugepaged:238]
  [84070314.314615] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} 
(detected by 19, t=150024 jiffies, g=8647354832, c=8647354831, q=0)
  [84070341.072534] BUG: soft lockup - CPU#1 stuck for 22s! 
[qemu-system-x86:30908]

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

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

[Kernel-packages] [Bug 1746860] Re: CPU Soft Lockup Causing Trusty (4.4.0-111-generic) to become unresponsive

2018-02-01 Thread Thomas Cuthbert

** Description changed:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 14.04.5 LTS
  Release:14.04
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
+ qemu-system 2.0.0+dfsg-2ubuntu1.36
  
  3) What you expected to happen
  The system should not have crashed
  
  4) What happened instead
  The system crashed and reported CPU soft lockup errors.
  
  Hi,
  
  we had a system lock up completely today, we noticed the following in the 
logs:
  [84070301.087602] BUG: soft lockup - CPU#1 stuck for 23s! 
[qemu-system-x86:30908]
  [84070301.271530] BUG: soft lockup - CPU#8 stuck for 22s! [khugepaged:238]
  [84070314.314615] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} 
(detected by 19, t=150024 jiffies, g=8647354832, c=8647354831, q=0)
  [84070341.072534] BUG: soft lockup - CPU#1 stuck for 22s! 
[qemu-system-x86:30908]

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

Title:
  CPU Soft Lockup Causing Trusty (4.4.0-111-generic) to become
  unresponsive

Status in linux package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  qemu-system 2.0.0+dfsg-2ubuntu1.36

  3) What you expected to happen
  The system should not have crashed

  4) What happened instead
  The system crashed and reported CPU soft lockup errors.

  Hi,

  we had a system lock up completely today, we noticed the following in the 
logs:
  [84070301.087602] BUG: soft lockup - CPU#1 stuck for 23s! 
[qemu-system-x86:30908]
  [84070301.271530] BUG: soft lockup - CPU#8 stuck for 22s! [khugepaged:238]
  [84070314.314615] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} 
(detected by 19, t=150024 jiffies, g=8647354832, c=8647354831, q=0)
  [84070341.072534] BUG: soft lockup - CPU#1 stuck for 22s! 
[qemu-system-x86:30908]

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

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

[Kernel-packages] [Bug 1746771] Re: black background drop-down menu

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

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

Title:
  black background drop-down menu

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1746860] [NEW] CPU Soft Lockup Causing Trusty (4.4.0-111-generic) to become unresponsive

2018-02-01 Thread Thomas Cuthbert

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
qemu-system 2.0.0+dfsg-2ubuntu1.36

3) What you expected to happen
The system should not have crashed

4) What happened instead
The system crashed and reported CPU soft lockup errors.

Hi,

we had a system lock up completely today, we noticed the following in the logs:
[84070301.087602] BUG: soft lockup - CPU#1 stuck for 23s! 
[qemu-system-x86:30908]
[84070301.271530] BUG: soft lockup - CPU#8 stuck for 22s! [khugepaged:238]
[84070314.314615] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected 
by 19, t=150024 jiffies, g=8647354832, c=8647354831, q=0)
[84070341.072534] BUG: soft lockup - CPU#1 stuck for 22s! 
[qemu-system-x86:30908]

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

** Attachment added: "lspci.txt"
   https://bugs.launchpad.net/bugs/1746860/+attachment/5047207/+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/1746860

Title:
  CPU Soft Lockup Causing Trusty (4.4.0-111-generic) to become
  unresponsive

Status in linux package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  qemu-system 2.0.0+dfsg-2ubuntu1.36

  3) What you expected to happen
  The system should not have crashed

  4) What happened instead
  The system crashed and reported CPU soft lockup errors.

  Hi,

  we had a system lock up completely today, we noticed the following in the 
logs:
  [84070301.087602] BUG: soft lockup - CPU#1 stuck for 23s! 
[qemu-system-x86:30908]
  [84070301.271530] BUG: soft lockup - CPU#8 stuck for 22s! [khugepaged:238]
  [84070314.314615] INFO: rcu_sched detected stalls on CPUs/tasks: { 0} 
(detected by 19, t=150024 jiffies, g=8647354832, c=8647354831, q=0)
  [84070341.072534] BUG: soft lockup - CPU#1 stuck for 22s! 
[qemu-system-x86:30908]

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

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

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

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

Title:
  Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15
  retina 2013 late

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I click on the suspend button (alternative of power off button)
  in the menu or I click the power button, the Ubuntu seems like will be
  suspended (with a black screen) and, after 5-10 seconds, come back to
  the login screen.

  Closing the lid also doesn't take effect. It doesn't even turn off the
  display.

  I found that clicking on the suspend button and very quickly closing
  the lid seems to make it stays suspended.

  I'm having this trouble in a Macbook Pro 15 retina 2013 late running a
  Ubuntu 17.10 in the most recent version.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  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
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  otto   1600 F pulseaudio
   /dev/snd/controlC0:  otto   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 22:58:16 2018
  InstallationDate: Installed on 2018-01-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Apple Inc. MacBookPro10,1
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=b05cd5cb-c451-4546-a9e0-377ae91a2e44 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.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00F2.B00.1708080809
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00F2.B00.1708080809:bd08/08/2017:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1746848] [NEW] Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15 retina 2013 late

2018-02-01 Thread Otto Julio Ahlert Pinno

Public bug reported:

When I click on the suspend button (alternative of power off button) in
the menu or I click the power button, the Ubuntu seems like will be
suspended (with a black screen) and, after 5-10 seconds, come back to
the login screen.

Closing the lid also doesn't take effect. It doesn't even turn off the
display.

I found that clicking on the suspend button and very quickly closing the
lid seems to make it stays suspended.

I'm having this trouble in a Macbook Pro 15 retina 2013 late running a
Ubuntu 17.10 in the most recent version.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
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
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  otto   1600 F pulseaudio
 /dev/snd/controlC0:  otto   1600 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  1 22:58:16 2018
InstallationDate: Installed on 2018-01-26 (6 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Apple Inc. MacBookPro10,1
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=b05cd5cb-c451-4546-a9e0-377ae91a2e44 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.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00F2.B00.1708080809
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00F2.B00.1708080809:bd08/08/2017:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.family: Mac
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug artful

** Description changed:

  When I click on the suspend button (alternative of power off button) in
  the menu or I click the power button, the Ubuntu seems like will be
  suspended (with a black screen) and, after 5-10 seconds, come back to
  the login screen.
  
  Closing the lid also doesn't take effect. It doesn't even turn off the
  display.
  
  I found that clicking on the suspend button and very quickly closing the
  lid seems to make it stays suspended.
  
  Probably it is already in the logs I'm sending, however, I'm having this
- trouble in a Macbook Pro retina 2013 late running a Ubuntu 17.10 in the
- most recent version.
+ trouble in a Macbook Pro 15 retina 2013 late running a Ubuntu 17.10 in
+ the most recent version.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  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
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  otto   1600 F pulseaudio
-  /dev/snd/controlC0:  otto   1600 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  otto   1600 F pulseaudio
+  /dev/snd/controlC0:  otto   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 22:58:16 2018
  InstallationDate: Installed on 2018-01-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Apple Inc. MacBookPro10,1
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=b05cd5cb-c451-4546-a9e0-377ae91a2e44 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.2
+  linux-restricted-modules-4.13.0-32-generic N/A
+  linux-backports-modules-4.13.0-32-generic  N/A
+  linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00F2.B00.1708080809
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F

[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

It sounds like maybe @peterpall isn't doing what @kaihengfeng asked:

  btcoex_enable=0 bt_ant_diversity=1

But at the same time it also sounds like @kaihengfeng is trying to solve
the wrong problem, judging by comment #20. Actually it sounds like the
fix @peterpall needs is just:

  btcoex_enable=1

Which is what the title of the bug says too :)

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-02-01 Thread gamdow

> #548
> Is it possible to create some sort of persistence on the liveusb, install the 
> latest kernel, then change my settings upon reboot? 

So I had the variety of this issue where I could only boot from the
particular Ubuntu 17.10 Live USB I did the original install with (BIOS
locked to a particular vendor/iso ID?). After quite a wild journey
trying to find a way to update the Live USB kernel (without modifying
the ID) I discovered a far simpler solution.

0. Presumably you have an installation of the bad 17.10 on the laptop HDD. If 
not, use the Live USB to do that (or another USB stick if you like)
1. Boot from the Live USB. When you reach the grub boot menu, hit 'c' to access 
the grub terminal.
2. Try to find the device id of the partition (e.g. '(hd0,1)') where the Ubuntu 
installation is located. Probe around with commands like 'ls (hd0,1)', 'ls 
(hd1,2)', etc. If SecureBoot is preventing you from using 'ls' try 'cat 
(hd0,1)/etc/issue', it should return something like 'Ubuntu 17.10 \n \l'.
3. Now issue the following commands to set and boot boot from that installation;
  'grub> set root=(hd1,2)' # replace with the id you found in step 2
  'grub> linux /vmlinuz root=/dev/sda2' # While sdb2 is the equivalent of 
(hd1,2), the root for this command is not necessarily the same as the previous 
one. The boot drive will be promoted to sda, replacing the USB stick. So root 
here should be sda2 for an installation with the default partitioning. Getting 
this wrong will result in init script error along the lines of 'can't mount 
/dev to /root/dev'. You may be able to figure out the correct root from the 
(initrmfs) terminal you end up in, try 'ls' there.
  'grub> initrd /initrd.img'
  'grub> boot'
4. Follow the OP's instructions for updating the Kernel, up to and including 
the reboot. However, you will end up back at the Live USB grub menu, but this 
is fine an you are nearly done.
5. Execute steps 1 to 3 again. This will boot the installation with the new 
kernel.
6. Reboot, access BIOS menu and check you can modify settings.
7. Pull the Live USB and burn it in a fire.

At this point, my BIOS was fixed, but I was still booting to the grub
menu. So I just did a fresh install of the fixed Ubuntu (17.10.1).

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30

[Kernel-packages] [Bug 1586539] Re: Major screen flickering in Chromium and Google Chrome

2018-02-01 Thread Kerry Martin

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kerry Martin (kerryg)

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

Title:
  Major screen flickering in Chromium and Google Chrome

Status in OEM Priority Project:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  On a fresh installation of Ubuntu 16.04 I noticed major screen
  flickering issues in Chromium and Google Chrome browsers. Since this
  never happened in Ubuntu 15.10 with exactly the same Google Chrome
  binary, I believe, bug is caused by something that was added/updated
  in 16.04. I came across some discussions where different people
  suggested that it is related to new X.Org version.

  Here's a video to show what is happening:
  https://youtu.be/l21WsKz3fZc?t=45s

  I could fix this flickering with --disable-gpu-compositing switch, but
  this slows down page drawing significantly so it can't be considered a
  workaround. There is also a Chromium bug report:
  https://bugs.chromium.org/p/chromium/issues/detail?id=606152, but I
  don't think they will fix an Ubuntu-specific bug.

  Update: this indeed happens only when browser window is maximized.

  WORKAROUND:

  1. sudo apt-get purge xserver-xorg-video-intel
  2. sudo rm /usr/share/X11/xorg.conf.d/20-intel.conf (for those who created 
this file before)
  3. reboot

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.0-040600-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 28 00:01:20 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.20, 4.4.0-22-generic, x86_64: installed
   vboxhost, 5.0.20, 4.6.0-040600-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13bd]
  InstallationDate: Installed on 2016-05-01 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. UX301LAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic 
root=UUID=172b2d49-444a-466b-ab91-b74605125b29 ro quiet splash rootfstype=ext4 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX301LAA.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX301LAA
  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.:bvrUX301LAA.211:bd06/05/2015:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX301LAA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 22 23:28:15 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5126
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1586539/+subscriptions

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

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

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

apport-collect 1746837

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

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

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

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

** Tags added: xenial

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

Title:
   Add support for Realtek card reader RTL8411B [10EC:5287]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The latest kernel upgrade seems to break the driver.

  Ubuntu 4.4.0-112.135-generic 4.4.98
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:5287] (rev 01)

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

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

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

[Kernel-packages] [Bug 1745945] Re: Kernel update makes HDMI unresponsive

2018-02-01 Thread Caymon

** Tags added: kernel-bug-exists-upstream

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

Title:
  Kernel update makes HDMI unresponsive

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've update to 4.13.0-32-generic in attempts to fix the same problem
  listed in Bug #1734084. The only reason I've made this bug is because
  I'm on 17.10 not 17.04.

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  $ apt-cache policy linux-image-4.13.0-32-generic
  linux-image-4.13.0-32-generic:
Installed: 4.13.0-32.35
Candidate: 4.13.0-32.35
Version table:
   *** 4.13.0-32.35 500
  500 http://mirror.kayo.moe/ubuntu artful-updates/main amd64 Packages
  500 http://mirror.kayo.moe/ubuntu artful-security/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  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.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caymon 1499 F pulseaudio
   /dev/snd/pcmC1D0p:   caymon 1499 F...m pulseaudio
   /dev/snd/controlC1:  caymon 1499 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jan 29 00:55:27 2018
  HibernationDevice: RESUME=UUID=29e48daf-947d-44ac-bf09-520219553efe
  InstallationDate: Installed on 2017-10-23 (97 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System76 Lemur
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  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.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76
  dmi.board.version: lemu7
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd01/25/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Lemur
  dmi.product.version: lemu7
  dmi.sys.vendor: System76

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

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

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

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This was on bootup of live usb

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-studio   2178 F pulseaudio
   /dev/snd/controlC0:  ubuntu-studio   2178 F pulseaudio
  CasperVersion: 1.387
  Date: Fri Feb  2 00:37:55 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location EIP: sanity+0xf/0xc0
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  LiveMediaBuild: Ubuntu-Studio 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/ubnkern initrd=/ubninit 
file=/cdrom/preseed/ubuntustudio.seed boot=casper 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: unable to handle kernel NULL pointer dereference at 0020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

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

2018-02-01 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  This was on bootup of live usb

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-studio   2178 F pulseaudio
   /dev/snd/controlC0:  ubuntu-studio   2178 F pulseaudio
  CasperVersion: 1.387
  Date: Fri Feb  2 00:37:55 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location EIP: sanity+0xf/0xc0
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  LiveMediaBuild: Ubuntu-Studio 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/ubnkern initrd=/ubninit 
file=/cdrom/preseed/ubuntustudio.seed boot=casper 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: unable to handle kernel NULL pointer dereference at 0020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Kernel-packages] [Bug 1746838] [NEW] BUG: unable to handle kernel NULL pointer dereference at 00000020

2018-02-01 Thread Swanhart

Public bug reported:

This was on bootup of live usb

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency i686
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ubuntu-studio   2178 F pulseaudio
 /dev/snd/controlC0:  ubuntu-studio   2178 F pulseaudio
CasperVersion: 1.387
Date: Fri Feb  2 00:37:55 2018
DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location EIP: sanity+0xf/0xc0
Failure: oops
IwConfig:
 lono wireless extensions.
 
 enp10s0   no wireless extensions.
LiveMediaBuild: Ubuntu-Studio 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/ubnkern initrd=/ubninit 
file=/cdrom/preseed/ubuntustudio.seed boot=casper 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: unable to handle kernel NULL pointer dereference at 0020
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/08/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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


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

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  This was on bootup of live usb

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency i686
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-studio   2178 F pulseaudio
   /dev/snd/controlC0:  ubuntu-studio   2178 F pulseaudio
  CasperVersion: 1.387
  Date: Fri Feb  2 00:37:55 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location EIP: sanity+0xf/0xc0
  Failure: oops
  IwConfig:
   lono wireless extensions.
   
   enp10s0   no wireless extensions.
  LiveMediaBuild: Ubuntu-Studio 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/ubnkern initrd=/ubninit 
file=/cdrom/preseed/ubuntustudio.seed boot=casper 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: unable to handle kernel NULL pointer dereference at 0020
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by

[Kernel-packages] [Bug 1746837] [NEW] Add support for Realtek card reader RTL8411B [10EC:5287]

2018-02-01 Thread Alex

Public bug reported:

The latest kernel upgrade seems to break the driver.

Ubuntu 4.4.0-112.135-generic 4.4.98
05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:5287] (rev 01)

Description:Ubuntu 16.04.3 LTS
Release:16.04

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

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

Title:
   Add support for Realtek card reader RTL8411B [10EC:5287]

Status in linux package in Ubuntu:
  New

Bug description:
  The latest kernel upgrade seems to break the driver.

  Ubuntu 4.4.0-112.135-generic 4.4.98
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 
[10ec:5287] (rev 01)

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

Nevermind comment #44.  I see that is already posted to the bug.  I'll
see if I can see which config change could have caused this withing
needing a bisect between those two versions.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

Thanks for testing those two.  That really points at a config change.
Can you post the output from the following, so I can see the hardware
info:

dmesg > dmesg.log
lspci -vvnn > lspci-vvnn.log

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

2018-02-01 Thread dann frazier

** Description changed:

  [Impact]
  After upgrading your KVM hypervisor past xenial, your xenial-based guests 
will fail to boot.
  
  [Test Case]
  Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.
  
  [Regression Risk]
- TBD
+ I've tested booting a xenial cloud image in bionic (ACPI mode), and 
regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a 
Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.
+ 
+ Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel
+ only supported 2 GICv3 systems - the 1 socket and 2 socket variants of
+ the Cavium ThunderX CRB - and I've regression tested on those systems.
+ 
+ Patch 6 only adds new macro definitions.
+ 
+ Patch 7 is restricted to devicetree code, except for a change to
+ earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is passed
+ on the cmdline (vs. earlycon=something), this function used to return 0
+ - but now it will return -ENODEV on non-devicetree systems, which is a
+ subtle API change. However, according to kernel-parameters.txt (and the
+ code itself), 'earlycon' by itself is only valid on devicetree systems.
+ Just to be sure, I booted an x86 system up w/ 'earlycon' with and
+ without this series, and observed no difference.
+ 
+ Patch 8 adds the SPCR table parser, but no caller to it yet. It also
+ modifies the same earlycon code as Patch 7 - here it avoids earlycon
+ init in the case that the devicetree-specific 'earlycon' was passed. As
+ mentioned in my analysis Patch 7, this codepath is only supported for
+ devicetree systems, and has been regression tested on x86.
+ 
+ Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will only
+ be built for arm64. TBH, I'm not 100% sure how Kconfig knows not to
+ build this for other archs - but I checked the logs, and there's no
+ spcr.o built on other archs. (Not that that should be a problem - they
+ would just grow a bit of unused code).
+ 
+ Patch 10 only touches arm64-specific code, adding the call to
+ parse_spcr().
+ 
+ Patch 11 adds a new match method to the ARM-specific pl011 console
+ driver.

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => dann frazier (dannf)

** Description changed:

  [Impact]
- After upgrading your KVM hypervisor past xenial, your xenial-based guests 
will fail to boot.
+ After upgrading an Ubuntu/arm64 KVM host past xenial, your xenial-based 
guests will fail to boot.
  
  [Test Case]
  Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.
  
  [Regression Risk]
  I've tested booting a xenial cloud image in bionic (ACPI mode), and 
regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a 
Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.
  
  Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel
  only supported 2 GICv3 systems - the 1 socket and 2 socket variants of
  the Cavium ThunderX CRB - and I've regression tested on those systems.
  
  Patch 6 only adds new macro definitions.
  
  Patch 7 is restricted to devicetree code, except for a change to
  earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is passed
  on the cmdline (vs. earlycon=something), this function used to return 0
  - but now it will return -ENODEV on non-devicetree systems, which is a
  subtle API change. However, according to kernel-parameters.txt (and the
  code itself), 'earlycon' by itself is only valid on devicetree systems.
  Just to be sure, I booted an x86 system up w/ 'earlycon' with and
  without this series, and observed no difference.
  
  Patch 8 adds the SPCR table parser, but no caller to it yet. It also
  modifies the same earlycon code as Patch 7 - here it avoids earlycon
  init in the case that the devicetree-specific 'earlycon' was passed. As
  mentioned in my analysis Patch 7, this codepath is only supported for
  devicetree systems, and has been regression tested on x86.
  
  Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will only
  be built for arm64. TBH, I'm not 100% sure how Kconfig knows not to
  build this for other archs - but I checked the logs, and there's no
  spcr.o built on other archs. (Not that that should be a problem - they
  would just grow a bit of unused code).
  
  Patch 10 only touches arm64-specific code, adding the call to
  parse_spcr().
  
  Patch 11 adds a new match method to the ARM-specific pl011 console
  driver.

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

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

Status in cloud-images:
  New
Status in edk2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in edk2 source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  [Impact]
  After

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

Linux flimsy 4.12.0-13-generic #14-Ubuntu SMP Sat Sep 2 15:52:55 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

works;

Linux flimsy 4.13.0-10-generic #11-Ubuntu SMP Sun Sep 10 23:39:40 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

does not.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver

2018-02-01 Thread Frederik Fromm

See make.log

** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742302/+attachment/5047071/+files/make.log

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

Title:
  Kernel 4.13.0-25 broke nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.13.0-25-generic the binary nvidia
  driver 387.22 cannot be built. As a result the system does not boot
  into the desktop environment (in my case, KDE).

  I've attached the driver build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   3049 F pulseaudio
   /dev/snd/controlC2:  lastique   3049 F pulseaudio
   /dev/snd/controlC3:  lastique   3049 F pulseaudio
   /dev/snd/controlC1:  lastique   3049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:00:46 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver

2018-02-01 Thread Frederik Fromm

No didn't work:
dkms install nvidia-381/381.22 -k 4.13.0-25-generic

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'make' -j8 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=4.13.0-25-generic 
IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/lib/modules/4.13.0-25-generic/build LD=/usr/bin/ld.bfd modules.(bad 
exit status: 2)
Error! Bad return status for module build on kernel: 4.13.0-25-generic (x86_64)
Consult /var/lib/dkms/nvidia-381/381.22/build/make.log for more information.

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

Title:
  Kernel 4.13.0-25 broke nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.13.0-25-generic the binary nvidia
  driver 387.22 cannot be built. As a result the system does not boot
  into the desktop environment (in my case, KDE).

  I've attached the driver build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   3049 F pulseaudio
   /dev/snd/controlC2:  lastique   3049 F pulseaudio
   /dev/snd/controlC3:  lastique   3049 F pulseaudio
   /dev/snd/controlC1:  lastique   3049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:00:46 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1745282] Re: Freezes XPS 13

2018-02-01 Thread Shaun Newcomer

Confirmed that 4.15.0-041500-lowlatency fixes the problem on an XPS 13
9360.

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

Title:
  Freezes XPS 13

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This kernel boots on the XPS 13 but in less than a minute it hard
  freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahron  2235 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 24 22:41:26 2018
  InstallationDate: Installed on 2018-01-04 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=5b8ac06d-8cf5-4417-85d2-df12f2d0dc30 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 0PVG6D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd12/12/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745104] Re: ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM guest

Commit 2621e945fbf1d is now in Bionic as of kernel version
Ubuntu-4.14.0-12.14.

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

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

Title:
  ISST-LTE: KVM:UBUNTU1804: kdump is not working on UbuntuKVM  guest

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

Bug description:
  == Comment: #0 - Chanh H. Nguyen  - 2018-01-23 14:55:05 
==
  root@boslcp4g5:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Bionic Beaver (development branch)"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  root@boslcp4g5:~# uname -r
  4.13.0-25-generic
  root@boslcp4g5:~# 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-25-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-25-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.13.0-25-generic 
root=UUID=8a776bc5-d9e0-4a1d-9218-135f9c702e11 ro splash quiet nr_cpus=1 
systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@boslcp4g5:~# kdump-config status
  current state   : ready to kdump
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  176.911191] sysrq: SysRq : This sysrq operation is disabled.
  root@boslcp4g5:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1
  root@boslcp4g5:~# echo c > /proc/sysrq-trigger
  [  240.304466] sysrq: SysRq : Trigger a crash
  [  240.304545] Unable to handle kernel paging request for data at address 
0x
  [  240.304656] Faulting instruction address: 0xc0792f88
  [  240.304771] Oops: Kernel access of bad area, sig: 11 [#1]
  [  240.304846] SMP NR_CPUS=2048
  [  240.304848] NUMA
  [  240.304903] pSeries
  [  240.305000] Modules linked in: sctp_diag sctp libcrc32c dccp_diag dccp 
tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache dm_service_time 
vmx_crypto crct10dif_vpmsum binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua sunrpc sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq 
crc32c_vpmsum virtio_net virtio_scsi
  [  240.305776] CPU: 12 PID: 1860 Comm: bash Not tainted 4.13.0-25-generic 
#29-Ubuntu
  [  240.305886] task: c000ff904500 task.stack: c001f2d7c000
  [  240.305979] NIP: c0792f88 LR: c0793eb8 CTR: 
c0792f60
  [  240.306087] REGS: c001f2d7f9f0 TRAP: 0300   Not tainted  
(4.13.0-25-generic)
  [  240.306195] MSR: 80009033 
  [  240.306207]   CR: 2842  XER: 2004
  [  240.306338] CFAR: c0793eb4 DAR:  DSISR: 4200 
SOFTE: 1
  [  240.306338] GPR00: c0793eb8 c001f2d7fc70 c15f6200 
0063
  [  240.306338] GPR04: c001feeeade8 c001fef02068 6967676572206120 
63726173680d0a72
  [  240.306338] GPR08: 0007 0001  

  [  240.306338] GPR12: c0792f60 c7ac7e00 10180df8 
10189e30
  [  240.306338] GPR16: 10189ea8 10151210 1018bd58 
1018de48
  [  240.306338] GPR20: 28bc0268 0001 10164590 
10163bb0
  [  240.306338] GPR24: 7fffdcb37d34 7fffdcb37d30 c14fa770 
0002
  [  240.306338] GPR28: 0063 0007 c14824f4 
c14fab10
  [  240.307346] NIP [c0792f88] sysrq_handle_crash+0x28/0x30
  [  240.307474] LR [c0793eb8] __handle_sysrq+0xf8/0x2b0
  [  240.307553] Call Trace:
  [  240.307594] [c001f2d7fc70] [c0793e98] 
__handle_sysrq+0xd8/0x2b0 (unreliable)
  [  240.307715] [c001f2d7fd10] [c07946b4] 
write_sysrq_trigger+0x64/0x90
  [  240.307850] [c001f2d7fd40] [c044fb28] proc_reg_write+0x88/0xd0
  [  240.307951] [c001f2d7fd70] [c03a160c] __vfs_write+0x3c/0x70
  [  240.308049] [c001f2d7fd90] [c03a3248] vfs_write+0xd8/0x220
  [  240.308149] [c001f2d7fde0] [c03a50c8] SyS_write+0x68/0x110
  [  240.308248] [c001f2d7fe30] [c000b184] system_call+0x58/0x6c
  [  240.308340] Instruction dump:
  [

[Kernel-packages] [Bug 1703742] Re: Transparent hugepages should default to enabled=madvise

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

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

Title:
  Transparent hugepages should default to enabled=madvise

Status in linux package in Ubuntu:
  Fix Released
Status in linux-gke package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-gke source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Released

Bug description:
  SRU Justification, Zesty, Xenial

  [Impact]

  Ubuntu kernels should default transparent_hugepages to
  enabled=madvise, not enabled=always

  (this corresponds to TRANSPARENT_HUGEPAGE_MADVISE=y in .config).

  I've blogged about this at some length here:
  https://blog.nelhage.com/post/transparent-hugepages/ but here is a
  summary:

  Transparent Hugepages are a feature that allows the kernel to attempt
  to automatically back any anonymous maps with "huge" 2MiB page tables,
  instead of the normal 4k entries. It can produce small net performance
  gains in certain benchmarks, but also has numerous downsides, in the
  form of apparent memory leaks and 30% slowdowns or worse for some
  applications. Many popular pieces of software now refuse to run with
  hugepages enabled because of known performance issues.

  Examples of problem reports:
  MongoDB: https://docs.mongodb.com/manual/tutorial/transparent-huge-pages/
  Oracle: 
https://blogs.oracle.com/linux/entry/performance_issues_with_transparent_huge
  Splunk: 
https://docs.splunk.com/Documentation/Splunk/6.5.2/ReleaseNotes/SplunkandTHP
  Go runtime: https://github.com/golang/go/issues/8832
  jemalloc: 
https://blog.digitalocean.com/transparent-huge-pages-and-alternative-memory-allocators/
  node.js: https://github.com/nodejs/node/issues/11077

  Setting `enabled=madvise` enables applications that know they benefit
  from transparent huge pages to opt-in to this feature, while
  eliminating all the problematic behavior for other applications. Note
  also that transparent hugepage settings don't affect the use of
  explicit hugepages via hugetlbfs or mmap(…, MAP_HUGETLB, …)

  [Fix]
  Enable CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y

  [Regression Potential]
  May marginally impact performance, but the benefits of madvise'd huge 
transparent hugepage over-weigh this considerably.

  This has been enabled in Artful since July (and in Bionic) and we've
  not seen any regression reports, so we are confident this has minimal
  impact.

  [Testcase]
  Kernel ADT tests and stress-ng memory tests should not show any regressions.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

Submitted SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089860.html

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1736317] Re: ath10k: enhance rf signal strength

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

Title:
  ath10k: enhance rf signal strength

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  ath10k: add max_tx_power for QCA6174 WLAN.RM.2.0 firmware
  QCA6174 WLAN.RM.2.0 firmware uses max_tx_power instead of using max_reg_power
  to set transmission power. The tx power was about -50dbm, after applying this
  change, it become -32dbm.

  Signed-off-by: Alan Liu 
  Signed-off-by: Kalle Valo 

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=513527c87a7feab2a5b31db07e5b07864d3c08f7

  This fix already included in Zesty/Artful/Bionic kernels.

  This bug is for tracking purposes only, please do not triage.

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

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

[Kernel-packages] [Bug 1738497] Re: Falkor erratum 1041 needs workaround

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

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

Title:
  Falkor erratum 1041 needs workaround

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

Bug description:
  [Impact]
  A hardware issue can lead to a kernel crash or unexpected behavior.

  [Test Case]
  The issue presents itself most commonly as a boot-time crash. It doesn't 
effect all Falkor CPUs, and only rarely occurs on CPUs that are effected.

  [Regression Risk]
  The fix is entirely in arm64 code, mitigating the risk to other 
architectures. The biggest regression risk is performance, as the workaround 
involves adding an instruction barrier prior to disabling the MMU.

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

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

[Kernel-packages] [Bug 1734757] Re: Add installer support for new Broadcom network drivers.

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

Title:
  Add installer support for new Broadcom network drivers.

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Please add bnxt_en_bpo to nic-modules to Ubuntu kernel 4.4.

  bnxt_en_pbo has been available since SAUCE commits with 4.4.0-94.

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

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

[Kernel-packages] [Bug 1706247] Re: Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

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

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

Title:
  Add support for 16g huge pages on Ubuntu 16.04.2 PowerNV

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

Bug description:
  16G Huge Pages are not supported on PowerNV (bare metal) installations. 
Ubuntu 16.04.2 still allows 16G huge pages to be turned on.
   
  Contact Information = Mike Hollinger (mchol...@us.ibm.com) 
   
  ---uname output---
  Linux aprilmin4 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:53:54 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8335-GTB 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Add the following to the kernel boot args (either via editing the 
petitboot boot option manually, or updating /boot/grub/grub.cfg:

  default_hugepagesz=16G hugepagesz=16G hugepages=4

  2. Boot Linux
  3. Observe that the kernel believes 16G huge pages are available:
  ubuntu@aprilmin7:~$ cat /proc/meminfo | grep -i huge
  AnonHugePages:475136 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   16777216 kB
  ubuntu@aprilmin7:~$ ls /sys/devices/system/node/node0/hugepages
  hugepages-1024kB  hugepages-16384kB  hugepages-16777216kB

   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Mike Hollinger (mchol...@us.ibm.com): 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  
  This may be recreated on any bare metal POWER8 server with Ubuntu 16.04.2; I 
haven't checked other versions of Ubuntu.

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

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

[Kernel-packages] [Bug 1730550] Re: e1000e in 4.4.0-97-generic breaks 82574L under heavy load.

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

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

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

Title:
  e1000e in 4.4.0-97-generic breaks 82574L under heavy load.

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

Bug description:
  
  == SRU Justification ==
  This issue was first reported on the netdev email list by Lennart Sorensen:
  https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html

  Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on
  the 82574L under heavy load.

  "Unfortunately this commit changed the driver to assume
  that the Other Causes interrupt can only mean link state change and
  hence sets the flag that (unfortunately) means both link is down and link
  state should be checked. Since this now happens 3000 times per second,
  the chances of it happening while the watchdog_task is checking the link
  state becomes pretty high, and it if does happen to coincice, then the
  watchdog_task will reset the adapter, which causes a real loss of link."

  The original reported experienced this issue on a Supermicro X7SPA-HF-D525 
server board. 
  However, the bug is now seen on many servers running X9DBL-1F server boards. 

  This bug is fixed by commits 19110cfbb34 and 4aea7a5c5e9, which were both 
added
  to mainline in v4.15-rc1.

  The commit that introduced this bug,16ecba5, was added to mainlien in 
v4.5-rc1.  However,
  Xenial recived this commit as well as commit 531ff577a.  Bionic master-next 
does not need
  these commits, since it got them via bug 1735843 and the 4.14.3 updates.

  == Fixes ==
  19110cfbb34 ("e1000e: Separate signaling for link check/link up")
  4aea7a5c5e9 ("e1000e: Avoid receiver overrun interrupt bursts")

  == Regression Potential ==
  These commits are specific to e1000.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  == Original Bug Descriptio ==
  This issue was first reported on the netdev email list by Lennart Sorensen:
  https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html

  Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on
  the 82574L under heavy load.

  "Unfortunately this commit changed the driver to assume
  that the Other Causes interrupt can only mean link state change and
  hence sets the flag that (unfortunately) means both link is down and link
  state should be checked.  Since this now happens 3000 times per second,
  the chances of it happening while the watchdog_task is checking the link
  state becomes pretty high, and it if does happen to coincice, then the
  watchdog_task will reset the adapter, which causes a real loss of link."

  A fix for this issue was accepted into the net-next branch, along with
  other e1000e/igb patches:
  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=f44dea3421b47d355a835e9cfcc59ca7318575a9

  The original reported experienced this issue on a Supermicro X7SPA-
  HF-D525 server board. We see this issue on many servers running X9DBL-
  1F server boards. Both boards use the Intel 82574L for the network
  interfaces.  We see messages like this under heavy load:

  [Nov 6 15:42] e1000e: eth0 NIC Link is Down
  [  +0.001670] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [Nov 6 16:10] e1000e: eth0 NIC Link is Down
  [  +0.008505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [Nov 7 00:49] e1000e: eth0 NIC Link is Down
  [  +2.235111] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx

  We have confirmed that the connected switch sees the link drops also,
  to these are not false alarms from the e1000e driver.

  # lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  I could not cleanly apply the net-next patch to 4.4.0 so I tested with just 
the following cherry picked changes on the latest 4.4.0 kernel source package.
  https://patchwork.ozlabs.org/patch/823942/
  https://patchwork.ozlabs.org/patch/823945/
  https://patchwork.ozlabs.org/patch/823940/
  https://patchwork.ozlabs.org/patch/823941/
  https://patchwork.ozlabs.org/patch/823939/

  Although it's my understanding the first two are the critical ones for
  the race condition. I have been running with the patches e1000e kernel
  driver, under network load for 7 days and I no longer see the network
  interface drops.

  Could we pull these changes into the Ubuntu 4.4.0 kernel ?

  Thanks
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,

[Kernel-packages] [Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops

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

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

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

Title:
  the kernel is blackholing IPv6 packets to linkdown nexthops

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
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:
  In Progress

Bug description:
  == SRU Justification ==
  When the 'ignore_routes_with_linkdown' sysctl is set, we should not
  consider linkdown nexthops during route lookup.

  While the code correctly verifies that the initially selected route
  ('match') has a carrier, it does not perform the same check in the
  subsequent multipath selection, resulting in a potential packet loss.

  In case the chosen route does not have a carrier and the sysctl is set,
  choose the initially selected route.

  This is a regression introduced by commit 35103d11173b in 4.3-rc1.  Commit
  bbfcd7763 resolves this regression and is mainline as of 4.15-rc1.

  == Fix ==
  commit bbfcd77631573ac4a9f57eb6169e04256a111bc1
  Author: Ido Schimmel 
  Date:   Tue Nov 21 09:50:12 2017 +0200

  ipv6: Do not consider linkdown nexthops during multipath

  == Regression Potential ==
  This fix is specific to ipv6 and fixes a current regression.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1745130] Re: Support rfkill-any led trigger for Fujitsu u727

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

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

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

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

Title:
  Support rfkill-any led trigger for Fujitsu u727

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

Bug description:
  I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based 
on Skylake hardware.
  It has a single rfkill button and a single LED for wlan and bluetooth. Both 
device driver currently provide a single rfkill trigger, so the led could just 
be assigned to one. As a result the upstream kernel got a new "rfkill-any" led 
trigger to correctly handle the led with multiple rfkill devices. That was 
added by one of the fujitsu-laptop maintainers and the driver sets it as the 
default trigger.

  commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
  Author: Michał Kępień 
  Date:   Fri Jan 6 07:07:47 2017 +0100

  rfkill: Add rfkill-any LED trigger

  Normally I would simply patch the affected modules using DKMS, like the 
i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW 
without messing with the kernel packages.
  I'm currently waiting for some reviews, like 
https://www.spinics.net/lists/platform-driver-x86/msg14606.html

  But the rfkill support is compiled in, so I can't patch it using DKMS.

  So my first proposed fix would be to include a backport of this patch.
  Alternatively rfkill can be compiled as a module, so I can patch it
  and provide an updated module.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-111-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Wed Jan 24 10:48:28 2018
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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

Title:
  vagrant artful64 box filesystem too small

Status in cloud-images:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [SRU Justfication, Artful]

  [Impact]

  Booting the 4.13 Artful kernel with vagrant using VirtualBox trips the
  warning:

  [ 61.010337] VFS: brelse: Trying to free free buffer
  [ 61.114875] [ cut here ]
  [ 61.114886] WARNING: CPU: 0 PID: 683 at 
/build/linux-XO_uEE/linux-4.13.0/fs/buffer.c:1205 __brelse+0x21/0x30

  and a failed resize of a partition.  The root cause has been bisected
  down to the following commmit:

  commit c20cfc27a47307e811346f85959cf3cc07ae42f9
  Author: Christoph Hellwig 
  Date: Wed Apr 5 19:21:07 2017 +0200

  block: stop using blkdev_issue_write_same for zeroing

  
  [Fix]
  The Upstream commit directly fixes this issue:

  commit d5ce4c31d6df518dd8f63bbae20d7423c5018a6c
  Author: Ilya Dryomov 
  Date:   Mon Oct 16 15:59:10 2017 +0200

  block: cope with WRITE ZEROES failing in blkdev_issue_zeroout()

  ..however we also require a backport of the following upstream commit
  to apply the above commit cleanly.

  commit 425a4dba7953e35ffd096771973add6d2f40d2ed
  Author: Ilya Dryomov 
  Date:   Mon Oct 16 15:59:09 2017 +0200

  block: factor out __blkdev_issue_zero_pages()

  [Testscase]

  On Ubuntu Xenial:

  1. sudo apt-get install virtualbox vagrant
  2. edit /etc/group and add one's user name to the vboxusers group
  3. log out log back
  4. vagrant init ubuntu/artful64
  5. vagrant up
  6. vagrant ssh
  7. dmesg | grep "VFS: brelse"

  without the fix one will see the VFS brelse warning message and the /
  partition will not have been resized.

  with a fixed system there is is no VFS vbrelse warning and / as been
  resized as expected.

  [Regresion potential]
  These patches touch the blk library so potentially it could break the block 
layer and corrupt data on disk.  However these are upstream fixes that address 
the buggy commit c20cfc27a47307e811346f85959cf3cc07ae42f9 and are known to 
address the bug.

  ---


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

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

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

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

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

  vagrant@ubuntu-artful:~$ sudo fdisk -l
  Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x4ad77c39

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

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

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

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

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

[Kernel-packages] [Bug 1732978] Re: Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr fallback"

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

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

Title:
Ubuntu 17.10: Include patch "crypto: vmx - Use skcipher for ctr
fallback"

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

Bug description:
== SRU Justification ==
Artful uses the 4.13 kernel which has an issue with the fallback cipher for
CTR mode. Commit e666d4e9ceec fixes this problem by using a new structure
for the generic ciphers.

This commit is also needed in Bionic until it gets rebased to 4.15.

Commit e666d4e9ceec was added to mainline in v4.15-rc2

== Fix ==
commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
Author: Paulo Flabiano Smorigo
Date: Mon Oct 16 20:54:19 2017 -0200

crypto: vmx - Use skcipher for ctr fallback

== Regression Potential ==
This commit is specific to crypto, and adds a new structure for the generic
ciphers.

== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.

== Original Bug Desription: ==
== Comment: #0 - Paulo Flabiano Smorigo - 2017-11-17
10:29:14 ==
Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
cipher for CTR mode. The commit bellow fixes this problem by using the new
structure for the generic ciphers. Please add it to the kernel package.

https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

== Comment: #1 - VIPIN K. PARASHAR - 2017-11-17
13:38:05 ==
(In reply to comment #0)
> Ubuntu 17.10 uses linux kernel 4.13 witch has a problem with the fallback
> cipher for CTR mode. The commit bellow fixes this problem by using the new
> structure for the generic ciphers. Please add it to the kernel package.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git/
> commit/?id=e666d4e9ceec94c0a88c94b7db31d56474da43b3

Which is commit e666d4e9ceec94

commit e666d4e9ceec94c0a88c94b7db31d56474da43b3
Author: Paulo Flabiano Smorigo
Date: Mon Oct 16 20:54:19 2017 -0200

crypto: vmx - Use skcipher for ctr fallback

Signed-off-by: Paulo Flabiano Smorigo
Signed-off-by: Herbert Xu

Its available with 4.14 kernel.

Hello Canonical,

Please include commit e666d4e9ceec94 - "crypto: vmx - Use skcipher for ctr
fallback"
with Ubuntu 17.10 kernel.

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

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

[Kernel-packages] [Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727

There is now a Trusty based test kernel with this patch available from:
http://kernel.ubuntu.com/~jsalisbury/lp1745130/trusty/

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

Title:
  Support rfkill-any led trigger for Fujitsu u727

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

Bug description:
  I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based 
on Skylake hardware.
  It has a single rfkill button and a single LED for wlan and bluetooth. Both 
device driver currently provide a single rfkill trigger, so the led could just 
be assigned to one. As a result the upstream kernel got a new "rfkill-any" led 
trigger to correctly handle the led with multiple rfkill devices. That was 
added by one of the fujitsu-laptop maintainers and the driver sets it as the 
default trigger.

  commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
  Author: Michał Kępień 
  Date:   Fri Jan 6 07:07:47 2017 +0100

  rfkill: Add rfkill-any LED trigger

  Normally I would simply patch the affected modules using DKMS, like the 
i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW 
without messing with the kernel packages.
  I'm currently waiting for some reviews, like 
https://www.spinics.net/lists/platform-driver-x86/msg14606.html

  But the rfkill support is compiled in, so I can't patch it using DKMS.

  So my first proposed fix would be to include a backport of this patch.
  Alternatively rfkill can be compiled as a module, so I can patch it
  and provide an updated module.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-111-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Wed Jan 24 10:48:28 2018
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1746801] [NEW] Request to update 18.04 kernel aacraid to upstream 4.16 version

2018-02-01 Thread bugproxy

Public bug reported:

We are asking for the aacraid driver to be updated for 18.04 release to
match the latest patches upstream, that targeting 4.16. The desired
patches were merged upstream this week and are present in Linus's
origin/master branch now.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-164193 severity-high 
targetmilestone-inin1804

** Tags added: architecture-ppc64le bugnameltc-164193 severity-high
targetmilestone-inin1804

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

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

Title:
  Request to update 18.04 kernel aacraid to upstream 4.16 version

Status in linux package in Ubuntu:
  New

Bug description:
  We are asking for the aacraid driver to be updated for 18.04 release
  to match the latest patches upstream, that targeting 4.16. The desired
  patches were merged upstream this week and are present in Linus's
  origin/master branch now.

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

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

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

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

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

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

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  Won't Fix
Status in systemd source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed
Status in systemd source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Won't Fix

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  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:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  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: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:

[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

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

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

Title:
  Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
  for 22s! [systemd:1]"

Status in linux package in Ubuntu:
  Fix Committed
Status in qemu-kvm package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  Won't Fix
Status in qemu-kvm source package in Zesty:
  New
Status in linux source package in Artful:
  Fix Committed
Status in qemu-kvm source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in qemu-kvm source package in Bionic:
  Confirmed

Bug description:
  == SRU Justification ==

  The fix to bug 1672819 can cause an lockup because it can spin
  indefinitely waiting for a child to exit.

  [FIX]
  Add a sauce patch to the original fix to insert a reasonable small delay and 
an upper bounds to the number of retries that are made before bailing out with 
an error. This avoids the lockup and also is less aggressive in the retry loop.

  [TEST]
  Without the fix the machine hangs. With the fix, the lockup no longer occurs.

  [REGRESSION POTENTIAL]
  There may be an issue with the interruptible sleep having some unforeseen 
impact with userspace racy code that expects the system call to return quickly 
when the race condition occurs and instead it gets delayed by a few 
milliseconds while the retry loop spins.  However, code that relies on timing 
on fork/exec inside pthreads where this particular code path could bite is 
generally non-POSIX conforming racy code anyhow.

  ---

  
  This is impacting us for ubuntu autopkgtests. Eventually the whole region 
ends up dying because each worker is hit by this bug in turn and backs off 
until the next reset (6 hourly).

  17.10 (and bionic) guests are sometimes failing to reboot. When this
  happens, you see the following in the console

    [[0;32m  OK  [0m] Reached target Shutdown.
    [  191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
    [  226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
    [  226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
    [  226.706093] All QSes seen, last rcu_sched kthread activity 15002 
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
    [  226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0

  One host that exhibits this behaviour was:

    Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

  guest running:

    Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
  (Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
  (Ubuntu 4.13.0-16.19-generic 4.13.4)

  The affected cloud region is running the xenial/Ocata cloud archive,
  so the version of qemu-kvm in there may also be relevant.

  Here's how I reproduced it in lcy01:

    $ for n in {1..30}; do nova boot --flavor m1.small --image 
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name 
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n}; 
done
    $  sudo reboot
    # wait a minute or so for the instances to all reboot
    $ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n} 
| tail; done

  On bad instances you'll see the "soft lockup" message - on good it'll
  reboot as normal.

  We've seen good and bad instances on multiple compute hosts - it
  doesn't feel to me like a host problem but rather a race condition
  somewhere that's somehow either triggered or triggered much more often
  by what lcy01 is running. I always saw this on the first reboot -
  never on first boot, and never on n>1th boot. (But if it's a race then
  that might not mean much.)

  I'll attach a bad and a good console-log for reference.

  If you're at Canonical then see internal rt #107135 for some other
  details.

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

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

[Kernel-packages] [Bug 1730515] Re: Request to backport cxlflash patches to 16.04 HWE Kernel

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

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

Title:
  Request to backport cxlflash patches to 16.04 HWE Kernel

Status in The Ubuntu-power-systems project:
  In Progress
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
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==
  IBM is requesting these three cxlflash patches in the Ubuntu 16.04 HWE and 
newer
  kernels.  All three patches have now landed in mainline v4.15-rc1.

  These commits fix bugs in the existing code - missing VPN could disable a
  card and the write same sector size.

  == Fixes ==
  285e6670d022 ("scsi: cxlflash: Use derived maximum write same length")
  0d4191305e69 ("scsi: cxlflash: Allow cards without WWPN VPD to configure")
  d84c198f43c5 ("scsi: cxlflash: Derive pid through accessors")

  == Regression Potential ==
  Medium.  These patches are not limited to one arch, but they are limited to 
cxlflash.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

Sorry, your right.  These are mainline kernels, so there is no -extra
package.

So it sounds like the bug is due to a config change.  I'll take a look
at the git logs and see if any changes stick out.

Could you give the following two Ubuntu kernels a try:

4.12.0-14: 
https://launchpad.net/ubuntu/+source/linux/4.12.0-13.14/+build/13325106
4.13.0-10: 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+build/13358561

With these kernels, you need to install both the linux-image and linux-
image-extra .debs.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746801] [NEW] Request to update 18.04 kernel aacraid to upstream 4.16 version

2018-02-01 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

We are asking for the aacraid driver to be updated for 18.04 release to
match the latest patches upstream, that targeting 4.16. The desired
patches were merged upstream this week and are present in Linus's
origin/master branch now.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-164193 severity-high 
targetmilestone-inin1804
-- 
Request to update 18.04 kernel aacraid to upstream 4.16 version
https://bugs.launchpad.net/bugs/1746801
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1746519] Re: package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2018-02-01 Thread Eclipticon

Exactly the same problem here, updates/installations via the package
management system are no longer possible.

Please let me know if I can contribute any information on my Ubuntu
17.10 64 bit system for the big picture.

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

Title:
  package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  After executing:
  sudo apt-get autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
linux-headers-4.13.0-21 linux-headers-4.13.0-21-generic
linux-image-4.13.0-21-generic linux-image-extra-4.10.0-42-generic
linux-image-extra-4.13.0-21-generic
  0 upgraded, 0 newly installed, 5 to remove and 10 not upgraded.
  7 not fully installed or removed.
  After this operation, 474 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 297436 files and directories currently installed.)
  Removing linux-headers-4.13.0-21-generic (4.13.0-21.24) ...
  Removing linux-headers-4.13.0-21 (4.13.0-21.24) ...
  Removing linux-image-extra-4.13.0-21-generic (4.13.0-21.24) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
4.13.0-21-generic /boot/vmlinuz-4.13.0-21-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-21-generic 
/boot/vmlinuz-4.13.0-21-generic

  
  dkms process is stuck and does not end

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2144 F pulseaudio
mvh2739 F pulseaudio
   /dev/snd/controlC0:  gdm2144 F pulseaudio
mvh2739 F pulseaudio
  Date: Wed Jan 31 14:41:24 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-04-15 (291 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6540
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic 
root=UUID=aa4075ec-5629-4eb4-9fa7-6e90dd0cd274 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  SourcePackage: linux
  Title: package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to artful on 2018-01-01 (29 days ago)
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0725FP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd02/02/2015:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-02-01 Thread Oliver R.

I can confirm the issue on a ThinkPad T420 running Linux Mint 18.3 Xfce.
4.13.0-32 freezes
4.10.0-42 works

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

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

Status in linux package in Ubuntu:
  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 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

with the one from 4.12/zesty-remote,

~$ uname -a
Linux flimsy 4.12.0-041200-generic #201802011737 SMP Thu Feb 1 17:43:21 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

it works.

I get the impression this is not good news.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

Ah, ok then, I'll give it a try.

(there haven't been linux-image-extra debs in all 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/1745342

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

Do you need the headers file for something?  To test the kernel, you
should only have to install the linux-image and linux-image-extra .debs.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

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

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

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in linux-azure source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  New

Bug description:
  Some SSD drives made by LiteOn can crash the kernel due to bad
  drivers.  A fix for this issue has been submitted upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  
  At a high level the root cause of this problem is that the device only 
supports commands with a transfer size up to 512KB.  This worked fine with 
older versions of Linux but newer versions are attempting commands with a 
transfer size of 1280KB which is problematic for this device (LITEON EP1-KB480)

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

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

[Kernel-packages] [Bug 1744988] Re: time drifting on linux-hwe kernels

SRU request for Artful submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089834.html

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

Title:
  time drifting on linux-hwe kernels

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

Bug description:
  == SRU Justification ==
  We observe NTP time drift on two servers running hwe kernels in Xenial. A few 
weeks ago we wanted to switch from 4.4 to 4.10. When rebooting the servers to 
the 4.10 kernel we were seeing a big time offset within minutes after booting. 
Despite running ntpd, it would not keep up and the offset stayed and kept 
growing over t.

  Rebooting back into the 4.4 at the time we immediatly noticed the time
  stayed normal. Over time I have tested about a dozen versions making
  me think something has been introduced in kernel 4.10 that makes the
  clock go out of sync.

  So what do we observe?

  After 1 min uptime:
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
  *ntp4.bit.nl .PPS.1 u5   1670.497  100.084  81.382
  +ntp1.bit.nl 193.0.0.229  2 u8   1670.603   93.241  70.643
  +ntp2.bit.nl 193.67.79.2022 u8   1670.582   93.218  70.674
  +ntp3.bit.nl 193.79.237.142 u9   1670.781   90.488  70.574

  A couple of minutes later (and also hours/days, the offset just keeps
  growing over time)

   remote   refid  st t when poll reach   delay   offset  jitter
  ==
  *ntp4.bit.nl .PPS.1 u   13   16  3770.447  400.198 151.335
  +ntp1.bit.nl 193.0.0.229  2 u   13   16  3770.313  400.561 151.339
  +ntp2.bit.nl 193.67.79.2022 u   13   16  3770.517  400.445 151.398
  +ntp3.bit.nl 193.79.237.142 u   12   16  3770.934  402.013 151.384

  As mentioned I tested about a dozen of kernels and I thought I got it
  pinpointed to a specific release when the drifting got introduced,
  4.10rc1. Below the test results of the kernels I have tested up till
  today:

  Tested: 4.4.0-112-generic: not affected
  Tested: 4.8.0-41-generic: not affected
  Tested: 4.8.0-58-generic : not affected
  Tested: 4.9.0 mainline: not affected
  Tested: 4.9.66 mainline: not affected
  Tested: 4.10-rc1 mainline: affected
  Tested: 4.10 mainline: affected
  Tested: 4.10.0-38-generic: affected
  Tested: 4.10.0-40-generic: affected
  Tested: 4.13.0-16-generic: affected
  Tested: 4.13.0-31-generic: affected
  Tested: 4.14.3 mainline: affected
  Tested: 4.15-rc1 mainline: affected

  When I was about to file this bugreport about an hour ago I noticed
  4.15-rc9 was present and thought I gave it a go to make sure I really
  tested the latest version. And while running it over an hour now it
  stable.

  Mostl likely the following from the changelog is related the issue we
  are having:

  Len Brown (3):
    x86/tsc: Future-proof native_calibrate_tsc()
    x86/tsc: Fix erroneous TSC rate on Skylake Xeon
    x86/tsc: Print tsc_khz, when it differs from cpu_khz

  Both servers that are having issues on our side our equipped with the
  following cpu:

  Cpu Model (from /proc/cpuinfo)
  vendor_id : GenuineIntel
  cpu family: 6
  model : 85
  model name: Intel(R) Xeon(R) Gold 6136 CPU @ 3.00GHz

  Standard information as requested:
  1:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  2:
  root@bit-host6:~# apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
    Installed: 4.13.0.31.51
    Candidate: 4.13.0.31.51

  3: Stable time

  4: A big time offset

  == Fixes ==
  da4ae6c4a0b8 ("x86/tsc: Future-proof native_calibrate_tsc()")
  b51120309348 ("x86/tsc: Fix erroneous TSC rate on Skylake Xeon")
  4b5b2127238e ("x86/tsc: Print tsc_khz, when it differs from cpu_khz")

  == Regression Potential ==
  Low.  These three commits fix an existing regression.  They were also cc'd to 
  stable so have had addition upstream review.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

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

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

[Kernel-packages] [Bug 1743053] Re: libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089837.html

** Description changed:

- Some SSD drives made by LiteOn can crash the kernel due to bad drivers.
- A fix for this issue has been submitted upstream:
- 
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes
+ == SRU Justification ==
+ Some SSD drives made by LiteOn can crash the kernel due to bad drivers. This 
is a
+ regression introduced by commit e0edc8c54646.  This regression is fixed by 
mainline
+ commit db5ff909798, which was added to mailine in v4.15-rc9.
+ 
+ This commit has already been added to Bionic via upstream stable udpates.  
Xenial
+ also needs this fix because it recieved the regression introducing commit 
e0edc8c54646
+ via the 4.4.48 stable updates(See bug lp1663657).
+ 
+ 
+ == Fix ==
+ commit db5ff909798ef0099004ad50a0ff5fde92426fd1
+ Author: Xinyu Lin 
+ Date:   Sun Dec 17 20:13:39 2017 +0800
+ 
+ libata: apply MAX_SEC_1024 to all LITEON EP1 series devices
+ 
+ == Regression Potential ==
+ Low.  This commit was also cc'd to upstream stable to fix a regression, so it
+ received extra upstream review.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ == Original Bug Description ==
+ Some SSD drives made by LiteOn can crash the kernel due to bad drivers.  A 
fix for this issue has been submitted upstream: 
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes
  
  LITEON EP1 has the same timeout issues as CX1 series devices.
  
  Revert max_sectors to the value of 1024.
  
  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP devices")'
  
  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org
  
- 
- At a high level the root cause of this problem is that the device only 
supports commands with a transfer size up to 512KB.  This worked fine with 
older versions of Linux but newer versions are attempting commands with a 
transfer size of 1280KB which is problematic for this device (LITEON EP1-KB480)
+ At a high level the root cause of this problem is that the device only
+ supports commands with a transfer size up to 512KB.  This worked fine
+ with older versions of Linux but newer versions are attempting commands
+ with a transfer size of 1280KB which is problematic for this device
+ (LITEON EP1-KB480)

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

Title:
  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in linux-azure source package in Artful:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-azure source package in Bionic:
  New

Bug description:
  == SRU Justification ==
  Some SSD drives made by LiteOn can crash the kernel due to bad drivers. This 
is a
  regression introduced by commit e0edc8c54646.  This regression is fixed by 
mainline
  commit db5ff909798, which was added to mailine in v4.15-rc9.

  This commit has already been added to Bionic via upstream stable udpates.  
Xenial
  also needs this fix because it recieved the regression introducing commit 
e0edc8c54646
  via the 4.4.48 stable updates(See bug lp1663657).

  
  == Fix ==
  commit db5ff909798ef0099004ad50a0ff5fde92426fd1
  Author: Xinyu Lin 
  Date:   Sun Dec 17 20:13:39 2017 +0800

  libata: apply MAX_SEC_1024 to all LITEON EP1 series devices

  == Regression Potential ==
  Low.  This commit was also cc'd to upstream stable to fix a regression, so it
  received extra upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  == Original Bug Description ==
  Some SSD drives made by LiteOn can crash the kernel due to bad drivers.  A 
fix for this issue has been submitted upstream: 
https://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git/commit/?h=for-4.15-fixes

  LITEON EP1 has the same timeout issues as CX1 series devices.

  Revert max_sectors to the value of 1024.

  'e0edc8c54646 ("libata: apply MAX_SEC_1024 to all CX1-JB*-HP
  devices")'

  Signed-off-by: Xinyu Lin 
  Signed-off-by: Tejun Heo 
  Cc: sta...@vger.kernel.org

  At a high level the root cause of this problem is that the device only
  supports commands with a transfer size up to 512KB.  This worked fine
  with older versions of Linux but

[Kernel-packages] [Bug 1744988] Re: time drifting on linux-hwe kernels

** Description changed:

- We observe NTP time drift on two servers running hwe kernels in Xenial.
- A few weeks ago we wanted to switch from 4.4 to 4.10. When rebooting the
- servers to the 4.10 kernel we were seeing a big time offset within
- minutes after booting. Despite running ntpd, it would not keep up and
- the offset stayed and kept growing over t.
+ == SRU Justification ==
+ We observe NTP time drift on two servers running hwe kernels in Xenial. A few 
weeks ago we wanted to switch from 4.4 to 4.10. When rebooting the servers to 
the 4.10 kernel we were seeing a big time offset within minutes after booting. 
Despite running ntpd, it would not keep up and the offset stayed and kept 
growing over t.
  
  Rebooting back into the 4.4 at the time we immediatly noticed the time
  stayed normal. Over time I have tested about a dozen versions making me
  think something has been introduced in kernel 4.10 that makes the clock
  go out of sync.
  
  So what do we observe?
  
  After 1 min uptime:
-  remote   refid  st t when poll reach   delay   offset  jitter
+  remote   refid  st t when poll reach   delay   offset  jitter
  ==
  *ntp4.bit.nl .PPS.1 u5   1670.497  100.084  81.382
  +ntp1.bit.nl 193.0.0.229  2 u8   1670.603   93.241  70.643
  +ntp2.bit.nl 193.67.79.2022 u8   1670.582   93.218  70.674
  +ntp3.bit.nl 193.79.237.142 u9   1670.781   90.488  70.574
  
  A couple of minutes later (and also hours/days, the offset just keeps
  growing over time)
  
-  remote   refid  st t when poll reach   delay   offset  jitter
+  remote   refid  st t when poll reach   delay   offset  jitter
  ==
  *ntp4.bit.nl .PPS.1 u   13   16  3770.447  400.198 151.335
  +ntp1.bit.nl 193.0.0.229  2 u   13   16  3770.313  400.561 151.339
  +ntp2.bit.nl 193.67.79.2022 u   13   16  3770.517  400.445 151.398
  +ntp3.bit.nl 193.79.237.142 u   12   16  3770.934  402.013 151.384
  
  As mentioned I tested about a dozen of kernels and I thought I got it
  pinpointed to a specific release when the drifting got introduced,
  4.10rc1. Below the test results of the kernels I have tested up till
  today:
  
  Tested: 4.4.0-112-generic: not affected
  Tested: 4.8.0-41-generic: not affected
  Tested: 4.8.0-58-generic : not affected
  Tested: 4.9.0 mainline: not affected
  Tested: 4.9.66 mainline: not affected
  Tested: 4.10-rc1 mainline: affected
  Tested: 4.10 mainline: affected
  Tested: 4.10.0-38-generic: affected
  Tested: 4.10.0-40-generic: affected
  Tested: 4.13.0-16-generic: affected
  Tested: 4.13.0-31-generic: affected
  Tested: 4.14.3 mainline: affected
  Tested: 4.15-rc1 mainline: affected
  
  When I was about to file this bugreport about an hour ago I noticed
  4.15-rc9 was present and thought I gave it a go to make sure I really
  tested the latest version. And while running it over an hour now it
  stable.
  
  Mostl likely the following from the changelog is related the issue we
  are having:
  
  Len Brown (3):
-   x86/tsc: Future-proof native_calibrate_tsc()
-   x86/tsc: Fix erroneous TSC rate on Skylake Xeon
-   x86/tsc: Print tsc_khz, when it differs from cpu_khz
+   x86/tsc: Future-proof native_calibrate_tsc()
+   x86/tsc: Fix erroneous TSC rate on Skylake Xeon
+   x86/tsc: Print tsc_khz, when it differs from cpu_khz
  
  Both servers that are having issues on our side our equipped with the
  following cpu:
  
  Cpu Model (from /proc/cpuinfo)
  vendor_id : GenuineIntel
  cpu family: 6
  model : 85
  model name: Intel(R) Xeon(R) Gold 6136 CPU @ 3.00GHz
  
  Standard information as requested:
  1:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  
- 2: 
+ 2:
  root@bit-host6:~# apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
-   Installed: 4.13.0.31.51
-   Candidate: 4.13.0.31.51
+   Installed: 4.13.0.31.51
+   Candidate: 4.13.0.31.51
  
  3: Stable time
  
  4: A big time offset
+ 
+ == Fixes ==
+ da4ae6c4a0b8 ("x86/tsc: Future-proof native_calibrate_tsc()")
+ b51120309348 ("x86/tsc: Fix erroneous TSC rate on Skylake Xeon")
+ 4b5b2127238e ("x86/tsc: Print tsc_khz, when it differs from cpu_khz")
+ 
+ == Regression Potential ==
+ Low.  These three commits fix an existing regression.  They were also cc'd to 
+ stable so have had addition upstream review.
+ 
+ == Test Case ==
+ A test kernel was built with these patches and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.

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

[Kernel-packages] [Bug 1744988] Re: time drifting on linux-hwe kernels

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

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

Title:
  time drifting on linux-hwe kernels

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

Bug description:
  We observe NTP time drift on two servers running hwe kernels in
  Xenial. A few weeks ago we wanted to switch from 4.4 to 4.10. When
  rebooting the servers to the 4.10 kernel we were seeing a big time
  offset within minutes after booting. Despite running ntpd, it would
  not keep up and the offset stayed and kept growing over t.

  Rebooting back into the 4.4 at the time we immediatly noticed the time
  stayed normal. Over time I have tested about a dozen versions making
  me think something has been introduced in kernel 4.10 that makes the
  clock go out of sync.

  So what do we observe?

  After 1 min uptime:
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
  *ntp4.bit.nl .PPS.1 u5   1670.497  100.084  81.382
  +ntp1.bit.nl 193.0.0.229  2 u8   1670.603   93.241  70.643
  +ntp2.bit.nl 193.67.79.2022 u8   1670.582   93.218  70.674
  +ntp3.bit.nl 193.79.237.142 u9   1670.781   90.488  70.574

  A couple of minutes later (and also hours/days, the offset just keeps
  growing over time)

   remote   refid  st t when poll reach   delay   offset  jitter
  ==
  *ntp4.bit.nl .PPS.1 u   13   16  3770.447  400.198 151.335
  +ntp1.bit.nl 193.0.0.229  2 u   13   16  3770.313  400.561 151.339
  +ntp2.bit.nl 193.67.79.2022 u   13   16  3770.517  400.445 151.398
  +ntp3.bit.nl 193.79.237.142 u   12   16  3770.934  402.013 151.384

  As mentioned I tested about a dozen of kernels and I thought I got it
  pinpointed to a specific release when the drifting got introduced,
  4.10rc1. Below the test results of the kernels I have tested up till
  today:

  Tested: 4.4.0-112-generic: not affected
  Tested: 4.8.0-41-generic: not affected
  Tested: 4.8.0-58-generic : not affected
  Tested: 4.9.0 mainline: not affected
  Tested: 4.9.66 mainline: not affected
  Tested: 4.10-rc1 mainline: affected
  Tested: 4.10 mainline: affected
  Tested: 4.10.0-38-generic: affected
  Tested: 4.10.0-40-generic: affected
  Tested: 4.13.0-16-generic: affected
  Tested: 4.13.0-31-generic: affected
  Tested: 4.14.3 mainline: affected
  Tested: 4.15-rc1 mainline: affected

  When I was about to file this bugreport about an hour ago I noticed
  4.15-rc9 was present and thought I gave it a go to make sure I really
  tested the latest version. And while running it over an hour now it
  stable.

  Mostl likely the following from the changelog is related the issue we
  are having:

  Len Brown (3):
x86/tsc: Future-proof native_calibrate_tsc()
x86/tsc: Fix erroneous TSC rate on Skylake Xeon
x86/tsc: Print tsc_khz, when it differs from cpu_khz

  Both servers that are having issues on our side our equipped with the
  following cpu:

  Cpu Model (from /proc/cpuinfo)
  vendor_id : GenuineIntel
  cpu family: 6
  model : 85
  model name: Intel(R) Xeon(R) Gold 6136 CPU @ 3.00GHz

  Standard information as requested:
  1:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  2: 
  root@bit-host6:~# apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
Installed: 4.13.0.31.51
Candidate: 4.13.0.31.51

  3: Stable time

  4: A big time offset

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

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

[Kernel-packages] [Bug 1746771] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1746771/+attachment/5047017/+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/1746771

Title:
  black background drop-down menu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1745508] Re: Please backport vmd suspend/resume patches to 16.04 hwe

Submitted Artful SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089829.html

** Description changed:

- Can you please backport VMD suspend/resume fixes from 4.14 to current
- 4.13 HWE?
+ == SRU Justification ==
+ 
+ This bug was opened to request commit e2b1820bd5d0 be backported from 4.14 to
+ the 4.13 kernel in Artful.  Without this patch, servers with VMD enabled 
+ run into issues suspending and resuming.
+ 
+ Commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f is in mainline as of
+ v4.14-rc1.
+ 
  
  [Fixes]
  commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f
  Author: Scott Bauer 
  Date:   Fri Aug 11 14:54:32 2017 -0600
- PCI: vmd: Free up IRQs on suspend path
+ PCI: vmd: Free up IRQs on suspend path
  
- [Impact] 
+ [Impact]
  Without this patch, servers with VMD enabled may run into issues suspending 
and resuming
  
  [Test Case]
  Typically this manifests by having many other devices having acquired IRQ 
resources competing with VMD. Without the patch, the server may fail to suspend 
when it can't move the IRQs to core 0 because of the lack of IRQs available on 
core 0.
  
- [Regression Potential] 
+ [Regression Potential]
  Low. This only affects one component of one arch and affects the non-typical 
use-case of suspending a server

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

Title:
  Please backport vmd suspend/resume patches to 16.04 hwe

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

Bug description:
  == SRU Justification ==

  This bug was opened to request commit e2b1820bd5d0 be backported from 4.14 to
  the 4.13 kernel in Artful.  Without this patch, servers with VMD enabled 
  run into issues suspending and resuming.

  Commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f is in mainline as of
  v4.14-rc1.


  [Fixes]
  commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f
  Author: Scott Bauer 
  Date:   Fri Aug 11 14:54:32 2017 -0600
  PCI: vmd: Free up IRQs on suspend path

  [Impact]
  Without this patch, servers with VMD enabled may run into issues suspending 
and resuming

  [Test Case]
  Typically this manifests by having many other devices having acquired IRQ 
resources competing with VMD. Without the patch, the server may fail to suspend 
when it can't move the IRQs to core 0 because of the lack of IRQs available on 
core 0.

  [Regression Potential]
  Low. This only affects one component of one arch and affects the non-typical 
use-case of suspending a server

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

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

[Kernel-packages] [Bug 1746771] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1746771/+attachment/5047016/+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/1746771

Title:
  black background drop-down menu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1746771] Re: black background drop-down menu

apport information

** Description changed:

  The internal drop-down menu for each program is unavailable because the
  text is only visible when I go above the mouse pointer.
  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency
  
  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: i386
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-11-08 (450 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
+ NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
+ Package: linux (not installed)
+ Tags:  xenial
+ Uname: Linux 4.4.113-0404113-lowlatency i686
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1746771/+attachment/5047015/+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/1746771

Title:
  black background drop-down menu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

The linux-headers deb seems to be truncated in that one.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746771] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1746771/+attachment/5047013/+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/1746771

Title:
  black background drop-down menu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1746771] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1746771/+attachment/5047014/+files/ProcEnviron.txt

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

Title:
  black background drop-down menu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1746771] Re: black background drop-down menu

apport information

** Tags added: apport-collected

** Description changed:

  The internal drop-down menu for each program is unavailable because the
  text is only visible when I go above the mouse pointer.
  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency
  
  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: i386
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-11-08 (450 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
+ NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
+ Package: linux (not installed)
+ Tags:  xenial
+ Uname: Linux 4.4.113-0404113-lowlatency i686
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1746771/+attachment/5047012/+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/1746771

Title:
  black background drop-down menu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-11-08 (450 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.113-0404113-lowlatency i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

Can you give the following kernel a try:
http://kernel.ubuntu.com/~jsalisbury/lp1745342/4.12/zesty-remote

It's the exact same tree as the last 4.12 kernel.  If it works, that
probably means the bug was introduced by a config change.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1742772] Re: powerpc: flush L1D on return to use

2018-02-01 Thread Stefan Bader

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

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

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Stefan Bader (smb)

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

Title:
  powerpc: flush L1D on return to use

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

Bug description:
  powerpc: flush L1D on return to use

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

Hmm, ok. I'm using a fit remote to artful for that build.  Let me try
building the kernel using Zesty or Xenial remote.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

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

apport-collect 1746771

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

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

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

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

** Tags added: xenial

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

Title:
  black background drop-down menu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png

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

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

[Kernel-packages] [Bug 1746771] [NEW] black background drop-down menu

Public bug reported:

The internal drop-down menu for each program is unavailable because the
text is only visible when I go above the mouse pointer.

lsb_release -a
LSB Version:
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial
kernel: 4.4.113-0404113-lowlatency

OpenGL version string: 4.5.0 NVIDIA 384.111
medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
https://i.imgur.com/VNKlTkq.png
https://i.imgur.com/sBIVQho.png
https://i.imgur.com/6FdYPcj.png
https://i.imgur.com/1RGXOlM.png

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

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

Title:
  black background drop-down menu

Status in linux package in Ubuntu:
  New

Bug description:
  The internal drop-down menu for each program is unavailable because
  the text is only visible when I go above the mouse pointer.

  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-ia32:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-ia32:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  kernel: 4.4.113-0404113-lowlatency

  OpenGL version string: 4.5.0 NVIDIA 384.111
  medium version: 17.2.4-0Ubuntu1 ~ 16.04.4
  The very confusing operation - the menu items are not visible! - It was most 
likely that the mesa package was upgraded at the end of January.
  https://i.imgur.com/VNKlTkq.png
  https://i.imgur.com/sBIVQho.png
  https://i.imgur.com/6FdYPcj.png
  https://i.imgur.com/1RGXOlM.png

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

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

[Kernel-packages] [Bug 1745508] Re: Please backport vmd suspend/resume patches to 16.04 hwe

2018-02-01 Thread Jonathan Derrick

Hi Joseph

Sorry for the delay. Everything in this lp looks good with your kernel.

Thanks again!

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

Title:
  Please backport vmd suspend/resume patches to 16.04 hwe

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

Bug description:
  Can you please backport VMD suspend/resume fixes from 4.14 to current
  4.13 HWE?

  [Fixes]
  commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f
  Author: Scott Bauer 
  Date:   Fri Aug 11 14:54:32 2017 -0600
  PCI: vmd: Free up IRQs on suspend path

  [Impact] 
  Without this patch, servers with VMD enabled may run into issues suspending 
and resuming

  [Test Case]
  Typically this manifests by having many other devices having acquired IRQ 
resources competing with VMD. Without the patch, the server may fail to suspend 
when it can't move the IRQs to core 0 because of the lack of IRQs available on 
core 0.

  [Regression Potential] 
  Low. This only affects one component of one arch and affects the non-typical 
use-case of suspending a server

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

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

[Kernel-packages] [Bug 1743908] Re: MODSIGN: Couldn't get UEFI db list

2018-02-01 Thread Wellington Uemura

Thank you.

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

Title:
  MODSIGN: Couldn't get UEFI db list

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel is having problem loading or validating certificates. Looking
  over the internet looks like this is a kernel issue.

  Patchs from other distro:
  https://bugzilla.redhat.com/show_bug.cgi?id=1497559
  - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch
  - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch
  - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch

  
  [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: 
ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734'
  [1.203352] Couldn't get size: 0x800e
  [1.203354] MODSIGN: Couldn't get UEFI db list
  [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate 
Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys 
keyring
  [1.205102] Couldn't get size: 0x800e
  [1.205103] MODSIGN: Couldn't get UEFI dbx list

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wellington   1429 F pulseaudio
   /dev/snd/pcmC1D3p:   wellington   1429 F...m pulseaudio
   /dev/snd/controlC1:  wellington   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 22:37:13 2018
  HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e
  InstallationDate: Installed on 2018-01-16 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD5 R5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5R5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1743908] Re: MODSIGN: Couldn't get UEFI db list

2018-02-01 Thread Wellington Uemura

v4.13 final, all good!

[1.485360] Loaded X.509 cert 'Build time autogenerated kernel key:
2977791a6bc138cb597bcddff841bb4e6c0cdbe0'

Fixed.

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

Title:
  MODSIGN: Couldn't get UEFI db list

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel is having problem loading or validating certificates. Looking
  over the internet looks like this is a kernel issue.

  Patchs from other distro:
  https://bugzilla.redhat.com/show_bug.cgi?id=1497559
  - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch
  - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch
  - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch

  
  [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: 
ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734'
  [1.203352] Couldn't get size: 0x800e
  [1.203354] MODSIGN: Couldn't get UEFI db list
  [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate 
Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys 
keyring
  [1.205102] Couldn't get size: 0x800e
  [1.205103] MODSIGN: Couldn't get UEFI dbx list

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wellington   1429 F pulseaudio
   /dev/snd/pcmC1D3p:   wellington   1429 F...m pulseaudio
   /dev/snd/controlC1:  wellington   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 22:37:13 2018
  HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e
  InstallationDate: Installed on 2018-01-16 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IwConfig:
   lono wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD5 R5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5R5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1579918] Re: Smart Card Reader BCM 5880 with kernel 4.2

2018-02-01 Thread Christopher M. Penalver

Karl Hill, the quickest way to confirm for your hardware is backup your 
install, temporarily install Windows via either:
http://www.dell.com/support/home/us/en/19/drivers/osiso/recoverytool/WT64A
https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool

and test the firmware update. This would be the most helpful for folks
who have exactly the same hardware as you do.

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

Title:
  Smart Card Reader BCM 5880 with kernel 4.2

Status in linux package in Ubuntu:
  Expired

Bug description:
  Native to Ubuntu 14.04 and 16.04 (kernel 4.2.0) on Dell Precision 7510
  with Broadcom 5880 (internal card reader). Card reads successfully
  from SCRx31 USB reader (external). Card also works on kernel 3.13.0
  (Dell Latitude E6430, 14.04) with same Broadcom 5880 reader.

  snippet from syslog:

  May 1 19:06:41 m-Precision pcscd: eventhandler.c:313:EHStatusHandlerThread() 
Error communicating to: Broadcom Corp 5880 [Contacted SmartCard] 
(0123456789ABCD) 00 00
  May 1 19:06:46 m-Precision kernel: [15276.197331] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision kernel: [15276.426405] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision kernel: [15276.442649] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision kernel: [15276.465888] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?
  May 1 19:06:46 m-Precision pcscd: commands.c:1456:CCID_Receive() Can't read 
all data (54 out of 92 expected)
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:214:t1_transceive() 
fatal: transmit/receive failed
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:46 m-Precision pcscd: openct/proto-t1.c:170:t1_transceive() T=1 
state machine is DEAD. Reset the card first.
  May 1 19:06:46 m-Precision pcscd: ifdwrapper.c:527:IFDTransmit() Card not 
transacted: 612
  May 1 19:06:46 m-Precision pcscd: winscard.c:1612:SCardTransmit() Card not 
transacted: 0x80100016
  May 1 19:06:47 m-Precision pcscd: ccid_usb.c:790:ReadUSB() read failed (1/2): 
-8 Resource temporarily unavailable
  May 1 19:06:47 m-Precision pcscd: ifdwrapper.c:348:IFDStatusICC() Card not 
transacted: 612
  May 1 19:06:47 m-Precision pcscd: eventhandler.c:313:EHStatusHandlerThread() 
Error communicating to: Broadcom Corp 5880 [Contacted SmartCard] 
(0123456789ABCD) 00 00
  May 1 19:06:52 m-Precision kernel: [15281.960976] xhci_hcd :00:14.0: WARN 
Event TRB for slot 1 ep 4 with no TDs queued?

  The above cycles on syslog roughly every second until card is removed.

  pcsc_scan shows card as alternating between successfully read to card
  reader not available, also on the roughly 1 sec interval.

  ---
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  grumpy 2207 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:28b8 Sunplus Innovation Technology Inc.
   Bus 001 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic.efi.signed 
root=UUID=62ed5a52-92de-456c-8a4b-433666572702 ro quiet splash

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

2018-02-01 Thread Yasmin Beatriz Alves da Silva

Tested this new build and they're good. You can use my IBM email address
that's fine :-)

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

Title:
  spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe
  kernel

Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in qemu source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * Xenial with HWE kernel (matching new relesaes) and qemu without cloud
 archive (not matching new releases) could trigger hypercalls that are 
 not supported in xenials-qemu.

   * There is no "real" case other than kvm tests yet to trigger it yet, but 
 it is an easy and well contained fix, so we might fix proactively.

  [Test Case]

1. deploy xenial + HWE kernel on a ppc64el box
2. sudo apt-get install qemu-kvm -y
3. git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
4. cd kvm-unit-tests
5. ./configure --endian=little; make
6. sudo ppc64_cpu --smt=off
7. sudo ./run_tests -v

  [Regression Potential]

   * The changes are all upstream since a long time now (lowering the risk 
 of silly mistakes)
   * The changes are isolated to ppc, so in the worst case only this arch 
 should regress.
   * We implement new hcalls, so if anything there might be a regression if 
 software expected them to fail, but now breaks by them working (don't 
 think so given the nature of these hcalls).

  [Other Info]
   
   * n/a

  ---

  kernel: 4.10.0-33.37~16.04.1

  I think this issue was introduced by the old qemu version (similar
  issue was spotted on Xenial before), will need to investigate this
  further.

  qemu-system-ppc64 -machine pseries,accel=kvm -bios powerpc/boot_rom.bin 
-display none -serial stdio -kernel powerpc/spapr_hcall.elf -smp 1
  FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x
  FAIL: hypercall: h_set_sprg0: sprg0 = 0x41a588
  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

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

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

[Kernel-packages] [Bug 1745007] Re: Support cppc-cpufreq driver on ThunderX2 systems

2018-02-01 Thread Seth Forshee

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

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

Title:
  Support cppc-cpufreq driver on ThunderX2 systems

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

Bug description:
  [Impact]
  The cppc-cpufreq driver fails to initialize on ThunderX2 systems, which is 
used to communicate power configuration to firmware.

  [Test Case]
  sudo modprobe cppc-cpufreq || echo "Fail"

  [Regression Risk]
  The fix consists of clean cherry-picks from upstream that are restricted to a 
single driver. Regressions would therefore be restricted to platforms that 
support ACPI CPPC power management.

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

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

[Kernel-packages] [Bug 1746164] Re: [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio and network skip on Wifi activity)

In my case this configuration results in
 - a bluetooth hangs, but only if the WiFi is far away and only about once 
every minute. But the connection losses I experienced with btcoex_enable=0 
bt_ant_diversity=0 are nearly gone.
 - and changing the file in mplayer causes a short audio hang.

With btcoex_enable=1 and bt_ant_diversity=1 I don't get any connection
losses, audio runs smoothly without hangs and switching from a file to
another works smoothly, too.

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

Title:
  [ath9k] Enable Bluetooth-Wifi coexistence by default (bluetooth audio
  and network skip on Wifi activity)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  By default BT audio works fine on Ubuntu - if there is no WiFi active:
  Both work on the same frequency range, 2 WiFi channel is about 20
  Bluetooth Channels wide and every time a WiFi package is sent
  bluetooth risks a packet loss.

  Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the
  following content:

  options ath9k btcoex_enable=1 bt_ant_diversity=1

  resolves the problem and drastically increases bluetooth throughput
  for all other use cases (bluetooth networking that doesn't drop every
  time the WiFi probes something, lower latency Bluetooth HIDs.

  We should ship things in a way that they work out-of-the-box => I am
  all for providing this file with Ubuntu, possibly with Bluez.

  In the case of my laptop btcoex_enable=1 would already do the trick.

  
  Technical background:
   - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex
   - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.46-0ubuntu4
  Uname: Linux 4.15.0-041500rc9-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 30 06:40:12 2018
  EcryptfsInUse: Yes
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Aspire S7-391
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency 
root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ 
acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable 
nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd 
intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Storm
  dmi.board.vendor: Acer
  dmi.board.version: V2.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09:
  dmi.product.family: ChiefRiver System
  dmi.product.name: Aspire S7-391
  dmi.product.version: V2.09
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:94:23:49:1B:BC  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:688 acl:0 sco:0 events:49 errors:0
TX bytes:3167 acl:0 sco:0 commands:49 errors:0

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

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

[Kernel-packages] [Bug 1735826] Re: SMART Board Pen not supported

2018-02-01 Thread civ4ever

I tested it with the latest 4.15 kernel - without success.

** Tags removed: kernel-da-key
** Tags added: kernel-bug-exists-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/1735826

Title:
  SMART Board Pen not supported

Status in libinput:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 | xserver-xorg-input-libinput 0.25.0-0ubuntu1

  I'm using Ubuntu 17.10 with a SMART Board 6000 (an interactive whiteboard) in 
school.
  The touch-screen of the board works fine. Unfortunately there are a lot of 
problems with the pen:
  - The pen isn't recognized as a device on Wayland. You can't either use it as 
a touch-device or write with it.
  - The same problem occurs when xserver-xorg-input-libinput is used on X.Org.
  After I replaced libinput with the old xserver-xorg-input-evdev/-synaptics 
the pen was recognized and I could use it. The output of xinput confirms this:

  xinput [libinput installed]:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SMART Technologies SMART IFPid=9[slave  pointer 
 (2)]
  ⎜   ↳ ETPS/2 Elantech Touchpadid=14   [slave  pointer 
 (2)]

  xinput [evdev/synaptics installed]:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SMART Technologies SMART IFP Penid=9[slave  pointer 
 (2)]
  ⎜   ↳ SMART Technologies SMART IFPid=10   [slave  pointer 
 (2)]
  ⎜   ↳ SMART Technologies SMART IFP UNKNOWNid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SMART Technologies SMART IFP UNKNOWNid=12   [slave  pointer 
 (2)]
  ⎜   ↳ SMART Technologies SMART IFP UNKNOWNid=13   [slave  pointer 
 (2)]
  ⎜   ↳ SMART Technologies SMART IFP UNKNOWNid=14   [slave  pointer 
 (2)]
  ⎜   ↳ ETPS/2 Elantech Touchpadid=18   [slave  pointer  (2)]

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

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

[Kernel-packages] [Bug 1746357] Re: Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

2018-02-01 Thread Christopher M. Penalver

Bib:

1) Regarding the error message:
gfxboot.c32: not a COM32R Image boot:

One may type the following and hit enter:
live

This is a known issue from LP#1325801.

2) The video capture unfortunately didn't reveal anything useful. Could
you please capture the boot following
https://wiki.ubuntu.com/DebuggingKernelBoot ?

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

Title:
  Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Boot looping since initial 14.04 install. I recently upgraded to
  16.04.3 and fell in the same issue as upgrade overwrote my
  /etc/default/grub without prompting, AFAIR.

  WORKAROUND: When using free radeon driver:
  nomodeset

  or:
  radeon.dpm=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  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/controlC1:  fab1962 F pulseaudio
   /dev/snd/controlC0:  fab1962 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 30 22:46:13 2018
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1284 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro radeon.dpm=0
  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.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-01-16 (14 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1746357] Re: Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

2018-02-01 Thread Christopher M. Penalver

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

Title:
  Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Boot looping since initial 14.04 install. I recently upgraded to
  16.04.3 and fell in the same issue as upgrade overwrote my
  /etc/default/grub without prompting, AFAIR.

  WORKAROUND: When using free radeon driver:
  nomodeset

  or:
  radeon.dpm=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  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/controlC1:  fab1962 F pulseaudio
   /dev/snd/controlC0:  fab1962 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 30 22:46:13 2018
  HibernationDevice: RESUME=UUID=66392631-7c4f-4773-8614-4c5ea0913890
  InstallationDate: Installed on 2014-07-26 (1284 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.

   eth1  no wireless extensions.
  MachineType: MSI MS-7721
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=09ecdff0-44fe-437e-8063-deabc6feb00e ro radeon.dpm=0
  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.15
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2018-01-16 (14 days ago)
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V30.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 6.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 6.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV30.6:bd12/15/2014:svnMSI:pnMS-7721:pvr6.0:rvnMSI:rnA88XM-E35(MS-7721):rvr6.0:cvnMSI:ct3:cvr6.0:
  dmi.product.name: MS-7721
  dmi.product.version: 6.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1103493] Re: kexec is broken

2018-02-01 Thread Launchpad Bug Tracker

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

** Changed in: kexec-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  kexec is broken

Status in kexec-tools package in Ubuntu:
  Confirmed

Bug description:
  After loading the new kernel wit kexec -l, the man page says to run
  kexec without any arguments and it will do a clean shutdown, then
  kexec.  Running kexec without any arguments results in:

  "No kernel specified" followed by help text.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

With the kernel in the 4.12 directory,

~$ uname -a
Linux flimsy 4.12.0-041200-generic #201802011529 SMP Thu Feb 1 15:34:08 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

the touchscreen did not work.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

Thanks for testing my kernel.  It sounds like the Debian bug may be
different or that the bug might be outside of the kernel.

It was originally reported that this bug was a regression.  Can those
that can reproduce this bug try the following kernel:

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

>From that page, select your arch under the "Builds" section.  Then
install the linux-image and linux-image-extra .deb packages.

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

Title:
  linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-
  image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-
  image-3.13.0-121-generic | Regression: many user-space apps crashing

Status in LibreOffice:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux package in Debian:
  Fix Released

Bug description:
  Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)

  linux-image-4.4.0-81-generic appears to contain a regression, probably
  related to the CVE-2017-1000364 fix backport / patch.

  Using this kernel, the Oracle Java browser plugin always crashes
  during stack-related actions on initialization. This means, the plugin
  completely stopped working.

  
  It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to 
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also 
contains a fix for CVE-2017-1000364.


  uname -a:

  > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
  UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
  well as Iceweasel / Firefox/3.5.16 in a chroot.

  Using linux-image-4.4.0-81-generic it crashes in all combinations
  while with both other kernels it works.

  
  I was not able to obtain any detailed crash information from Firefox 51.0.1, 
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace 
which shows the relation to stack operations performed by the plugin, even 
without proper debug symbols:

  
  > (gdb) bt full
  > #0  0x7fa06d805307 in _expand_stack_to(unsigned char*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #1  0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, 
unsigned char*) ()
  >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #2  0x7fa06d80cf0b in JVM_handle_linux_signal () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #3  0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from 
/opt/java-8-oracle/jre/lib/amd64/server/libjvm.so
  > No symbol table info available.
  > #4  

  
  I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6.

  
  The crash will be triggered by any applet, for example the test applet at:

  * https://java.com/en/download/installed8.jsp

  
  I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow 
apparently does not allow me to use apport to report this bug:

  > $ LANG= apport-cli linux-image-4.4.0-81-generic
  > 
  > *** Collecting problem information
  > 
  > The collected information can be sent to the developers to improve the
  > application. This might take a few minutes.
  > .
  > 
  > *** Problem in linux-image-4.4.0-81-generic
  > 
  > The problem cannot be reported:
  > 
  > This is not an official KDE package. Please remove any third party package 
and try again.

  If someone can tell me how to get apport working for this package, I
  can use it to collect additional information, but (unfortunately?) the
  problem should be fairly easy to reproduce...

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+subscriptions

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

[Kernel-packages] [Bug 1746713] Re: Dialogic ISDN card vendor-driver kernel-module fails to load after meltdown/spectre kernel versions were released