[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-04-11 Thread Kai-Heng Feng
Can you try latest mainline kernel again? At least the issue is gone for
me with latest mainline kernel.

I'll do a reverse bisect to find the commit that fixes the issue, and
backport the patch to Bionic's kernel.

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that the network stopped working on my desktop after
  I've suspended the system and woke it up. On dmesg there are messages
  like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity: 
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
 Mixer name : 'VIA VT1818S'
 Components : 'HDA:11060440,18492818,0010'
 Controls  : 40
 Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 7
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  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.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr: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/1752772/+subscriptions

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

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

2018-04-11 Thread bugproxy
--- Comment From chetj...@in.ibm.com 2018-04-12 01:24 EDT---
(In reply to comment #18)
> Can you see if the bug happens with and of these mainline kernels?  We can
> perform a kernel bisect if we can narrow down to the last good kernel
> version and first bad one:
>
> v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/
> v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/
> v4.15-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc4/
> v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/
>
> You don't have to test every kernel, just up until the kernel that first has
> this bug.
>
> Thanks in advance!

We need to make progress in testing other firmware and guest issues. We
will come back to this later.

Meanwhile, the problem happened again today with the reboot and we tried
to collect the vmcore using 'X', but it did not collect. Indira, pls add
those details.

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = 

[Kernel-packages] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

2018-04-11 Thread Kai-Heng Feng
** Also affects: linux-oem (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/1762693

Title:
  No network with e1000e driver on 4.13.0-38-generic

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New

Bug description:
  When my computer boots with the most recent kernel 4.13.0-38-generic,
  I don't have a working network connection. ethtool reports that my
  network interface doesn't have a connection:

  martin@dogmeat ~ % cat ethtool.txt 
  Settings for eth0:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full 
  100baseT/Half 100baseT/Full 
  1000baseT/Full 
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full 
  100baseT/Half 100baseT/Full 
  1000baseT/Full 
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: Unknown!
  Duplex: Unknown! (255)
  Port: Twisted Pair
  PHYAD: 2
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: Unknown (auto)
  Supports Wake-on: pumbg
  Wake-on: g
  Current message level: 0x0007 (7)
 drv probe link
  Link detected: no

  dmesg contains suspicious e1000e error messages:

  martin@dogmeat ~ % tail -n 40 dmesg.txt
  [   20.211715] Could not find valid key in user session keyring for sig 
specified in mount option: [459a10809c211381]
  [   20.211716] One or more global auth toks could not properly register; rc = 
[-2]
  [   20.211717] Error parsing options; rc = [-2]
  [   25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   51.244686] ahci :00:17.0: port does not support device sleep
  [   56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   88.938939] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   93.021350] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   99.163603] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  104.038668] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  110.048532] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  110.191137] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  115.022823] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  120.800524] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  120.910537] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  125.019509] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  131.040530] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  131.164741] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  136.039268] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  142.048536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  142.186891] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  147.038361] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500

  Everything works fine when I boot Linux 4.13.0-37-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: 

[Kernel-packages] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

2018-04-11 Thread Kai-Heng Feng
** Tags added: originate-from-1762323 somerville

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

Title:
  No network with e1000e driver on 4.13.0-38-generic

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

Bug description:
  When my computer boots with the most recent kernel 4.13.0-38-generic,
  I don't have a working network connection. ethtool reports that my
  network interface doesn't have a connection:

  martin@dogmeat ~ % cat ethtool.txt 
  Settings for eth0:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full 
  100baseT/Half 100baseT/Full 
  1000baseT/Full 
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full 
  100baseT/Half 100baseT/Full 
  1000baseT/Full 
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: Unknown!
  Duplex: Unknown! (255)
  Port: Twisted Pair
  PHYAD: 2
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: Unknown (auto)
  Supports Wake-on: pumbg
  Wake-on: g
  Current message level: 0x0007 (7)
 drv probe link
  Link detected: no

  dmesg contains suspicious e1000e error messages:

  martin@dogmeat ~ % tail -n 40 dmesg.txt
  [   20.211715] Could not find valid key in user session keyring for sig 
specified in mount option: [459a10809c211381]
  [   20.211716] One or more global auth toks could not properly register; rc = 
[-2]
  [   20.211717] Error parsing options; rc = [-2]
  [   25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   51.244686] ahci :00:17.0: port does not support device sleep
  [   56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   88.938939] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   93.021350] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   99.163603] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  104.038668] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  110.048532] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  110.191137] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  115.022823] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  120.800524] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  120.910537] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  125.019509] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  131.040530] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  131.164741] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  136.039268] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  142.048536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  142.186891] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  147.038361] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500

  Everything works fine when I boot Linux 4.13.0-37-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"

2018-04-11 Thread Launchpad Bug Tracker
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Expired
Status in mesa package in Ubuntu:
  Expired

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  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.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to 

[Kernel-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"

2018-04-11 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after
  starting "EFI VGA"

Status in linux package in Ubuntu:
  Expired
Status in mesa package in Ubuntu:
  Expired

Bug description:
  Ubuntu 17.10.1 boots into a black screen with no display, when
  switching into "EFI VGA" during boot up.

  Modifying the boot menu to run in "text" mode, shows the last line as
  below, before losing all monitor output:

  "Switching to EFI VGA"

  The 15m DisplayPort cable shouldn't be a problem, but using a
  DisplayPort-to-DVI adapter and a 1m DVI cable works

  PC Specs

  CPU : Intel Core i9-7900X 4.3GHz 10-Core
  MBO : ASRock X299 Taichi
  RAM : Corsair Vengeance 32GB
  GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-02-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  eric   2029 F pulseaudio
   /dev/snd/controlC1:  eric   2029 F pulseaudio
   /dev/snd/pcmC0D0p:   eric   2029 F...m pulseaudio
   /dev/snd/controlC0:  eric   2029 F pulseaudio
  CurrentDesktop: GNOME
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff
  InstallationDate: Installed on 2018-02-05 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: mesa (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: X299 Taichi
  dmi.board.vendor: ASRock
  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.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr: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.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to

[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)

2018-04-11 Thread Gopal
#43~lp1745646TwoReverts is bad .http://paste.ubuntu.com/p/kfsgKdVMYW/

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

Title:
  Battery drains when laptop is off  (shutdown)

Status in Linux:
  Unknown
Status in acpi package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in acpi source package in Artful:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  I am using hp AY008tx laptop , and many other laptop users (HP) are also 
facing the same issue . The problem don't occur when i install windows 10 . 
Now, only ubuntu is installed.
  i am using latest bios insyde20 rev 5.(latest)
  WOL disabled and no usb device connected
  checked my battery .
  it don't happen when i remove battery and plug it again after shutdown.
  tried laptop_mode_tools and tpl too

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 26 22:50:53 2018
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopal  2391 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 0a5c:216d Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.58
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1763156] Re: Bluetooth doesn't reconnect to my headsetup post resume from sleep

2018-04-11 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1759628 ***
https://bugs.launchpad.net/bugs/1759628

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


** This bug has been marked a duplicate of bug 1759628
bluez regression: Bluetooth audio fails to reconnect after resume

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

Title:
  Bluetooth doesn't reconnect to my headsetup post resume from sleep

Status in bluez package in Ubuntu:
  New

Bug description:
  Steps to repro:

  * Cold boot the laptop
  * Pair it with bluetooth headset
  * Listen to music
  * Turn off the headset or turn off the bluetooth on the laptop
  * Play music, sound comes out of the laptop speakers
  * Turn on the headset back on or the bluetooth on the laptop
  * Headset reconnects with the laptop and audio plays from the headset

  -- all the above is expected --

  * Suspend the laptop
  * wait a minute or two for the headset to power down
  * Resume the laptop
  * Turn on the bluetooth headeset
  * It doesn't automatically reconnect to the laptop (not expected behaviour)
  * Launch Gnome Settings and select Bluetooth and force the headset to connect
  * It connects for 2 seconds then disconnects (not expected behaviour)

  The only to get the headset to reconnect again is by restarting the
  bluetooth.service using systemctl.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr 11 15:28:28 2018
  InstallationDate: Installed on 2018-04-03 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=1f5de204-14c1-4ab7-b29c-880bbcd6f1d9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:34:41:D4:8F:36  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:19284 acl:106 sco:0 events:2607 errors:0
TX bytes:605507 acl:103 sco:0 commands:2473 errors:0

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

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


[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

2018-04-11 Thread David Henningsson
Kernel 4.15rc2+78d9b048446c3c0a83313444fb706f8f3bccdae7: Black screen.

Note: I installed the linux-image-...-generic deb only as the header
ones seemed to require libssl1.1...?

Anyway, I did some research on my own as well.

First, I had a look at the commits between 4.15rc2 and 4.15rc3. The only
one I could see being relevant is this one:

commit a703c55004e1c5076d57e43771b3e7796ea0
Author: Daniel Vetter 
Date:   Mon Dec 4 21:48:18 2017 +0100

drm: safely free connectors from connector_iter

...it seems relevant because the error I get is "Cannot find any crtc or
sizes", and the code emitting this error message (in
drivers/gpu/drm/drm_fb_helper.c) deals with connectors.

This commit is then referenced in other commits later on as being
required to fix, but since 4.16 is "black screen" too those fixes seems
not have helped here.

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

Title:
  Black screen on 18.04 + AMD RX460

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

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

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

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


[Kernel-packages] [Bug 1685712] Re: [Featire] CNL: Enable RAPL support

2018-04-11 Thread quanxian
yes, follow process between Canonical and Intel
If patches are available, it can be opened to public.

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

Title:
  [Featire] CNL: Enable RAPL support

Status in intel:
  Incomplete
Status in intel trunk series:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  enable RAPL on Cannon Lake Client Platforms

  Kernel Release: 4.17
  Target Release: 18.04

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

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


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

2018-04-11 Thread Vi+
My YEPO 737A with recent 4.16.1-041601-lowlatency kernel under Mint 18.3
still needs suspend in order to run touchpad smoothly after it (I
expected 4.16 release will fix it finally, but it's 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/1728244

Title:
  Touchpad stops working after reboot on Apollo Lake

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

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

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

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

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

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

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


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

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

apport-collect 1763202

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

Title:
  Lenovo X1 Carbon 6th Gen. HDMI not working for external monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an X1 Carbon 6th Gen. (Intel Core i7 8th Gen, 16 GB RAM, 512 GB
  SSD).

  When I try to attach an external monitor via an HDMI cable the monitor
  receives no signal. Similarly, when I use the Thunderbold dock and
  attach two monitors (one via HDMI, one with DisplayPort) only the
  monitor attached with DisplayPort works; the monitor attached with
  HDMI stays black.

  This made me think if this is really a bug in the software. I saw
  people describing this issue with Windows installed; the solution was
  to hit a special key combination. Unfortunately, the multimedia keys
  all not all functional, specifically the F7 key, which seems to meant
  for "activate external monitor", has no function.

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

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


[Kernel-packages] [Bug 1763202] [NEW] Lenovo X1 Carbon 6th Gen. HDMI not working for external monitor

2018-04-11 Thread Peter Bittner
Public bug reported:

I have an X1 Carbon 6th Gen. (Intel Core i7 8th Gen, 16 GB RAM, 512 GB
SSD).

When I try to attach an external monitor via an HDMI cable the monitor
receives no signal. Similarly, when I use the Thunderbold dock and
attach two monitors (one via HDMI, one with DisplayPort) only the
monitor attached with DisplayPort works; the monitor attached with HDMI
stays black.

This made me think if this is really a bug in the software. I saw people
describing this issue with Windows installed; the solution was to hit a
special key combination. Unfortunately, the multimedia keys all not all
functional, specifically the F7 key, which seems to meant for "activate
external monitor", has no function.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1763202

Title:
  Lenovo X1 Carbon 6th Gen. HDMI not working for external monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an X1 Carbon 6th Gen. (Intel Core i7 8th Gen, 16 GB RAM, 512 GB
  SSD).

  When I try to attach an external monitor via an HDMI cable the monitor
  receives no signal. Similarly, when I use the Thunderbold dock and
  attach two monitors (one via HDMI, one with DisplayPort) only the
  monitor attached with DisplayPort works; the monitor attached with
  HDMI stays black.

  This made me think if this is really a bug in the software. I saw
  people describing this issue with Windows installed; the solution was
  to hit a special key combination. Unfortunately, the multimedia keys
  all not all functional, specifically the F7 key, which seems to meant
  for "activate external monitor", has no function.

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

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


[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

2018-04-11 Thread Peter Bittner
I have an X1 Carbon 6th Generation (Core i7 8th Gen, 16 GB RAM, 512 GB
SSD) and it behaves like described in the first comments above.

Specifically, when I close the notebook it somewhat goes in standby (or
not really, I'm not sure), the red dot blinks but underneath the
notebook gets hot within a few minutes. And sometimes, not always, it
freezes (or stays frozen) instead of waking up when I open the notebook
again.

I'm running 18.04 Bionic (development branch).

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

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  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/linux/+bug/1708043/+subscriptions

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


[Kernel-packages] [Bug 1752437] Re: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

2018-04-11 Thread Quentin Iorio
This problem also affects me.  I have a similar model HP ENVY x360
15-bq0xx

Linux fireball-x360 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Same gpio error:

[0.989418] amd_gpio AMD0030:00: Failed to get gpio IRQ.
[0.989500] amd_gpio: probe of AMD0030:00 failed with error -22

Entire dmesg is attached.

I would be more than willing to help in debugging.

Kind regards


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/+attachment/5111358/+files/dmesg.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/1752437

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1761179] Re: linux-aws: 4.15.0-1003.3 -proposed tracker

2018-04-11 Thread Brad Figg
The package has been published and the bug is being set to Fix Released


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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1761177
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-phase:Released
+ kernel-phase-changed:Wednesday, 11. April 2018 22:01 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1761177
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-phase:Released
- kernel-phase-changed:Wednesday, 11. April 2018 22:01 UTC

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

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

Title:
  linux-aws: 4.15.0-1003.3 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Bionic:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1761177
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

-- 
Mailing list: https://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 1762468] Re: Cryptoswap not working in Bionic

2018-04-11 Thread Martin D. Weinberg
BTW, I _do_ realize that you want a starting point for bisection; I'm
sorry this is turning out so messy.


On 04/11/2018 05:51 PM, Martin Weinberg wrote:
> The first kernel on that list that exhibits the bug is the first one:
> 4.14 Final.  Recall: the bug results in a full up hang.  The disk stops
> swapping (it's audible).   I can reboot with sysctl SUB however.
>
> I then tested 4.13.0-36 from the Ubuntu 17.10 respoitory, followed by
> 4.11.12-041112-generic from mainline.  Both had the bug.
>
> I also tested each of these without cryptswap (i.e. normal swap) and
> they did not hang.  The system ground to a halt, but I could hear the
> disk swapping and the process eventually completed.
>
> I then booted an 16.04 live usb which has kernel 4.10.  I had to make a
> cryptswap using cryptsetup on the swap partition of the hard disk, to
> test it.   But this one worked! The behavior was a bit different that
> more recent kernels: after allocating 6 GB of the 10 GB that I
> requested, the system invoked the oom-killer on the process.  However,
> it did not hang.
>
> I then grabbed 4.10.1-041001-generic from mainline and tested it.  This
> worked the same as the live usb.  So 4.10 does not have the bug,
> although the oom-killer is invoked to kill the process grabbing the memory.
>
> I have an older machine with an SSD.  This does not exhibit the bug on
> Ubuntu 17.10 running 4.13.0-36.  However, this disk is _fast_ (Samsung
> EVO), so I'm guessing that there is some tuning problem, maybe, in how
> the kernel handles swap speed vs memory allocation requests???  I really
> don't know.
>
> --M
>
>
> On 04/11/2018 11:18 AM, Joseph Salisbury wrote:
>> I'd like to perform a bisect to figure out what commit caused this
>> regression. We need to identify the earliest kernel where the issue
>> started happening as well as the latest kernel that did not have this
>> issue.
>>
>> Can you test the following kernels and report back? We are looking for
>> the first kernel version that exhibits this bug:
>>
>> v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/
>> v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/
>> v4.15-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc4/
>> v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/
>>
>> You don't have to test every kernel, just up until the kernel that first
>> has this bug.
>>
>> Thanks in advance!
>>
>> ** Tags added: performing-bisect
>>

-- 
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039

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

Title:
  Cryptoswap not working in Bionic

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

Bug description:
  I have cryptoswap set up both with the 2 GB default swap file and an 8
  GB swap partition with 8 GB of ram.  However, the system does not use
  this swap when it should.  For example, if I run a little test code
  which attempts to allocate 10 GB of memory in 1 GB chuncks, the system
  hangs with no obvious use of swap.  E.g. running top shows no swap use
  before the hang.  However, if I replace cryptoswap by standard swap,
  it works as expected: allocates the requested memory and exits, using
  swap.  Of course, my disk is slow, so this takes some time but it does
  work.

  I originally noticed this problem when compiling a very large
  application.  The system would hang on ld.  I've checked hardware
  using memtest and stress.  No problems.  This took me days to track
  down but I'm 99% certain now that the problem is with cryptoswap.  If
  I compile with cryptoswap: hang.  If I compile with standard swap: no
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  weinberg   2425 F pulseaudio
   /dev/snd/controlC0:  weinberg   2425 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 11:57:23 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113
  InstallationDate: Installed on 2018-03-12 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  MachineType: LENOVO 20ARA0S100
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  

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

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

apport-collect 1763189

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: 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/1763189

Title:
  kernel 4.15 breaks nouveau on Lenovo P50

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to linux 4.15.0-13-generic, the system freezes at boot,
  apparently when the nouveau driver tries to start.  The console is
  still in 80x25 text mode at this point.  No panic or error message is
  displayed, only unrelated log messages (screenshot attached).

  Booting in recovery mode is possible and allows X11 to start using the
  vesa driver.

  nouveau still works fine when booting an older kernel
  (4.13.0-36-generic) so this problem seems to be specific to 4.15.0.

  ProblemType: Bug
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Apr 11 17:25:27 2018
  Dependencies:
   adduser 3.113+nmu3ubuntu4
   apt 1.2.26
   apt-utils 1.2.26
   busybox-initramfs 1:1.22.0-15ubuntu1
   coreutils 8.25-2ubuntu3~16.04
   cpio 2.11+dfsg-5ubuntu1
   debconf 1.5.58ubuntu1
   debianutils 4.7
   dpkg 1.18.4ubuntu1.4
   e2fslibs 1.42.13-1ubuntu1
   e2fsprogs 1.42.13-1ubuntu1
   gcc-5-base 5.4.0-6ubuntu1~16.04.9
   gcc-6-base 6.0.1-0ubuntu1
   gettext-base 0.19.7-2ubuntu3
   gnupg 1.4.20-1ubuntu3.1
   gpgv 1.4.20-1ubuntu3.1
   grub-common 2.02~beta2-36ubuntu3.17
   grub-gfxpayload-lists 0.7
   grub-pc 2.02~beta2-36ubuntu3.17
   grub-pc-bin 2.02~beta2-36ubuntu3.17
   grub2-common 2.02~beta2-36ubuntu3.17
   init-system-helpers 1.29ubuntu4
   initramfs-tools 0.122ubuntu8.11
   initramfs-tools-bin 0.122ubuntu8.11
   initramfs-tools-core 0.122ubuntu8.11
   initscripts 2.88dsf-59.3ubuntu2
   insserv 1.14.0-5ubuntu3
   klibc-utils 2.0.4-8ubuntu1.16.04.4
   kmod 22-1ubuntu5
   libacl1 2.2.52-3
   libapt-inst2.0 1.2.26
   libapt-pkg5.0 1.2.26
   libasprintf0v5 0.19.7-2ubuntu3
   libattr1 1:2.4.47-2
   libaudit-common 1:2.4.5-1ubuntu2.1
   libaudit1 1:2.4.5-1ubuntu2.1
   libblkid1 2.27.1-6ubuntu3.4
   libbz2-1.0 1.0.6-8
   libc6 2.23-0ubuntu10
   libcomerr2 1.42.13-1ubuntu1
   libdb5.3 5.3.28-11ubuntu0.1
   libdevmapper1.02.1 2:1.02.110-1ubuntu10
   libfdisk1 2.27.1-6ubuntu3.4
   libfreetype6 2.6.1-0.1ubuntu2.3
   libfuse2 2.9.4-1ubuntu3.1
   libgcc1 1:6.0.1-0ubuntu1
   libgcrypt20 1.6.5-2ubuntu0.4
   libgpg-error0 1.21-2ubuntu1
   libgpm2 1.20.4-6.1
   libklibc 2.0.4-8ubuntu1.16.04.4
   libkmod2 22-1ubuntu5
   liblz4-1 0.0~r131-2ubuntu2
   liblzma5 5.1.1alpha+20120614-2ubuntu2
   libmount1 2.27.1-6ubuntu3.4
   libncurses5 6.0+20160213-1ubuntu1
   libncursesw5 6.0+20160213-1ubuntu1
   libpam-modules 1.1.8-3.2ubuntu2
   libpam-modules-bin 1.1.8-3.2ubuntu2
   libpam0g 1.1.8-3.2ubuntu2
   libpcre3 2:8.38-3.1
   libpng12-0 1.2.54-1ubuntu1
   libprocps4 2:3.3.10-4ubuntu2.3
   libreadline6 6.3-8ubuntu2
   libselinux1 2.4-3build2
   libsemanage-common 2.3-1build3
   libsemanage1 2.3-1build3
   libsepol1 2.4-2
   libsmartcols1 2.27.1-6ubuntu3.4
   libss2 1.42.13-1ubuntu1
   libstdc++6 5.4.0-6ubuntu1~16.04.9
   libsystemd0 229-4ubuntu21.2
   libtinfo5 6.0+20160213-1ubuntu1
   libudev1 229-4ubuntu21.2
   libusb-0.1-4 2:0.1.12-28
   libustr-1.0-1 1.0.4-5
   libuuid1 2.27.1-6ubuntu3.4
   linux-base 4.0ubuntu1
   lsb-base 9.20160110ubuntu0.2
   mount 2.27.1-6ubuntu3.4
   multiarch-support 2.23-0ubuntu10
   os-prober 1.70ubuntu3.3
   passwd 1:4.2-3.1ubuntu5.3
   perl-base 5.22.1-9ubuntu0.2
   procps 2:3.3.10-4ubuntu2.3
   psmisc 22.21-2.1build1
   readline-common 6.3-8ubuntu2
   sensible-utils 0.0.9ubuntu0.16.04.1
   sysv-rc 2.88dsf-59.3ubuntu2
   sysvinit-utils 2.88dsf-59.3ubuntu2
   tar 1.28-2.1ubuntu0.1
   ubuntu-keyring 2012.05.19
   ucf 3.0036
   udev 229-4ubuntu21.2
   util-linux 2.27.1-6ubuntu3.4
   uuid-runtime 2.27.1-6ubuntu3.4
   zlib1g 1:1.2.8.dfsg-2ubuntu4.1
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-02-01 (434 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   -- Logs begin at Wed 2018-04-11 17:25:19 EDT, end at Wed 2018-04-11 17:25:22 
EDT. --
   Apr 11 17:25:19 hostname kernel: Intel Spectre v2 broken microcode detected; 
disabling Speculation Control
   Apr 11 17:25:19 hostname kernel: ENERGY_PERF_BIAS: Set to 'normal', was 
'performance'
   Apr 11 17:25:19 hostname kernel: ENERGY_PERF_BIAS: View and update with 

Re: [Kernel-packages] [Bug 1762468] Re: Cryptoswap not working in Bionic

2018-04-11 Thread Martin D. Weinberg
The first kernel on that list that exhibits the bug is the first one:
4.14 Final.  Recall: the bug results in a full up hang.  The disk stops
swapping (it's audible).   I can reboot with sysctl SUB however.

I then tested 4.13.0-36 from the Ubuntu 17.10 respoitory, followed by
4.11.12-041112-generic from mainline.  Both had the bug.

I also tested each of these without cryptswap (i.e. normal swap) and
they did not hang.  The system ground to a halt, but I could hear the
disk swapping and the process eventually completed.

I then booted an 16.04 live usb which has kernel 4.10.  I had to make a
cryptswap using cryptsetup on the swap partition of the hard disk, to
test it.   But this one worked! The behavior was a bit different that
more recent kernels: after allocating 6 GB of the 10 GB that I
requested, the system invoked the oom-killer on the process.  However,
it did not hang.

I then grabbed 4.10.1-041001-generic from mainline and tested it.  This
worked the same as the live usb.  So 4.10 does not have the bug,
although the oom-killer is invoked to kill the process grabbing the memory.

I have an older machine with an SSD.  This does not exhibit the bug on
Ubuntu 17.10 running 4.13.0-36.  However, this disk is _fast_ (Samsung
EVO), so I'm guessing that there is some tuning problem, maybe, in how
the kernel handles swap speed vs memory allocation requests???  I really
don't know.

--M


On 04/11/2018 11:18 AM, Joseph Salisbury wrote:
> I'd like to perform a bisect to figure out what commit caused this
> regression. We need to identify the earliest kernel where the issue
> started happening as well as the latest kernel that did not have this
> issue.
>
> Can you test the following kernels and report back? We are looking for
> the first kernel version that exhibits this bug:
>
> v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/
> v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/
> v4.15-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc4/
> v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/
>
> You don't have to test every kernel, just up until the kernel that first
> has this bug.
>
> Thanks in advance!
>
> ** Tags added: performing-bisect
>

-- 
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039

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

Title:
  Cryptoswap not working in Bionic

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

Bug description:
  I have cryptoswap set up both with the 2 GB default swap file and an 8
  GB swap partition with 8 GB of ram.  However, the system does not use
  this swap when it should.  For example, if I run a little test code
  which attempts to allocate 10 GB of memory in 1 GB chuncks, the system
  hangs with no obvious use of swap.  E.g. running top shows no swap use
  before the hang.  However, if I replace cryptoswap by standard swap,
  it works as expected: allocates the requested memory and exits, using
  swap.  Of course, my disk is slow, so this takes some time but it does
  work.

  I originally noticed this problem when compiling a very large
  application.  The system would hang on ld.  I've checked hardware
  using memtest and stress.  No problems.  This took me days to track
  down but I'm 99% certain now that the problem is with cryptoswap.  If
  I compile with cryptoswap: hang.  If I compile with standard swap: no
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  weinberg   2425 F pulseaudio
   /dev/snd/controlC0:  weinberg   2425 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 11:57:23 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113
  InstallationDate: Installed on 2018-03-12 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  MachineType: LENOVO 20ARA0S100
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No 

[Kernel-packages] [Bug 1762928] Re: [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

2018-04-11 Thread bugproxy
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1804

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

Title:
  [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

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

Bug description:
  ---Problem Description---
  tm_trap_test failed on P8 compat mode [16.04.04 daily build as well bionic ] 
guests on a P9 host running bionic final beta version.
   
  Contact Information = srikanth/bssrika...@in.ibm.com 
   
  ---uname output---

  16.04.04 Guest running in P8compat mode:

  Linux guest 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:18:22 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  18.04 guest running in P8compat mode:
  Linux ubuntu 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Log into P9 Ubuntu 18.04 host, take console of guest 
`srikanth_ubuntu160404`
  2. Run TM selftests
  git clone --depth 1 https://github.com/torvalds/linux.git;cd 
linux/tools/testing/selftests/powerpc/;git log --oneline -1;make;make -C tm 
run_tests

  We will observe one of the tm tests failing, mentioned below:

  selftests: tm-trap
  
  test: tm_trap_test
  tags: git_version:c18bb39
  Little-Endian machine detected. Checking if endianness flips inadvertently on 
trap in TM... yes!
  failure: tm_trap_test
  not ok 1..11 selftests:  tm-trap [FAIL]

  
  Expected result: All tm selftests should have been pass on the P8 compat 
guest.. giventhat we had TM workaround patches in latest Ubuntu BIONIC host 
kernel
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for srikanth/bssrika...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.


  == Comment: #2 - SRIKANTH AITHAL  - 2018-04-10
  01:32:00 ==

  
  == Comment: #3 - SRIKANTH AITHAL  - 2018-04-10 
01:33:41 ==

  
  == Comment: #4 - SRIKANTH AITHAL  - 2018-04-10 
01:34:02 ==

  
  Please pick 

   `1c200e63d055 ("powerpc/tm: Fix endianness flip on trap")`

  ie. the commit that the test was written for

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

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


[Kernel-packages] [Bug 1763189] [NEW] kernel 4.15 breaks nouveau on Lenovo P50

2018-04-11 Thread John Lindgren
Public bug reported:

After updating to linux 4.15.0-13-generic, the system freezes at boot,
apparently when the nouveau driver tries to start.  The console is still
in 80x25 text mode at this point.  No panic or error message is
displayed, only unrelated log messages (screenshot attached).

Booting in recovery mode is possible and allows X11 to start using the
vesa driver.

nouveau still works fine when booting an older kernel
(4.13.0-36-generic) so this problem seems to be specific to 4.15.0.

ProblemType: Bug
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Wed Apr 11 17:25:27 2018
Dependencies:
 adduser 3.113+nmu3ubuntu4
 apt 1.2.26
 apt-utils 1.2.26
 busybox-initramfs 1:1.22.0-15ubuntu1
 coreutils 8.25-2ubuntu3~16.04
 cpio 2.11+dfsg-5ubuntu1
 debconf 1.5.58ubuntu1
 debianutils 4.7
 dpkg 1.18.4ubuntu1.4
 e2fslibs 1.42.13-1ubuntu1
 e2fsprogs 1.42.13-1ubuntu1
 gcc-5-base 5.4.0-6ubuntu1~16.04.9
 gcc-6-base 6.0.1-0ubuntu1
 gettext-base 0.19.7-2ubuntu3
 gnupg 1.4.20-1ubuntu3.1
 gpgv 1.4.20-1ubuntu3.1
 grub-common 2.02~beta2-36ubuntu3.17
 grub-gfxpayload-lists 0.7
 grub-pc 2.02~beta2-36ubuntu3.17
 grub-pc-bin 2.02~beta2-36ubuntu3.17
 grub2-common 2.02~beta2-36ubuntu3.17
 init-system-helpers 1.29ubuntu4
 initramfs-tools 0.122ubuntu8.11
 initramfs-tools-bin 0.122ubuntu8.11
 initramfs-tools-core 0.122ubuntu8.11
 initscripts 2.88dsf-59.3ubuntu2
 insserv 1.14.0-5ubuntu3
 klibc-utils 2.0.4-8ubuntu1.16.04.4
 kmod 22-1ubuntu5
 libacl1 2.2.52-3
 libapt-inst2.0 1.2.26
 libapt-pkg5.0 1.2.26
 libasprintf0v5 0.19.7-2ubuntu3
 libattr1 1:2.4.47-2
 libaudit-common 1:2.4.5-1ubuntu2.1
 libaudit1 1:2.4.5-1ubuntu2.1
 libblkid1 2.27.1-6ubuntu3.4
 libbz2-1.0 1.0.6-8
 libc6 2.23-0ubuntu10
 libcomerr2 1.42.13-1ubuntu1
 libdb5.3 5.3.28-11ubuntu0.1
 libdevmapper1.02.1 2:1.02.110-1ubuntu10
 libfdisk1 2.27.1-6ubuntu3.4
 libfreetype6 2.6.1-0.1ubuntu2.3
 libfuse2 2.9.4-1ubuntu3.1
 libgcc1 1:6.0.1-0ubuntu1
 libgcrypt20 1.6.5-2ubuntu0.4
 libgpg-error0 1.21-2ubuntu1
 libgpm2 1.20.4-6.1
 libklibc 2.0.4-8ubuntu1.16.04.4
 libkmod2 22-1ubuntu5
 liblz4-1 0.0~r131-2ubuntu2
 liblzma5 5.1.1alpha+20120614-2ubuntu2
 libmount1 2.27.1-6ubuntu3.4
 libncurses5 6.0+20160213-1ubuntu1
 libncursesw5 6.0+20160213-1ubuntu1
 libpam-modules 1.1.8-3.2ubuntu2
 libpam-modules-bin 1.1.8-3.2ubuntu2
 libpam0g 1.1.8-3.2ubuntu2
 libpcre3 2:8.38-3.1
 libpng12-0 1.2.54-1ubuntu1
 libprocps4 2:3.3.10-4ubuntu2.3
 libreadline6 6.3-8ubuntu2
 libselinux1 2.4-3build2
 libsemanage-common 2.3-1build3
 libsemanage1 2.3-1build3
 libsepol1 2.4-2
 libsmartcols1 2.27.1-6ubuntu3.4
 libss2 1.42.13-1ubuntu1
 libstdc++6 5.4.0-6ubuntu1~16.04.9
 libsystemd0 229-4ubuntu21.2
 libtinfo5 6.0+20160213-1ubuntu1
 libudev1 229-4ubuntu21.2
 libusb-0.1-4 2:0.1.12-28
 libustr-1.0-1 1.0.4-5
 libuuid1 2.27.1-6ubuntu3.4
 linux-base 4.0ubuntu1
 lsb-base 9.20160110ubuntu0.2
 mount 2.27.1-6ubuntu3.4
 multiarch-support 2.23-0ubuntu10
 os-prober 1.70ubuntu3.3
 passwd 1:4.2-3.1ubuntu5.3
 perl-base 5.22.1-9ubuntu0.2
 procps 2:3.3.10-4ubuntu2.3
 psmisc 22.21-2.1build1
 readline-common 6.3-8ubuntu2
 sensible-utils 0.0.9ubuntu0.16.04.1
 sysv-rc 2.88dsf-59.3ubuntu2
 sysvinit-utils 2.88dsf-59.3ubuntu2
 tar 1.28-2.1ubuntu0.1
 ubuntu-keyring 2012.05.19
 ucf 3.0036
 udev 229-4ubuntu21.2
 util-linux 2.27.1-6ubuntu3.4
 uuid-runtime 2.27.1-6ubuntu3.4
 zlib1g 1:1.2.8.dfsg-2ubuntu4.1
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2017-02-01 (434 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
JournalErrors:
 -- Logs begin at Wed 2018-04-11 17:25:19 EDT, end at Wed 2018-04-11 17:25:22 
EDT. --
 Apr 11 17:25:19 hostname kernel: Intel Spectre v2 broken microcode detected; 
disabling Speculation Control
 Apr 11 17:25:19 hostname kernel: ENERGY_PERF_BIAS: Set to 'normal', was 
'performance'
 Apr 11 17:25:19 hostname kernel: ENERGY_PERF_BIAS: View and update with 
x86_energy_perf_policy(8)
 Apr 11 17:25:19 hostname kernel: resource sanity check: requesting [mem 
0xfed1-0xfed15fff], which spans more than pnp 00:01 [mem 
0xfed1-0xfed13fff]
 Apr 11 17:25:19 hostname kernel: caller snb_uncore_imc_init_box+0x6b/0xb0 
mapping multiple BARs
 Apr 11 17:25:19 hostname kernel: (NULL device *): hwmon_device_register() is 
deprecated. Please convert the driver to use hwmon_device_register_with_info().
 Apr 11 17:25:19 hostname kernel: usb: port power management may be unreliable
 Apr 11 17:25:19 hostname kernel: [Firmware Bug]: ACPI(PEGP) defines _DOD but 
not _DOS
 Apr 11 17:25:19 hostname kernel: acpi PNP0C14:01: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
 Apr 11 17:25:19 hostname kernel: acpi PNP0C14:02: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
 Apr 11 17:25:19 hostname kernel: ata4.00: supports DRM functions and may not 
be fully accessible
 Apr 11 17:25:19 hostname kernel: ata4.00: supports DRM functions and may not 
be fully accessible
 Apr 11 17:25:19 hostname 

[Kernel-packages] [Bug 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic

2018-04-11 Thread Lars Ehrhardt
*** This bug is a duplicate of bug 1759920 ***
https://bugs.launchpad.net/bugs/1759920

We can also confirm, that kernel image 4.15.0-15.16 boots on one of our
affected machines.

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

Title:
  System freezes when starting Xorg after installing linux-
  image-4.13.0-32-generic

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

Bug description:
  My laptop (Lenovo T440) freezes when starting Xorg (lightdm) only
  after installing the latest ubuntu kernel for 17.10, linux-
  image-4.13.0-32-generic.

  Am running Xorg instead of MIR due to MIR crashing when I initially
  upgraded from 17.04 to 17.10, but that's a different problem for a
  different day. It's been running with Xorg stably for at least 2-3
  months.

  If I boot with the previous kernel version on my /boot (linux-
  image-4.13.0-25-generic), everything works fine.

  If I boot with the latest mainline kernel from the Ubuntu mainline
  repo (4.15.0), everything works.

  Using grub's option to run "Recovery Mode" for the 4.13.0-32 kernel, I
  am able to use the CLI and access the encrypted root filesystem, which
  is how I generated the apport repo that's attached. It's only when
  telling it to continue Normal booting that it freezes, which is why I
  suspect the problem of being Xorg.

  When the system freezes, the fan starts to spin up. I cannot switch
  virtual consoles using CTRL-ALT-F{1-7}. CTRL-ALT-DEL pressed
  repeatedly doesn't do anything. To reboot, I have to hold the power
  button until the system powers off.

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

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


[Kernel-packages] [Bug 1757166] Re: linux-aws: 4.15.0-1002.2 -proposed tracker

2018-04-11 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1761179 ***
https://bugs.launchpad.net/bugs/1761179

This bug was fixed in the package linux-aws - 4.15.0-1003.3

---
linux-aws (4.15.0-1003.3) bionic; urgency=medium

  * linux-aws: 4.15.0-1003.3 -proposed tracker (LP: #1761179)


  [ Ubuntu: 4.15.0-15.16 ]

  * linux: 4.15.0-15.16 -proposed tracker (LP: #1761177)
  * FFe: Enable configuring resume offset via sysfs (LP: #1760106)
- PM / hibernate: Make passing hibernate offsets more friendly
  * /dev/bcache/by-uuid links not created after reboot (LP: #1729145)
- SAUCE: (no-up) bcache: decouple emitting a cached_dev CHANGE uevent
  * Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine
type(pseries-bionic) complaining "KVM implementation does not support
Transactional Memory, try cap-htm=off" (kvm) (LP: #1752026)
- powerpc: Use feature bit for RTC presence rather than timebase presence
- powerpc: Book E: Remove unused CPU_FTR_L2CSR bit
- powerpc: Free up CPU feature bits on 64-bit machines
- powerpc: Add CPU feature bits for TM bug workarounds on POWER9 v2.2
- powerpc/powernv: Provide a way to force a core into SMT4 mode
- KVM: PPC: Book3S HV: Work around transactional memory bugs in POWER9
- KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode
- KVM: PPC: Book3S HV: Work around TEXASR bug in fake suspend state
  * Important Kernel fixes to be backported for Power9 (kvm) (LP: #1758910)
- powerpc/mm: Fixup tlbie vs store ordering issue on POWER9
  * Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16
namespaces  (Bolt / NVMe) (LP: #1757497)
- powerpc/64s: Fix lost pending interrupt due to race causing lost update to
  irq_happened
  * fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module
failed to build (LP: #1760876)
- [Packaging] include the retpoline extractor in the headers

  [ Ubuntu: 4.15.0-14.15 ]

  * linux: 4.15.0-14.15 -proposed tracker (LP: #1760678)
  * [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor
(LP: #1758662)
- net/mlx4_en: Change default QoS settings
  * AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
(LP: #1759312)
- powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features
  * Bionic update to 4.15.15 stable release (LP: #1760585)
- net: dsa: Fix dsa_is_user_port() test inversion
- openvswitch: meter: fix the incorrect calculation of max delta_t
- qed: Fix MPA unalign flow in case header is split across two packets.
- tcp: purge write queue upon aborting the connection
- qed: Fix non TCP packets should be dropped on iWARP ll2 connection
- sysfs: symlink: export sysfs_create_link_nowarn()
- net: phy: relax error checking when creating sysfs link netdev->phydev
- devlink: Remove redundant free on error path
- macvlan: filter out unsupported feature flags
- net: ipv6: keep sk status consistent after datagram connect failure
- ipv6: old_dport should be a __be16 in __ip6_datagram_connect()
- ipv6: sr: fix NULL pointer dereference when setting encap source address
- ipv6: sr: fix scheduling in RCU when creating seg6 lwtunnel state
- mlxsw: spectrum_buffers: Set a minimum quota for CPU port traffic
- net: phy: Tell caller result of phy_change()
- ipv6: Reflect MTU changes on PMTU of exceptions for MTU-less routes
- net sched actions: return explicit error when tunnel_key mode is not
  specified
- ppp: avoid loop in xmit recursion detection code
- rhashtable: Fix rhlist duplicates insertion
- test_rhashtable: add test case for rhltable with duplicate objects
- kcm: lock lower socket in kcm_attach
- sch_netem: fix skb leak in netem_enqueue()
- ieee802154: 6lowpan: fix possible NULL deref in lowpan_device_event()
- net: use skb_to_full_sk() in skb_update_prio()
- net: Fix hlist corruptions in inet_evict_bucket()
- s390/qeth: free netdevice when removing a card
- s390/qeth: when thread completes, wake up all waiters
- s390/qeth: lock read device while queueing next buffer
- s390/qeth: on channel error, reject further cmd requests
- soc/fsl/qbman: fix issue in qman_delete_cgr_safe()
- dpaa_eth: fix error in dpaa_remove()
- dpaa_eth: remove duplicate initialization
- dpaa_eth: increment the RX dropped counter when needed
- dpaa_eth: remove duplicate increment of the tx_errors counter
- dccp: check sk for closed state in dccp_sendmsg()
- ipv6: fix access to non-linear packet in ndisc_fill_redirect_hdr_option()
- l2tp: do not accept arbitrary sockets
- net: ethernet: arc: Fix a potential memory leak if an optional regulator 
is
  deferred
- net: ethernet: ti: cpsw: add check for in-band mode setting with RGMII PHY
  interface
- net: fec: Fix unbalanced PM runtime calls
- net/iucv: Free memory obtained by kzalloc
- 

[Kernel-packages] [Bug 1761179] Re: linux-aws: 4.15.0-1003.3 -proposed tracker

2018-04-11 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 4.15.0-1003.3

---
linux-aws (4.15.0-1003.3) bionic; urgency=medium

  * linux-aws: 4.15.0-1003.3 -proposed tracker (LP: #1761179)


  [ Ubuntu: 4.15.0-15.16 ]

  * linux: 4.15.0-15.16 -proposed tracker (LP: #1761177)
  * FFe: Enable configuring resume offset via sysfs (LP: #1760106)
- PM / hibernate: Make passing hibernate offsets more friendly
  * /dev/bcache/by-uuid links not created after reboot (LP: #1729145)
- SAUCE: (no-up) bcache: decouple emitting a cached_dev CHANGE uevent
  * Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine
type(pseries-bionic) complaining "KVM implementation does not support
Transactional Memory, try cap-htm=off" (kvm) (LP: #1752026)
- powerpc: Use feature bit for RTC presence rather than timebase presence
- powerpc: Book E: Remove unused CPU_FTR_L2CSR bit
- powerpc: Free up CPU feature bits on 64-bit machines
- powerpc: Add CPU feature bits for TM bug workarounds on POWER9 v2.2
- powerpc/powernv: Provide a way to force a core into SMT4 mode
- KVM: PPC: Book3S HV: Work around transactional memory bugs in POWER9
- KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode
- KVM: PPC: Book3S HV: Work around TEXASR bug in fake suspend state
  * Important Kernel fixes to be backported for Power9 (kvm) (LP: #1758910)
- powerpc/mm: Fixup tlbie vs store ordering issue on POWER9
  * Ubuntu 18.04 - IO Hang on some namespaces when running HTX with 16
namespaces  (Bolt / NVMe) (LP: #1757497)
- powerpc/64s: Fix lost pending interrupt due to race causing lost update to
  irq_happened
  * fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module
failed to build (LP: #1760876)
- [Packaging] include the retpoline extractor in the headers

  [ Ubuntu: 4.15.0-14.15 ]

  * linux: 4.15.0-14.15 -proposed tracker (LP: #1760678)
  * [Bionic] mlx4 ETH - mlnx_qos failed when set some TC to vendor
(LP: #1758662)
- net/mlx4_en: Change default QoS settings
  * AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10
(LP: #1759312)
- powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features
  * Bionic update to 4.15.15 stable release (LP: #1760585)
- net: dsa: Fix dsa_is_user_port() test inversion
- openvswitch: meter: fix the incorrect calculation of max delta_t
- qed: Fix MPA unalign flow in case header is split across two packets.
- tcp: purge write queue upon aborting the connection
- qed: Fix non TCP packets should be dropped on iWARP ll2 connection
- sysfs: symlink: export sysfs_create_link_nowarn()
- net: phy: relax error checking when creating sysfs link netdev->phydev
- devlink: Remove redundant free on error path
- macvlan: filter out unsupported feature flags
- net: ipv6: keep sk status consistent after datagram connect failure
- ipv6: old_dport should be a __be16 in __ip6_datagram_connect()
- ipv6: sr: fix NULL pointer dereference when setting encap source address
- ipv6: sr: fix scheduling in RCU when creating seg6 lwtunnel state
- mlxsw: spectrum_buffers: Set a minimum quota for CPU port traffic
- net: phy: Tell caller result of phy_change()
- ipv6: Reflect MTU changes on PMTU of exceptions for MTU-less routes
- net sched actions: return explicit error when tunnel_key mode is not
  specified
- ppp: avoid loop in xmit recursion detection code
- rhashtable: Fix rhlist duplicates insertion
- test_rhashtable: add test case for rhltable with duplicate objects
- kcm: lock lower socket in kcm_attach
- sch_netem: fix skb leak in netem_enqueue()
- ieee802154: 6lowpan: fix possible NULL deref in lowpan_device_event()
- net: use skb_to_full_sk() in skb_update_prio()
- net: Fix hlist corruptions in inet_evict_bucket()
- s390/qeth: free netdevice when removing a card
- s390/qeth: when thread completes, wake up all waiters
- s390/qeth: lock read device while queueing next buffer
- s390/qeth: on channel error, reject further cmd requests
- soc/fsl/qbman: fix issue in qman_delete_cgr_safe()
- dpaa_eth: fix error in dpaa_remove()
- dpaa_eth: remove duplicate initialization
- dpaa_eth: increment the RX dropped counter when needed
- dpaa_eth: remove duplicate increment of the tx_errors counter
- dccp: check sk for closed state in dccp_sendmsg()
- ipv6: fix access to non-linear packet in ndisc_fill_redirect_hdr_option()
- l2tp: do not accept arbitrary sockets
- net: ethernet: arc: Fix a potential memory leak if an optional regulator 
is
  deferred
- net: ethernet: ti: cpsw: add check for in-band mode setting with RGMII PHY
  interface
- net: fec: Fix unbalanced PM runtime calls
- net/iucv: Free memory obtained by kzalloc
- netlink: avoid a double skb free in genlmsg_mcast()
- net: Only honor ifindex in IP_PKTINFO 

[Kernel-packages] [Bug 1756877] Re: Dell XPS 9530 (Nvidia GeForce GT 750M): Intermittent freeze when using nouveau

2018-04-11 Thread Luke Carrier
FYI I'm currently mitigating this using Bumblebee:

https://wiki.ubuntu.com/Bumblebee#Setup_for_14.04_and_later

I've not yet been able to get applications running against the discrete
chip, but since I'm now running with onboard Intel graphics the
stuttering is no longer an 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/1756877

Title:
  Dell XPS 9530 (Nvidia GeForce GT 750M): Intermittent freeze when using
  nouveau

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am on an Dell xps 9530 laptop and I had recently cleaned installed
  17.10. A few days back I decided to updated to 18.04 to check it out
  and report some bugs. The most annoying bug so far is the insane
  amount of input latency this update has brought with it to a degree
  that it makes it impossible to be productive. The issue is observable
  when using either the mouse or the keyboard. The mouse does not move
  immediately but it needs a second or two to register and start moving
  and even then at some point it freezes for half a second at some
  random point and then moves again. Also if I have two applications
  side by side and I try an move focus from one to the next at around
  the edges of each window the mouse freezes for a second and then
  moves. The keyboard freezes if it hasn't been used for a while and on
  the first keystroke will take a second to register and for a bonus you
  get the first keystorke repeated for around 15-30 times. So if you are
  trying to write "and" will become "aaand" or pressing
  "ctrl + T" in the browser will open not one but 20 tabs!

  I am reporting it here cause I am not sure what is causing all this
  latency (it could be libinput or something else entirely) but please
  try and fix this as soon as possible!!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 19 13:04:05 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-14 (32 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (3 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giannissc   2031 F pulseaudio
   /dev/snd/pcmC1D0p:   giannissc   2031 F...m pulseaudio
   /dev/snd/controlC1:  giannissc   2031 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=999e9885-dbd2-4a45-a45f-998e322f32dc
  InstallationDate: Installed on 2018-03-26 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
  MachineType: Dell Inc. XPS 15 9530
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  wayland-session bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

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

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


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

2018-04-11 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/1763177

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Playing lollypop while lollypop is scanning its library for the first
  time

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bertadmin   1522 F...m pulseaudio
   /dev/snd/controlC0:  bertadmin   1522 F pulseaudio
   /dev/snd/timer:  bertadmin   1522 f pulseaudio
  Date: Wed Apr 11 14:20:57 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: down_read_trylock+0x9/0x40 RSP: aa45c038fc80
  Failure: oops
  InstallationDate: Installed on 2018-03-11 (31 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=22835ac6-a7b5-4601-bd4b-a6c98e4df3fb ro quiet splash zwap.enabled=1
  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 
0008
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


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

2018-04-11 Thread BertN45
Public bug reported:

Playing lollypop while lollypop is scanning its library for the first
time

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   bertadmin   1522 F...m pulseaudio
 /dev/snd/controlC0:  bertadmin   1522 F pulseaudio
 /dev/snd/timer:  bertadmin   1522 f pulseaudio
Date: Wed Apr 11 14:20:57 2018
DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: down_read_trylock+0x9/0x40 RSP: aa45c038fc80
Failure: oops
InstallationDate: Installed on 2018-03-11 (31 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
IwConfig:
 enp0s3no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=22835ac6-a7b5-4601-bd4b-a6c98e4df3fb ro quiet splash zwap.enabled=1
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 0008
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-kerneloops bionic 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/1763177

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Playing lollypop while lollypop is scanning its library for the first
  time

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bertadmin   1522 F...m pulseaudio
   /dev/snd/controlC0:  bertadmin   1522 F pulseaudio
   /dev/snd/timer:  bertadmin   1522 f pulseaudio
  Date: Wed Apr 11 14:20:57 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: down_read_trylock+0x9/0x40 RSP: aa45c038fc80
  Failure: oops
  InstallationDate: Installed on 2018-03-11 (31 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=22835ac6-a7b5-4601-bd4b-a6c98e4df3fb ro quiet splash zwap.enabled=1
  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 
0008
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 

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

2018-04-11 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Playing lollypop while lollypop is scanning its library for the first
  time

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bertadmin   1522 F...m pulseaudio
   /dev/snd/controlC0:  bertadmin   1522 F pulseaudio
   /dev/snd/timer:  bertadmin   1522 f pulseaudio
  Date: Wed Apr 11 14:20:57 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: down_read_trylock+0x9/0x40 RSP: aa45c038fc80
  Failure: oops
  InstallationDate: Installed on 2018-03-11 (31 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=22835ac6-a7b5-4601-bd4b-a6c98e4df3fb ro quiet splash zwap.enabled=1
  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 
0008
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1761179] Re: linux-aws: 4.15.0-1003.3 -proposed tracker

2018-04-11 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

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

** Tags removed: block-proposed-bionic

** Tags removed: block-proposed

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

Title:
  linux-aws: 4.15.0-1003.3 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1761177
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1761179] Re: linux-aws: 4.15.0-1003.3 -proposed tracker

2018-04-11 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux-aws: 4.15.0-1003.3 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1761177
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1763170] [NEW] Bionic update to v4.16.1 stable release

2018-04-11 Thread Seth Forshee
Public bug reported:

SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

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

bitmap: fix memset optimization on big-endian systems
USB: serial: ftdi_sio: add RT Systems VX-8 cable
USB: serial: ftdi_sio: add support for Harman FirmwareHubEmulator
USB: serial: cp210x: add ELDAT Easywave RX09 id
serial: 8250: Add Nuvoton NPCM UART
mei: remove dev_err message on an unsupported ioctl
/dev/mem: Avoid overwriting "err" in read_mem()
media: usbtv: prevent double free in error case
parport_pc: Add support for WCH CH382L PCI-E single parallel port card.
crypto: lrw - Free rctx->ext with kzfree
crypto: ccp - Fill the result buffer only on digest, finup, and final ops
crypto: talitos - don't persistently map req_ctx->hw_context and req_ctx->buf
crypto: inside-secure - fix clock management
crypto: testmgr - Fix incorrect values in PKCS#1 test vector
crypto: talitos - fix IPsec cipher in length
crypto: ahash - Fix early termination in hash walk
crypto: caam - Fix null dereference at error path
crypto: ccp - return an actual key size from RSA max_size callback
crypto: arm,arm64 - Fix random regeneration of S_shipped
crypto: x86/cast5-avx - fix ECB encryption when long sg follows short one
Bluetooth: hci_bcm: Add 6 new ACPI HIDs
Btrfs: fix unexpected cow in run_delalloc_nocow
siox: fix possible buffer overflow in device_add_store
staging: comedi: ni_mio_common: ack ai fifo error interrupts.
Revert "base: arch_topology: fix section mismatch build warnings"
Input: ALPS - fix TrackStick detection on Thinkpad L570 and Latitude 7370
Input: i8042 - add Lenovo ThinkPad L460 to i8042 reset list
Input: i8042 - enable MUX on Sony VAIO VGN-CS series to fix touchpad
vt: change SGR 21 to follow the standards
Fix slab name "biovec-(1<<(21-12))"
signal: Correct the offset of si_pkey and si_lower in struct siginfo on m68k
Linux 4.16.1

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: Fix Committed


** Tags: kernel-stable-tracking-bug

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The v4.16.1 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The v4.16.1 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
+    The following patches from the v4.16.1 stable release shall be
+ applied:
  
-The following patches from the v4.16.1 stable release shall be
- applied:
+ bitmap: fix memset optimization on big-endian systems
+ USB: serial: ftdi_sio: add RT Systems VX-8 cable
+ USB: serial: ftdi_sio: add support for Harman FirmwareHubEmulator
+ USB: serial: cp210x: add ELDAT Easywave RX09 id
+ serial: 8250: Add Nuvoton NPCM UART
+ mei: remove dev_err message on an unsupported ioctl
+ /dev/mem: Avoid overwriting "err" in read_mem()
+ media: usbtv: prevent double free in error case
+ parport_pc: Add support for WCH CH382L PCI-E single parallel port card.
+ crypto: lrw - Free rctx->ext with kzfree
+ crypto: ccp - Fill the result buffer only on digest, finup, and final ops
+ crypto: talitos - don't persistently map req_ctx->hw_context and req_ctx->buf
+ crypto: inside-secure - fix clock management
+ crypto: testmgr - Fix incorrect values in PKCS#1 test vector
+ crypto: talitos - fix IPsec cipher in length
+ crypto: ahash - Fix early termination in hash walk
+ crypto: caam - Fix null dereference at error path
+ crypto: ccp - return an actual key size from RSA max_size callback
+ crypto: arm,arm64 - Fix random regeneration of S_shipped
+ crypto: 

[Kernel-packages] [Bug 1760851] Re: ethernet wired adapter lost

2018-04-11 Thread Fabien COMBERNOUS
After a second reboot, the wired adapter device reappeared.
And since this, it never disappeared again.

I suppose this bug could be closed.

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

Title:
  ethernet wired adapter lost

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

Bug description:
  When i upgraded kernel from linux-image-4.4.0-112-generic to linux-
  image-4.4.0-116-generic, my dell xps lost the wired network adapter.

  On this laptop the ethernet wired adapter is on usb-c extension.  When i boot 
on my old kernel :
   * The device is named enxd481d74f12bb.
   * The address looks to be 
/sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enxd481d74f12bb

  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/controlC0:  fcombernous   7044 F pulseaudio
  Date: Tue Apr  3 14:18:14 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=7c5d4db9-e495-4d8b-ac3e-12534cd9fdd2
  InstallationDate: Installed on 2017-05-19 (319 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=ce828ede-44e4-4f8a-a8c4-422e1815674d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.17
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 00GCYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr:
  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/1760851/+subscriptions

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


[Kernel-packages] [Bug 1760656] Re: test_151_sysctl_disables_bpf_unpriv_userns in kernel security test failed with 4.4/4.15 kvm

2018-04-11 Thread Kamal Mostafa
** Changed in: linux-kvm (Ubuntu Xenial)
   Status: New => In Progress

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

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

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

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

Title:
  test_151_sysctl_disables_bpf_unpriv_userns in kernel security test
  failed with 4.4/4.15 kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  In Progress

Bug description:
FAIL: test_151_sysctl_disables_bpf_unpriv_userns 
(__main__.KernelSecurityTest)
unprivileged_bpf_disabled sysctl supported
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1951, in 
test_151_sysctl_disables_bpf_unpriv_userns
self._test_sysctl_value('kernel/unprivileged_bpf_disabled', expected, 
exists=exists)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1185, in _test_sysctl_value
self.assertEqual(exists, os.path.exists(sysctl), sysctl)
AssertionError: /proc/sys/kernel/unprivileged_bpf_disabled

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:22:38 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760656/+subscriptions

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


[Kernel-packages] [Bug 1760654] Re: test_140_kernel_modules_not_tainted in kernel security test failed with 4.4 X-kvm

2018-04-11 Thread Kamal Mostafa
This seems to be a false failure caused by test script itself (qa-
regression-testing/scripts/test-kernel-security.py):

Here, test_140_kernel_modules_not_tainted is complaining about a module
'signpost' which is a test module that was inserted by an unrelated test
case (test_072_strict_devmem) which ran and failed earlier in this run
(see bug 1760649).  The fault is that test_072_strict_devmem fails to
remove its 'signpost' test module at line 768 if that assert at line 766
fails.

@Po-Hsu, could you take a look at fixing test_072_strict_devmem so that
it removes 'signpost' regardless of success or failure?

** Changed in: linux-kvm (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: linux-kvm (Ubuntu Xenial)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux-kvm (Ubuntu)
   Status: New => Invalid

** Changed in: linux-kvm (Ubuntu Xenial)
   Status: Won't Fix => Invalid

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

Title:
  test_140_kernel_modules_not_tainted in kernel security test failed
  with 4.4 X-kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  Invalid

Bug description:
FAIL: test_140_kernel_modules_not_tainted (__main__.KernelSecurityTest)
kernel modules are not marked with a taint flag (especially 'E' for 
TAINT_UNSIGNED_MODULE)
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1740, in 
test_140_kernel_modules_not_tainted
self.fail('Module \'%s\' is tainted: %s' % (fields[0], last_field))
AssertionError: Module 'signpost' is tainted: (OE)

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:18:25 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760654/+subscriptions

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


[Kernel-packages] [Bug 1763156] Re: Bluetooth doesn't reconnect to my headsetup post resume from sleep

2018-04-11 Thread Anmar Oueja
The following patches were added to the 5.48 version in Fedora and they
did fix the problem. Perhaps worth you adding them as well. Please see
https://koji.fedoraproject.org/koji/buildinfo?buildID=1040106 and the
bug https://bugzilla.redhat.com/show_bug.cgi?id=1534857

** Attachment added: "bluez-5.48-patches.zip"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1763156/+attachment/5111219/+files/bluez-5.48-patches.zip

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

Title:
  Bluetooth doesn't reconnect to my headsetup post resume from sleep

Status in bluez package in Ubuntu:
  New

Bug description:
  Steps to repro:

  * Cold boot the laptop
  * Pair it with bluetooth headset
  * Listen to music
  * Turn off the headset or turn off the bluetooth on the laptop
  * Play music, sound comes out of the laptop speakers
  * Turn on the headset back on or the bluetooth on the laptop
  * Headset reconnects with the laptop and audio plays from the headset

  -- all the above is expected --

  * Suspend the laptop
  * wait a minute or two for the headset to power down
  * Resume the laptop
  * Turn on the bluetooth headeset
  * It doesn't automatically reconnect to the laptop (not expected behaviour)
  * Launch Gnome Settings and select Bluetooth and force the headset to connect
  * It connects for 2 seconds then disconnects (not expected behaviour)

  The only to get the headset to reconnect again is by restarting the
  bluetooth.service using systemctl.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr 11 15:28:28 2018
  InstallationDate: Installed on 2018-04-03 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=1f5de204-14c1-4ab7-b29c-880bbcd6f1d9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:34:41:D4:8F:36  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:19284 acl:106 sco:0 events:2607 errors:0
TX bytes:605507 acl:103 sco:0 commands:2473 errors:0

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

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


[Kernel-packages] [Bug 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic

2018-04-11 Thread Joseph Salisbury
*** This bug is a duplicate of bug 1759920 ***
https://bugs.launchpad.net/bugs/1759920

** This bug has been marked a duplicate of bug 1759920
   intel-microcode 3.20180312.0 causes lockup at login screen(w/ 
linux-image-4.13.0-37-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/1746418

Title:
  System freezes when starting Xorg after installing linux-
  image-4.13.0-32-generic

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

Bug description:
  My laptop (Lenovo T440) freezes when starting Xorg (lightdm) only
  after installing the latest ubuntu kernel for 17.10, linux-
  image-4.13.0-32-generic.

  Am running Xorg instead of MIR due to MIR crashing when I initially
  upgraded from 17.04 to 17.10, but that's a different problem for a
  different day. It's been running with Xorg stably for at least 2-3
  months.

  If I boot with the previous kernel version on my /boot (linux-
  image-4.13.0-25-generic), everything works fine.

  If I boot with the latest mainline kernel from the Ubuntu mainline
  repo (4.15.0), everything works.

  Using grub's option to run "Recovery Mode" for the 4.13.0-32 kernel, I
  am able to use the CLI and access the encrypted root filesystem, which
  is how I generated the apport repo that's attached. It's only when
  telling it to continue Normal booting that it freezes, which is why I
  suspect the problem of being Xorg.

  When the system freezes, the fan starts to spin up. I cannot switch
  virtual consoles using CTRL-ALT-F{1-7}. CTRL-ALT-DEL pressed
  repeatedly doesn't do anything. To reboot, I have to hold the power
  button until the system powers off.

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

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


[Kernel-packages] [Bug 1745349] Re: Hard lockup during boot with linux-image-4.4.0-112-generic

2018-04-11 Thread Joseph Salisbury
*** This bug is a duplicate of bug 1759920 ***
https://bugs.launchpad.net/bugs/1759920

** This bug has been marked a duplicate of bug 1759920
   intel-microcode 3.20180312.0 causes lockup at login screen(w/ 
linux-image-4.13.0-37-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/1745349

Title:
  Hard lockup during boot with linux-image-4.4.0-112-generic

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

Bug description:
  Systems on ASUS H110M-C Boards don't boot here with Kernel 4.4.0-112
  instead they show

  NMI watchdog: Watchdog detected hard lockup on cpu 0
  NMI watchdog: Watchdog detected hard lockup on cpu 1
  NMI watchdog: Watchdog detected hard lockup on cpu 3
  NMI watchdog: Watchdog detected hard lockup on cpu 2

  I cannot provide any logs of course.

  Booting with 4.4.0-109 works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lr3200 2013 F pulseaudio
  Date: Thu Jan 25 11:38:55 2018
  HibernationDevice: RESUME=UUID=8e35131d-6d40-4f4f-a3db-c7336e72cbce
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=4dc5bb0a-ab7c-48fa-ac23-bcdf23755d93 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3601
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-C:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1745349/+subscriptions

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


[Kernel-packages] [Bug 1763156] Re: Bluetooth doesn't reconnect to my headsetup post resume from sleep

2018-04-11 Thread Anmar Oueja
Problem seems resolved with bluez 5.48.2 as outlined in this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1534857#c30

** Bug watch added: Red Hat Bugzilla #1534857
   https://bugzilla.redhat.com/show_bug.cgi?id=1534857

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

Title:
  Bluetooth doesn't reconnect to my headsetup post resume from sleep

Status in bluez package in Ubuntu:
  New

Bug description:
  Steps to repro:

  * Cold boot the laptop
  * Pair it with bluetooth headset
  * Listen to music
  * Turn off the headset or turn off the bluetooth on the laptop
  * Play music, sound comes out of the laptop speakers
  * Turn on the headset back on or the bluetooth on the laptop
  * Headset reconnects with the laptop and audio plays from the headset

  -- all the above is expected --

  * Suspend the laptop
  * wait a minute or two for the headset to power down
  * Resume the laptop
  * Turn on the bluetooth headeset
  * It doesn't automatically reconnect to the laptop (not expected behaviour)
  * Launch Gnome Settings and select Bluetooth and force the headset to connect
  * It connects for 2 seconds then disconnects (not expected behaviour)

  The only to get the headset to reconnect again is by restarting the
  bluetooth.service using systemctl.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr 11 15:28:28 2018
  InstallationDate: Installed on 2018-04-03 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=1f5de204-14c1-4ab7-b29c-880bbcd6f1d9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:34:41:D4:8F:36  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:19284 acl:106 sco:0 events:2607 errors:0
TX bytes:605507 acl:103 sco:0 commands:2473 errors:0

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

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


[Kernel-packages] [Bug 1763156] [NEW] Bluetooth doesn't reconnect to my headsetup post resume from sleep

2018-04-11 Thread Anmar Oueja
Public bug reported:

Steps to repro:

* Cold boot the laptop
* Pair it with bluetooth headset
* Listen to music
* Turn off the headset or turn off the bluetooth on the laptop
* Play music, sound comes out of the laptop speakers
* Turn on the headset back on or the bluetooth on the laptop
* Headset reconnects with the laptop and audio plays from the headset

-- all the above is expected --

* Suspend the laptop
* wait a minute or two for the headset to power down
* Resume the laptop
* Turn on the bluetooth headeset
* It doesn't automatically reconnect to the laptop (not expected behaviour)
* Launch Gnome Settings and select Bluetooth and force the headset to connect
* It connects for 2 seconds then disconnects (not expected behaviour)

The only to get the headset to reconnect again is by restarting the
bluetooth.service using systemctl.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Apr 11 15:28:28 2018
InstallationDate: Installed on 2018-04-03 (8 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=1f5de204-14c1-4ab7-b29c-880bbcd6f1d9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.1
dmi.board.name: 0JHP5H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:34:41:D4:8F:36  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:19284 acl:106 sco:0 events:2607 errors:0
TX bytes:605507 acl:103 sco:0 commands:2473 errors:0

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


** Tags: amd64 apport-bug bionic wayland-session

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

Title:
  Bluetooth doesn't reconnect to my headsetup post resume from sleep

Status in bluez package in Ubuntu:
  New

Bug description:
  Steps to repro:

  * Cold boot the laptop
  * Pair it with bluetooth headset
  * Listen to music
  * Turn off the headset or turn off the bluetooth on the laptop
  * Play music, sound comes out of the laptop speakers
  * Turn on the headset back on or the bluetooth on the laptop
  * Headset reconnects with the laptop and audio plays from the headset

  -- all the above is expected --

  * Suspend the laptop
  * wait a minute or two for the headset to power down
  * Resume the laptop
  * Turn on the bluetooth headeset
  * It doesn't automatically reconnect to the laptop (not expected behaviour)
  * Launch Gnome Settings and select Bluetooth and force the headset to connect
  * It connects for 2 seconds then disconnects (not expected behaviour)

  The only to get the headset to reconnect again is by restarting the
  bluetooth.service using systemctl.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr 11 15:28:28 2018
  InstallationDate: Installed on 2018-04-03 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=1f5de204-14c1-4ab7-b29c-880bbcd6f1d9 ro quiet splash 
nouveau.modeset=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  

[Kernel-packages] [Bug 1685712] Re: [Featire] CNL: Enable RAPL support

2018-04-11 Thread Thadeu Lima de Souza Cascardo
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

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

Title:
  [Featire] CNL: Enable RAPL support

Status in intel:
  Incomplete
Status in intel trunk series:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  enable RAPL on Cannon Lake Client Platforms

  Kernel Release: 4.17
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1760653] Re: test_077_config_security_ipsec in kernel security test failed with 4.4/4.15 kvm

2018-04-11 Thread Kamal Mostafa
** Changed in: linux-kvm (Ubuntu Xenial)
   Status: New => In Progress

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

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

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

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

Title:
  test_077_config_security_ipsec in kernel security test failed with
  4.4/4.15 kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  In Progress

Bug description:
FAIL: test_077_config_security_ipsec (__main__.KernelSecurityTest)
Config options for IPsec
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 897, in 
test_077_config_security_ipsec
self.assertTrue(self._test_config(c), 'CONFIG_%s is not set' % (c))
AssertionError: CONFIG_XFRM_USER is not set

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:17:15 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760653/+subscriptions

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


[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)

2018-04-11 Thread Sebastiaan Breedveld
I can finally report a working solution for me.

Ubuntu 18.04 alpha
kernel 4.15.0-13-generic

Add these options to the GRUB command line:
pci=nomsi iommu=soft

USB works like a charm after resume :)

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

Title:
  USB stops working after a while (xhci_hcd :00:14.0: Timeout while
  waiting for setup device command)

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my laptop the kernel will sometimes drop the USB hub. After this,
  the laptop doesn't recognise any device plugged in to the USB ports -
  plugging and unplugging any device I've tried into any of the USB
  ports produces no response, not even dmesg entries.

  Strangely this also applies to bluetooth - it no longer works once USB
  has dropped (possibly the module is hung of the bus internally).

  Once this has happened only a reboot fixes it; I've not managed to
  find any combination of module unload/reload or suspend cycles to
  reinitialise things correctly.

  Relevant snippet of dmesg:
  [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe 
the host is dead
  [48838.079742] xhci_hcd :00:14.0: Abort command ring failed
  [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up
  [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079806] sched: RT throttling activated
  [48838.079981] usb 1-1: USB disconnect, device number 16
  [48838.079985] usb 1-1.2: USB disconnect, device number 18
  [48838.079987] usb 1-1.2.3: USB disconnect, device number 19
  [48838.080285] usb 1-1.2.4: USB disconnect, device number 20
  [48838.111892] usb 1-1.4: USB disconnect, device number 17
  [48838.191292] usb 1-4: USB disconnect, device number 6
  [48838.267550] usb 1-10: USB disconnect, device number 8
  [48838.282968] usb 2-1: device not accepting address 8, error -62
  [48838.282983] usb 2-1: USB disconnect, device number 8
  [48838.282986] usb 2-1.2: USB disconnect, device number 9

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  4255 F pulseaudio
   /dev/snd/controlC0:  chris  4255 F pulseaudio
  CRDA:
   country AU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (3, 23), (N/A)
(5250 - 5330 @ 40), (3, 23), (0 ms), DFS
(5735 - 5835 @ 40), (3, 30), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jan 22 12:59:27 2015
  InstallationDate: Installed on 2013-08-06 (533 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Galago UltraPro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed 
root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd break=mount
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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


[Kernel-packages] [Bug 1753430] Re: virtualbox-guest-utils.service not starting

2018-04-11 Thread Tony Middleton
Just did a fresh upgrade of Ubuntu Mate from Xenial to Bionic.  The
guest packages were installed on the Xenial system prior to upgrade.
During the upgrade the guest packages were upgraded, NOT removed.

However, on the upgraded system the virtualbox-guest-utils.service was
NOT started but could be started manually.

Thus the original bug reported on this number still applies, although
all the other issues found on the way seem to have been addressed.

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

Title:
  virtualbox-guest-utils.service not starting

Status in dkms package in Ubuntu:
  Fix Released

Bug description:
  I am trialing various flavours of Ubuntu in Virtualbox virtual
  machines - Xubuntu, Lubuntu, Ubuntu and Ubuntu Mate.  All version
  18.04, running on Kubuntu 17.10 host.  All set up identically as far
  as I can tell, with virtualbox-guest-dkms, virtualbox-guest-utils and
  virtualbox-guest-x11 installed in each guest.

  All work fine except that shared folders does not work in 2 of the
  VMs.  It works in Xubuntu, Ubuntu but not in Lubuntu and Ubuntu Mate.
  On investigation it appears that the virtualbox-guest-utils.service is
  not started automatically on the two versions not working.  If I start
  it manually everything is OK.

  Here is the status - 
  systemctl status virtualbox-guest-utils.service 
  ● virtualbox-guest-utils.service - Virtualbox guest utils
 Loaded: loaded (/lib/systemd/system/virtualbox-guest-utils.service; 
enabled; vendor preset: enabled)
 Active: inactive (dead)

  Looking in journalctl there are no messages showing that the service
  tried to start and failed.  There is nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-guest-utils 5.2.8-dfsg-2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic i686
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon Mar  5 09:53:02 2018
  InstallationDate: Installed on 2012-10-23 (1958 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: virtualbox
  UpgradeStatus: Upgraded to bionic on 2018-03-04 (0 days ago)

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

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


[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)

2018-04-11 Thread Gopal
Linux gopal-HP-Notebook 4.13.0-38-generic #43~lp1745646TwoReverts SMP Wed Apr 
11 12:07:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
http://paste.ubuntu.com/p/wz3XhCFWJx/

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

Title:
  Battery drains when laptop is off  (shutdown)

Status in Linux:
  Unknown
Status in acpi package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in acpi source package in Artful:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  I am using hp AY008tx laptop , and many other laptop users (HP) are also 
facing the same issue . The problem don't occur when i install windows 10 . 
Now, only ubuntu is installed.
  i am using latest bios insyde20 rev 5.(latest)
  WOL disabled and no usb device connected
  checked my battery .
  it don't happen when i remove battery and plug it again after shutdown.
  tried laptop_mode_tools and tpl too

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 26 22:50:53 2018
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopal  2391 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 0a5c:216d Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.58
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows

2018-04-11 Thread Julian Andres Klode
Sorry, messed up the tag a bit.

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows

2018-04-11 Thread Julian Andres Klode
I have seen this problem on all bionic kernels I have tested. The
machine has never seen anything older than bionic. I installed it from a
daily end of March.

The mainline kernel does not fix the bug.

** Tags added: bug-exists-upstream

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

** Tags removed: bug-exists-upstream
** 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/1763144

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] ProcModules.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1763144/+attachment/514/+files/ProcModules.txt

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows

2018-04-11 Thread Julian Andres Klode
Note that the thermal limit seems to be rewritten by the EC at random
times.

The person originally discovering the issue wrote a userspace daemon to
write the proper stuff in memory from time to time -
https://github.com/erpalma/lenovo-throttling-fix - but this should best
get fixed in the kernel (unless it's a bug in the BIOS/EC firmware, then
it's out of our hands).

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] Re: Significantly lower power and thermal limits on T480s (and probably others) than on Windows

2018-04-11 Thread Julian Andres Klode
An actually useful dmesg log (from journalctl -k)

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+attachment/520/+files/dmesg.txt

** Summary changed:

- Significantly lower power and thermal limits on T480s (and probably others) 
than on Windows
+ Significantly lower power and thermal limits on ThinkPad T480s (and probably 
others) than on Windows

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1685712] Re: [Featire] CNL: Enable RAPL support

2018-04-11 Thread Thadeu Lima de Souza Cascardo
** Also affects: intel/trunk
   Importance: Undecided
   Status: Incomplete

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

Title:
  [Featire] CNL: Enable RAPL support

Status in intel:
  Incomplete
Status in intel trunk series:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  enable RAPL on Cannon Lake Client Platforms

  Kernel Release: 4.17
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1760648] Re: test_072_config_strict_devmem in kernel security test failed with 4.4/4.15 kvm

2018-04-11 Thread Kamal Mostafa
** Changed in: linux-kvm (Ubuntu Xenial)
   Status: New => In Progress

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

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

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

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

Title:
  test_072_config_strict_devmem in kernel security test failed with
  4.4/4.15 kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  In Progress

Bug description:
FAIL: test_072_config_strict_devmem (__main__.KernelSecurityTest)
CONFIG_STRICT_DEVMEM enabled
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 707, in 
test_072_config_strict_devmem
self.assertEqual(self._test_config('STRICT_DEVMEM'), strict)
AssertionError: False != True

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:02:10 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760648/+subscriptions

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


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

2018-04-11 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1734327] Re: Kernel panic on a nfsroot system

2018-04-11 Thread Fabio Augusto Miranda Martins
** Changed in: linux (Ubuntu Artful)
   Status: Fix Committed => 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/1734327

Title:
  Kernel panic on a nfsroot system

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

Bug description:
  == SRU Justification ==
  The following commit introduced a regression identified in bug 1734327:
  ac8f82a0b6d9 ("UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure management of 
the remaining blobs")

  The regression causes a kernel panic to occur after multiple TCP connection 
  creations/closures to the localhost.  The bug was found using STAF RPC calls, 
  but is easily reproducible with SSH.

  A revert of commit ac8f82a0b6d9 is needed to resolve this bug.  However, 
commit 4ae2508f0bed
  also needs to be reverted because it depend on commit ac8f82a0b6d9.

  == Fix ==
  Revert 4ae2508f0bed ("UBUNTU: SAUCE: LSM stacking: add stacking support to 
apparmor network hooks")
  Revert ac8f82a0b6d9 ("UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure 
management of the remaining blobs")

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



  
  == Original Bug Description ==
  Summary:
  Kernel panic occurs after multiple TCP connection creations/closures to the 
localhost.
  The bug was found using STAF RPC calls, but is easily reproducible with SSH.
  The bug doesn't appear on an identical virtual machine booting from the disk.
  The bug is not reproducible on a similarly-prepared Ubuntu 16.04 machine.
  The bug is reproducible using an older 4.13.0-16-generic kernel
  Reproducible on multiple hardware types.
  Unable to create a kernel memory dump due to makedumpfile errors.
  apport-bug save attached.

  NFSRoot boot options:
  vmlinuz initrd=initrd.img boot=nfs root=/dev/nfs 
nfsroot=190.0.0.254:/diskless/host/u1616/Ubuntu/17.10 intel_iommu=on 
net.ifnames=0 biosdevname=0 apparmor=0 ip=:eth0:dhcp 
blacklist=i40e,ixgbe,fm10k crashkernel=384M-:768M rw

  Software:
  OS: Ubuntu 17.10
  Kernel: 4.13.0-17-generic x86_64

  Reproduction steps:
  1. Boot a system from a nfsroot
  2. Configure password-less localhost ssh access
  3. Run a loop: `while true; do ssh localhost 'uname -a'; done`
  4. Wait for system to crash

  Trace:
  4,1151,52372730,-;general protection fault:  [#1] SMP
  4,1152,52372771,-;Modules linked in: arc4 md4 rpcsec_gss_krb5 nls_utf8 
auth_rpcgss cifs nfsv4 ccm ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal 
intel_powerclamp coretemp intel_cstate mei_me input_leds joydev intel_rapl_perf 
mei kvm_intel lpc_ich ioatdma kvm irqbypass ipmi_si ipmi_devintf 
ipmi_msghandler shpchp acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ast ttm aesni_intel igb 
drm_kms_helper aes_x86_64 crypto_simd syscopyarea glue_helper
  4,1153,52373251,c; sysfillrect dca cryptd sysimgblt i2c_algo_bit fb_sys_fops 
ahci ptp drm libahci pps_core wmi
  4,1154,52373322,-;CPU: 11 PID: 1848 Comm: STAFProc Not tainted 
4.13.0-17-generic #20-Ubuntu
  4,1155,52373371,-;Hardware name: Supermicro Super Server/X10SRD-F, BIOS 2.0 
12/17/2015
  4,1156,52373418,-;task: 9d09267f5d00 task.stack: afddc3a7
  4,1157,52373461,-;RIP: 0010:kfree+0x53/0x160
  4,1158,52373486,-;RSP: 0018:9d092ecc3bc8 EFLAGS: 00010207
  4,1159,52373521,-;RAX:  RBX: 241c89490001 RCX: 
0004
  4,1160,52373566,-;RDX: 32d49081cc08 RSI: 00010080 RDI: 
62fac000
  4,1161,52373611,-;RBP: 9d092ecc3be0 R08: 0001f4c0 R09: 
943bb839
  4,1162,52373656,-;R10: 00904c789100 R11:  R12: 
9d09267ef000
  4,1163,52373701,-;R13: 93fa155e R14: 9d09267ef000 R15: 
9d09267ef000
  4,1164,52373746,-;FS:  7f3a53313700() GS:9d092ecc() 
knlGS:
  4,1165,52373797,-;CS:  0010 DS:  ES:  CR0: 80050033
  4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4: 
003406e0
  4,1167,52373878,-;DR0:  DR1:  DR2: 

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; 

[Kernel-packages] [Bug 1763107] Re: linux-kvm 4.15 needs UNWINDER_FRAME_POINTER

2018-04-11 Thread Kamal Mostafa
** Changed in: linux-kvm (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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1763107

Title:
  linux-kvm 4.15 needs UNWINDER_FRAME_POINTER

Status in linux-kvm package in Ubuntu:
  Fix Committed
Status in linux-kvm source package in Bionic:
  Fix Committed

Bug description:
  As is the case for bionic, linux-kvm requires UNWINDER_FRAME_POINTER
  vs UNWINDER_ORC:

  commit 028eb9123f783b3a38936b1a02a235c4680f873d
  Author: Seth Forshee 
  Date:   Sat Dec 9 22:08:25 2017 -0600

  UBUNTU: [Config] CONFIG_UNWINDER_FRAME_POINTER=y for amd64
  
  During the rebase to 4.15 UNWINDER_ORC was chosen as the stack
  unwinder as it promises a 5-10% performance improvement over
  using UNWINDER_FRAME_POINTER. However it turns out to have a
  couple of downsides. It adds a new requierment for building dkms
  modules, and it does not produce the reliable stack traces
  required for livepatch. Switch back to UNWINDER_FRAME_POINTER.
  
  Signed-off-by: Seth Forshee 

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

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


[Kernel-packages] [Bug 1763144] PulseList.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1763144/+attachment/515/+files/PulseList.txt

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows

2018-04-11 Thread Julian Andres Klode
He also reported it to Lenovo at https://forums.lenovo.com/t5/Linux-
Discussion/X1C6-T480s-low-cTDP-and-trip-temperature-in-
Linux/td-p/4028489

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] ProcInterrupts.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1763144/+attachment/513/+files/ProcInterrupts.txt

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows

2018-04-11 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16


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

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

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] UdevDb.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1763144/+attachment/517/+files/UdevDb.txt

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] RfKill.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1763144/+attachment/516/+files/RfKill.txt

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1685712] Re: [Featire] CNL: Enable RAPL support

2018-04-11 Thread Thadeu Lima de Souza Cascardo
** 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/1685712

Title:
  [Featire] CNL: Enable RAPL support

Status in intel:
  Incomplete
Status in intel trunk series:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  enable RAPL on Cannon Lake Client Platforms

  Kernel Release: 4.17
  Target Release: 18.04

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

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


[Kernel-packages] [Bug 1763144] ProcCpuinfo.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1763144/+attachment/510/+files/ProcCpuinfo.txt

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] Lspci.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1763144/+attachment/508/+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/1763144

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] CurrentDmesg.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1763144/+attachment/506/+files/CurrentDmesg.txt

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] IwConfig.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1763144/+attachment/507/+files/IwConfig.txt

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


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

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1763144/+attachment/512/+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/1763144

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] CRDA.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1763144/+attachment/505/+files/CRDA.txt

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] AlsaInfo.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1763144/+attachment/504/+files/AlsaInfo.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/1763144

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] ProcCpuinfoMinimal.txt

2018-04-11 Thread Julian Andres Klode
apport information

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] Lsusb.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1763144/+attachment/509/+files/Lsusb.txt

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] WifiSyslog.txt

2018-04-11 Thread Julian Andres Klode
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1763144/+attachment/518/+files/WifiSyslog.txt

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

Title:
  Significantly lower power and thermal limits on ThinkPad T480s (and
  probably others) than on Windows

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A ThinkPad T480s under windows has a power limit of 44W, both short
  and long term, with a thermal maximum of about 93C or so. Under Linux,
  the power limits are 44W and 15W (short) or so, and the thermal limit
  is 80C, causing a significant performance loss.

  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078

  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
  -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
  in performance comparative to Windows.

  Most of the analysis is based on the analysis in

  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  This applies to all bionic kernels I have tested so far, including

  Ubuntu 4.15.0-13.14-generic 4.15.10
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
   /dev/snd/controlC2:  jak5881 F pulseaudio
   /dev/snd/controlC1:  jak5881 F pulseaudio
   /dev/snd/controlC0:  jak5881 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-14 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ 
quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1763144] [NEW] Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows

2018-04-11 Thread Julian Andres Klode
Public bug reported:

A ThinkPad T480s under windows has a power limit of 44W, both short and
long term, with a thermal maximum of about 93C or so. Under Linux, the
power limits are 44W and 15W (short) or so, and the thermal limit is
80C, causing a significant performance loss.

Looking at MSR and MCHBAR values, we can see that the values are
correctly at 44W in the MSR, but the MCHBAR is set to a lower value:

$ sudo rdmsr -a 0x610
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
$ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
0x0042816000dd8078


Setting the MCHBAR to the same value as the MSR register solves the problem. At 
some point intel-rapl seems to reduce overall frequency to 600 MHz, though.

The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24 -d
0x1a2 returns 20. Setting those bits to 7 increases it, resulting in
performance comparative to Windows.

Most of the analysis is based on the analysis in

https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

This applies to all bionic kernels I have tested so far, including

Ubuntu 4.15.0-13.14-generic 4.15.10
--- 
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
 /dev/snd/controlC2:  jak5881 F pulseaudio
 /dev/snd/controlC1:  jak5881 F pulseaudio
 /dev/snd/controlC0:  jak5881 F pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-03-14 (28 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
MachineType: LENOVO 20L8S02D00
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet 
splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-13-generic N/A
 linux-backports-modules-4.15.0-13-generic  N/A
 linux-firmware 1.173
Tags:  bionic
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET31W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S02D00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S02D00
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO

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


** Tags: apport-collected bionic

** Tags added: apport-collected bionic

** Description changed:

  A ThinkPad T480s under windows has a power limit of 44W, both short and
  long term, with a thermal maximum of about 93C or so. Under Linux, the
  power limits are 44W and 15W (short) or so, and the thermal limit is
  80C, causing a significant performance loss.
  
  Looking at MSR and MCHBAR values, we can see that the values are
  correctly at 44W in the MSR, but the MCHBAR is set to a lower value:
  
  $ sudo rdmsr -a 0x610
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  42816000dd8160
  $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
  0x0042816000dd8078
  
  
  Setting the MCHBAR to the same value as the MSR register solves the problem. 
At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.
  
  The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24 -d
  0x1a2 returns 20. Setting those bits to 7 increases it, resulting in
  performance comparative to Windows.
  
  Most of the analysis is based on the analysis in
  
  https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/
  
  This applies to all bionic kernels I have tested so far, including
  
  Ubuntu 4.15.0-13.14-generic 4.15.10
+ --- 
+ ApportVersion: 2.20.9-0ubuntu4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC2D0p:   jak5881 F...m pulseaudio
+  /dev/snd/controlC2:  jak5881 F pulseaudio
+  /dev/snd/controlC1:  jak5881 F pulseaudio
+  /dev/snd/controlC0:  jak5881 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-03-14 (28 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
+ MachineType: LENOVO 20L8S02D00
+ Package: linux (not installed)
+ 

[Kernel-packages] [Bug 1760649] Re: test_072_strict_devmem in kernel security test failed with 4.4/4.15 kvm

2018-04-11 Thread Kamal Mostafa
** Changed in: linux-kvm (Ubuntu Xenial)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

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

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

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

Title:
  test_072_strict_devmem in kernel security test failed with 4.4/4.15
  kvm

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux-kvm source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  In Progress

Bug description:
FAIL: test_072_strict_devmem (__main__.KernelSecurityTest)
/dev/mem unreadable for kernel memory
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 766, in test_072_strict_devmem
self.assertTrue(rc in expected, 'exit code: %d (wanted %s). 
Output:\n%s' % (rc, ", ".join(["%d" % (x) for x in expected]), output))
AssertionError: exit code: 1 (wanted 0). Output:
/dev/mem: No such file or directory

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 17:10:38 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760649/+subscriptions

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


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

2018-04-11 Thread Seth Forshee
I've applied the additional fix to bionic/master-next, thanks!

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

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

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

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

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

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

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

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

  commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

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

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

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

  b2e2f43a01bace1a25bdbae04c9f9846882b727a
  6e179d64126b909f0b288fa63cdbf07c531e9b1d
  bc035599718412cfba9249aa713f90ef13f13ee9
  d424986f1d6b16079b3231db0314923f4f8deed1

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

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


[Kernel-packages] [Bug 1763107] [NEW] linux-kvm 4.15 needs UNWINDER_FRAME_POINTER

2018-04-11 Thread Kamal Mostafa
Public bug reported:

As is the case for bionic, linux-kvm requires UNWINDER_FRAME_POINTER vs
UNWINDER_ORC:

commit 028eb9123f783b3a38936b1a02a235c4680f873d
Author: Seth Forshee 
Date:   Sat Dec 9 22:08:25 2017 -0600

UBUNTU: [Config] CONFIG_UNWINDER_FRAME_POINTER=y for amd64

During the rebase to 4.15 UNWINDER_ORC was chosen as the stack
unwinder as it promises a 5-10% performance improvement over
using UNWINDER_FRAME_POINTER. However it turns out to have a
couple of downsides. It adds a new requierment for building dkms
modules, and it does not produce the reliable stack traces
required for livepatch. Switch back to UNWINDER_FRAME_POINTER.

Signed-off-by: Seth Forshee 

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

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

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

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

Title:
  linux-kvm 4.15 needs UNWINDER_FRAME_POINTER

Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Bionic:
  In Progress

Bug description:
  As is the case for bionic, linux-kvm requires UNWINDER_FRAME_POINTER
  vs UNWINDER_ORC:

  commit 028eb9123f783b3a38936b1a02a235c4680f873d
  Author: Seth Forshee 
  Date:   Sat Dec 9 22:08:25 2017 -0600

  UBUNTU: [Config] CONFIG_UNWINDER_FRAME_POINTER=y for amd64
  
  During the rebase to 4.15 UNWINDER_ORC was chosen as the stack
  unwinder as it promises a 5-10% performance improvement over
  using UNWINDER_FRAME_POINTER. However it turns out to have a
  couple of downsides. It adds a new requierment for building dkms
  modules, and it does not produce the reliable stack traces
  required for livepatch. Switch back to UNWINDER_FRAME_POINTER.
  
  Signed-off-by: Seth Forshee 

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

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


[Kernel-packages] [Bug 1763067] Re: zvol_id throws ioctl_get_msg failed:Inappropriate ioctl for device

2018-04-11 Thread Colin Ian King
** Changed in: zfs-linux (Ubuntu)
   Status: New => In Progress

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

Title:
  zvol_id throws ioctl_get_msg failed:Inappropriate ioctl for device

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  Symlinks in /dev/zvol are not created because /lib/udev/zvol_id
  crashes with ioctl_get_msg failed:Inappropriate ioctl for device.

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Running  linux-generic-hwe-16.04-edge
  4.15.0-13-generic

  zfsutils-linux 0.6.5.6-0ubuntu19

  The version of zvol_id in zfsutils-linux_0.7.5-1ubuntu14_amd64 works
  without error.

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

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


[Kernel-packages] [Bug 1763062] Re: LSM stacking patches for bionic

2018-04-11 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

Title:
  LSM stacking patches for bionic

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

Bug description:
  LSM stacking patches for bionic

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

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


[Kernel-packages] [Bug 1762913] Re: [OPAL] Assert fail: core/mem_region.c:447:lock_held_by_me(>free_list_lock)

2018-04-11 Thread Joseph Salisbury
The Bionic request has been sent.  However, because Artful is a stable
release, it requires testing before submitting a SRU request.

I built an Artful test kernel with commit 
47712a921bb781caf69fca9eae43be19968816cb.  The test kernel can be downloaded 
from:
http://kernel.ubuntu.com/~jsalisbury/lp1762913

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!

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

Title:
  [OPAL] Assert fail:
  core/mem_region.c:447:lock_held_by_me(>free_list_lock)

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 - Application Cdeadmin  -
  2018-04-03 05:20:56 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-04-05 01:30:56 ==
  --- Comment From pridhiviraj 2018-04-05 01:30:25 EDT ---
  The disto needs 47712a921bb781caf69fca9eae43be19968816cb this level of 
commits need to be backported as suggested by Nick piggin.

  == Comment: #2 - PAWAN K. SINGH <> - 2018-04-06 03:35:49 ==
  which is 
  >>>

  From 47712a921bb781caf69fca9eae43be19968816cb Mon Sep 17 00:00:00 2001
  From: Nicholas Piggin 
  Date: Wed, 17 Jan 2018 22:47:22 +1000
  Subject: [PATCH] powerpc/watchdog: remove arch_trigger_cpumask_backtrace

  The powerpc NMI IPIs may not be recoverable if they are taken in
  some sections of code, and also there have been and still are issues
  with taking NMIs (in KVM guest code, in firmware, etc) which makes them
  a bit dangerous to use.

  Generic code like softlockup detector and rcu stall detectors really
  hammer on trigger_*_backtrace, which has lead to further problems
  because we've implemented it with the NMI.

  So stop providing NMI backtraces for now. Importantly, the powerpc code
  uses NMI IPIs in crash/debug, and the SMP hardlockup watchdog. So if the
  softlockup and rcu hang detection traces are not being printed because
  the CPU is stuck with interrupts off, then the hard lockup watchdog
  should get it with the NMI IPI.

  Fixes: 2104180a5369 ("powerpc/64s: implement arch-specific hardlockup 
watchdog")
  Signed-off-by: Nicholas Piggin 
  Signed-off-by: Michael Ellerman 
  ---
   arch/powerpc/include/asm/nmi.h |  4 
   arch/powerpc/kernel/watchdog.c | 22 --
   2 files changed, 26 deletions(-)

  diff --git a/arch/powerpc/include/asm/nmi.h b/arch/powerpc/include/asm/nmi.h
  index e97f586..9c80939 100644
  --- a/arch/powerpc/include/asm/nmi.h
  +++ b/arch/powerpc/include/asm/nmi.h
  @@ -4,10 +4,6 @@
   
   #ifdef CONFIG_PPC_WATCHDOG
   extern void arch_touch_nmi_watchdog(void);
  -extern void arch_trigger_cpumask_backtrace(const cpumask_t *mask,
  -bool exclude_self);
  -#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace
  -
   #else
   static inline void arch_touch_nmi_watchdog(void) {}
   #endif
  diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c
  index 87da80c..3963baa 100644
  --- a/arch/powerpc/kernel/watchdog.c
  +++ b/arch/powerpc/kernel/watchdog.c
  @@ -393,25 +393,3 @@ int __init watchdog_nmi_probe(void)
}
return 0;
   }
  -
  -static void handle_backtrace_ipi(struct pt_regs *regs)
  -{
  - nmi_cpu_backtrace(regs);
  -}
  -
  -static void raise_backtrace_ipi(cpumask_t *mask)
  -{
  - unsigned int cpu;
  -
  - for_each_cpu(cpu, mask) {
  - if (cpu == smp_processor_id())
  - handle_backtrace_ipi(NULL);
  - else
  - smp_send_nmi_ipi(cpu, handle_backtrace_ipi, 100);
  - }
  -}
  -
  -void arch_trigger_cpumask_backtrace(const cpumask_t *mask, bool exclude_self)
  -{
  - nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi);
  -}
  -- 
  2.7.4

  
  >>>

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

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


[Kernel-packages] [Bug 1762725] Re: Linux reports Samson Meteor USB mic as an output device

2018-04-11 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  Linux reports Samson Meteor USB mic as an output device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever I reboot my system, pulseaudio selects my Samson Meteor USB
  mic as the default output device. I have to manually select the analog
  output every time. Also, the Default effect sound does not make any
  noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2355 F pulseaudio
   /dev/snd/controlC1:  guru   2355 F pulseaudio
   /dev/snd/controlC0:  guru   2355 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Tue Apr 10 08:54:30 2018
  InstallationDate: Installed on 2018-04-07 (2 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.52
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2402 F pulseaudio
   /dev/snd/controlC1:  guru   2402 F pulseaudio
   /dev/snd/controlC0:  guru   2402 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-07 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  IwConfig:
   enp30s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7A37
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.52
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350M MORTAR ARCTIC (MS-7A37)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 4
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.52:bd06/06/2017:svnMSI:pnMS-7A37:pvr2.0:rvnMSI:rnB350MMORTARARCTIC(MS-7A37):rvr2.0:cvnMSI:ct4:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A37
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  guru   2402 F pulseaudio
   /dev/snd/controlC1:  guru   2402 F pulseaudio
   /dev/snd/controlC0:  guru   2402 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-07 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  IwConfig:
   enp30s0   no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7A37
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=9407e2de-9df6-494d-8d4a-ab6fd82dbe85 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A

[Kernel-packages] [Bug 1762844] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel

2018-04-11 Thread Joseph Salisbury
Can you see if the bug happens with and of these mainline kernels?  We
can perform a kernel bisect if we can narrow down to the last good
kernel version and first bad one:

v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/
v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/
v4.15-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc4/
v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/

You don't have to test every kernel, just up until the kernel that first
has this bug.

Thanks in advance!

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
   Status: Triaged

** Tags added: kernel-key

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   

[Kernel-packages] [Bug 1762816] Re: chaoskey interferes with suspend on thinkpad

2018-04-11 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16

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

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

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

Title:
  chaoskey interferes with suspend on thinkpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Thinkpad T450s, docking station, Altus Metrum Chaoskey plugged into
  the docking station - suspend fails often (more than half the time,
  maybe not 100% but easily duplicated in my setup) in that it doesn't
  seem to go all the way down - and on wakeup, lsusb output doesn't
  update, `lsusb -t` hangs when run.  It *may* require "suspend, undock,
  unsuspend" but I'm not convinced...

  Interesting logs include a "blocked for more than 120 seconds"
  traceback after restore that goes through chaoskey_disconnect even
  though the laptop is undocked so it's no longer attached:

  [17038.103142] Call Trace:
__schedule+0x297/0x8b0
schedule+0x2c/0x80
schedule_timeout+0x1cf/0x350
? ttwu_do_activate+0x7a/0x90
wait_for_completion+0xba/0x140
? wake_up_q+0x80/0x80
hwrng_unregister+0x8f/0xa0
  ***  chaoskey_disconnect+0xbe/0x110 [chaoskey] ***
usb_unbind_interface+0x77/0x290
device_release_driver_internal+0x15b/0x220
device_release_driver+0x12/0x20
bus_remove_device+0xec/0x160
device_del+0x13d/0x360
? usb_remove_ep_devs+0x1f/0x30
usb_disable_device+0x9f/0x270
usb_disconnect+0xc6/0x270
hub_quiesce+0x48/0xa0
hub_event+0xfb/0xb10
process_one_work+0x1de/0x410
worker_thread+0x32/0x410
kthread+0x121/0x140
? process_one_work+0x410/0x410
? kthread_create_worker_on_cpu+0x70/0x70
? do_syscall_64+0x73/0x130
? SyS_exit_group+0x14/0x20
ret_from_fork+0x35/0x40

  Kernel is most recently `4.15.0-13-generic #14-Ubuntu` but it's been
  going on for the last month of bionic, and *possibly* longer but I
  only recently caught that the Chaoskey was related.

  $ lsb_release -rd
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  $ uname -a
  Linux workbench 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:44:27 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ dpkg --status linux-image-4.15.0-13-generic
  Package: linux-image-4.15.0-13-generic
  Status: install ok installed
  Priority: optional
  Section: kernel
  Installed-Size: 72167
  Maintainer: Ubuntu Kernel Team 
  Architecture: amd64
  Source: linux
  Version: 4.15.0-13.14
  Provides: aufs-dkms, fuse-module, ivtv-modules, kvm-api-4, linux-image, 
redhat-cluster-modules, spl-dkms, spl-modules, virtualbox-guest-modules, 
zfs-dkms, zfs-modules
  Depends: kmod
  Recommends: grub-pc | grub-efi-amd64 | grub-efi-ia32 | grub | lilo, 
initramfs-tools | linux-initramfs-tool
  Suggests: fdutils, linux-doc-4.15.0 | linux-source-4.15.0, linux-tools, 
linux-headers-4.15.0-13-generic
  Description: Linux kernel image for version 4.15.0 on 64 bit x86 SMP
   This package contains the Linux kernel image for version 4.15.0 on
   64 bit x86 SMP.
   .
   Also includes the corresponding System.map file, the modules built by the
   packager, and scripts that try to ensure that the system is not left in an
   unbootable state after an update.
   .
   Supports Generic processors.
   .
   Geared toward desktop and server systems.
   .
   You likely do not want to install this package directly. Instead, install
   the linux-generic meta-package, which will ensure that upgrades work
   correctly, and that supporting packages are also installed.

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

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


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

2018-04-11 Thread bugproxy
--- Comment From martin.schwidef...@de.ibm.com 2018-04-11 12:11 EDT---
> Cherry picked the auto-detection patches into bionic, set
> CONFIG_EXPOLINE_AUTO=y and CONFIG_KERNEL_NOBP=n.

You sure are quick.. Unfortunately there is a bug in the auto-detection
which is solved by a patch I created today. It can be found on the
s390/linux:features branch on kernel.org:

https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=features=6a3d1e81a434fc311f224b8be77258bafc18ccc6

I plan to send a please-pull for this by the end of the week.

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

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

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

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

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

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

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

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

  commit 6e179d64126b909f0b288fa63cdbf07c531e9b1d

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

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

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

  b2e2f43a01bace1a25bdbae04c9f9846882b727a
  6e179d64126b909f0b288fa63cdbf07c531e9b1d
  bc035599718412cfba9249aa713f90ef13f13ee9
  d424986f1d6b16079b3231db0314923f4f8deed1

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

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


[Kernel-packages] [Bug 1755979] Re: Cpu utilization showing system time for kvm guests (performance) (sysstat)

2018-04-11 Thread bugproxy
--- Comment From jhop...@us.ibm.com 2018-04-11 12:01 EDT---
I verified the -proposed kernel fixes the issue:

10:59:35 AM  CPU%usr   %nice%sys %iowait%irq   %soft  %steal  
%guest  %gnice   %idle
10:59:37 AM  all0.010.000.080.000.000.010.00   
20.680.00   79.21
10:59:37 AM00.530.000.000.000.000.000.00   
51.340.00   48.13
10:59:37 AM10.000.000.000.000.000.000.00   
76.000.00   24.00

Selected version '4.13.0.39.42' (Ubuntu:17.10/artful-proposed [ppc64el])
for 'linux-image-generic'

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

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

Title:
  Cpu utilization showing system time for kvm guests (performance)
  (sysstat)

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

Bug description:
  == SRU Justification ==
  All KVM guest cpu utilization is being reported as sys% time in the host.
  It turns out Guest time accounting (CONFIG_VIRT_CPU_ACCOUNTING_GEN) has
  been broken since v4.13 by commit 8b24e69fc47e436.

  Commit 61bd0f66ff92 fixes this bug and is included in mainline as of 
v4.16-rc5.
  The commit was cc'd to upstream stable, but has not yet landed in upstream 
4.15.

  == Fix ==
  61bd0f66ff92 ("KVM: PPC: Book3S HV: Fix guest time accounting with 
VIRT_CPU_ACCOUNTING_GEN")

  == Regression Potential ==
  Low.  Also cc'd to stable, so it has had additionl upstream review.  Limited 
to powerpc.

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


  == Comment: #0 - JENIFER HOPPER  - 2018-03-14 16:20:47 ==
  +++ This bug was initially created as a clone of Bug #163375 +++

  ---Problem Description---
  All KVM guest cpu utilization is being reported as sys% time in the host.
  It turns out Guest time accounting (CONFIG_VIRT_CPU_ACCOUNTING_GEN) has been 
broken since v4.13 by commit:

  commit 8b24e69fc47e43679bb29ddb481aa0e8dce2a3c5
  Author: Paul Mackerras 
  Date:   Mon Jun 26 15:45:51 2017 +1000

  KVM: PPC: Book3S HV: Close race with testing for signals on guest
  entry

  ---

  That is now fixed and upstream accepted in Paulus' tree as git commit:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-fixes=61bd0f66ff92d5ce765ff9850fd3cbfec773c560
  ("KVM: PPC: Book3S HV: Fix guest time accounting with 
VIRT_CPU_ACCOUNTING_GEN")

  Please include this patch in Ubuntu so that guest cpu accounting is
  correct.

  Contact Information = jhop...@us.ibm.com

  ---uname output---
  Linux ltc-b114 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 5104-22C

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   Start a KVM guest, run something that generates cpu utilization in the 
guest, observe mpstat on the host.

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

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


[Kernel-packages] [Bug 1762913] Re: [OPAL] Assert fail: core/mem_region.c:447:lock_held_by_me(>free_list_lock)

2018-04-11 Thread Joseph Salisbury
Bionic request:
https://lists.ubuntu.com/archives/kernel-team/2018-April/091528.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/1762913

Title:
  [OPAL] Assert fail:
  core/mem_region.c:447:lock_held_by_me(>free_list_lock)

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 - Application Cdeadmin  -
  2018-04-03 05:20:56 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-04-05 01:30:56 ==
  --- Comment From pridhiviraj 2018-04-05 01:30:25 EDT ---
  The disto needs 47712a921bb781caf69fca9eae43be19968816cb this level of 
commits need to be backported as suggested by Nick piggin.

  == Comment: #2 - PAWAN K. SINGH <> - 2018-04-06 03:35:49 ==
  which is 
  >>>

  From 47712a921bb781caf69fca9eae43be19968816cb Mon Sep 17 00:00:00 2001
  From: Nicholas Piggin 
  Date: Wed, 17 Jan 2018 22:47:22 +1000
  Subject: [PATCH] powerpc/watchdog: remove arch_trigger_cpumask_backtrace

  The powerpc NMI IPIs may not be recoverable if they are taken in
  some sections of code, and also there have been and still are issues
  with taking NMIs (in KVM guest code, in firmware, etc) which makes them
  a bit dangerous to use.

  Generic code like softlockup detector and rcu stall detectors really
  hammer on trigger_*_backtrace, which has lead to further problems
  because we've implemented it with the NMI.

  So stop providing NMI backtraces for now. Importantly, the powerpc code
  uses NMI IPIs in crash/debug, and the SMP hardlockup watchdog. So if the
  softlockup and rcu hang detection traces are not being printed because
  the CPU is stuck with interrupts off, then the hard lockup watchdog
  should get it with the NMI IPI.

  Fixes: 2104180a5369 ("powerpc/64s: implement arch-specific hardlockup 
watchdog")
  Signed-off-by: Nicholas Piggin 
  Signed-off-by: Michael Ellerman 
  ---
   arch/powerpc/include/asm/nmi.h |  4 
   arch/powerpc/kernel/watchdog.c | 22 --
   2 files changed, 26 deletions(-)

  diff --git a/arch/powerpc/include/asm/nmi.h b/arch/powerpc/include/asm/nmi.h
  index e97f586..9c80939 100644
  --- a/arch/powerpc/include/asm/nmi.h
  +++ b/arch/powerpc/include/asm/nmi.h
  @@ -4,10 +4,6 @@
   
   #ifdef CONFIG_PPC_WATCHDOG
   extern void arch_touch_nmi_watchdog(void);
  -extern void arch_trigger_cpumask_backtrace(const cpumask_t *mask,
  -bool exclude_self);
  -#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace
  -
   #else
   static inline void arch_touch_nmi_watchdog(void) {}
   #endif
  diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c
  index 87da80c..3963baa 100644
  --- a/arch/powerpc/kernel/watchdog.c
  +++ b/arch/powerpc/kernel/watchdog.c
  @@ -393,25 +393,3 @@ int __init watchdog_nmi_probe(void)
}
return 0;
   }
  -
  -static void handle_backtrace_ipi(struct pt_regs *regs)
  -{
  - nmi_cpu_backtrace(regs);
  -}
  -
  -static void raise_backtrace_ipi(cpumask_t *mask)
  -{
  - unsigned int cpu;
  -
  - for_each_cpu(cpu, mask) {
  - if (cpu == smp_processor_id())
  - handle_backtrace_ipi(NULL);
  - else
  - smp_send_nmi_ipi(cpu, handle_backtrace_ipi, 100);
  - }
  -}
  -
  -void arch_trigger_cpumask_backtrace(const cpumask_t *mask, bool exclude_self)
  -{
  - nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi);
  -}
  -- 
  2.7.4

  
  >>>

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

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


[Kernel-packages] [Bug 1762913] Re: [OPAL] Assert fail: core/mem_region.c:447:lock_held_by_me(>free_list_lock)

2018-04-11 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: Triaged => In Progress

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

Title:
  [OPAL] Assert fail:
  core/mem_region.c:447:lock_held_by_me(>free_list_lock)

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 - Application Cdeadmin  -
  2018-04-03 05:20:56 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-04-05 01:30:56 ==
  --- Comment From pridhiviraj 2018-04-05 01:30:25 EDT ---
  The disto needs 47712a921bb781caf69fca9eae43be19968816cb this level of 
commits need to be backported as suggested by Nick piggin.

  == Comment: #2 - PAWAN K. SINGH <> - 2018-04-06 03:35:49 ==
  which is 
  >>>

  From 47712a921bb781caf69fca9eae43be19968816cb Mon Sep 17 00:00:00 2001
  From: Nicholas Piggin 
  Date: Wed, 17 Jan 2018 22:47:22 +1000
  Subject: [PATCH] powerpc/watchdog: remove arch_trigger_cpumask_backtrace

  The powerpc NMI IPIs may not be recoverable if they are taken in
  some sections of code, and also there have been and still are issues
  with taking NMIs (in KVM guest code, in firmware, etc) which makes them
  a bit dangerous to use.

  Generic code like softlockup detector and rcu stall detectors really
  hammer on trigger_*_backtrace, which has lead to further problems
  because we've implemented it with the NMI.

  So stop providing NMI backtraces for now. Importantly, the powerpc code
  uses NMI IPIs in crash/debug, and the SMP hardlockup watchdog. So if the
  softlockup and rcu hang detection traces are not being printed because
  the CPU is stuck with interrupts off, then the hard lockup watchdog
  should get it with the NMI IPI.

  Fixes: 2104180a5369 ("powerpc/64s: implement arch-specific hardlockup 
watchdog")
  Signed-off-by: Nicholas Piggin 
  Signed-off-by: Michael Ellerman 
  ---
   arch/powerpc/include/asm/nmi.h |  4 
   arch/powerpc/kernel/watchdog.c | 22 --
   2 files changed, 26 deletions(-)

  diff --git a/arch/powerpc/include/asm/nmi.h b/arch/powerpc/include/asm/nmi.h
  index e97f586..9c80939 100644
  --- a/arch/powerpc/include/asm/nmi.h
  +++ b/arch/powerpc/include/asm/nmi.h
  @@ -4,10 +4,6 @@
   
   #ifdef CONFIG_PPC_WATCHDOG
   extern void arch_touch_nmi_watchdog(void);
  -extern void arch_trigger_cpumask_backtrace(const cpumask_t *mask,
  -bool exclude_self);
  -#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace
  -
   #else
   static inline void arch_touch_nmi_watchdog(void) {}
   #endif
  diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c
  index 87da80c..3963baa 100644
  --- a/arch/powerpc/kernel/watchdog.c
  +++ b/arch/powerpc/kernel/watchdog.c
  @@ -393,25 +393,3 @@ int __init watchdog_nmi_probe(void)
}
return 0;
   }
  -
  -static void handle_backtrace_ipi(struct pt_regs *regs)
  -{
  - nmi_cpu_backtrace(regs);
  -}
  -
  -static void raise_backtrace_ipi(cpumask_t *mask)
  -{
  - unsigned int cpu;
  -
  - for_each_cpu(cpu, mask) {
  - if (cpu == smp_processor_id())
  - handle_backtrace_ipi(NULL);
  - else
  - smp_send_nmi_ipi(cpu, handle_backtrace_ipi, 100);
  - }
  -}
  -
  -void arch_trigger_cpumask_backtrace(const cpumask_t *mask, bool exclude_self)
  -{
  - nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi);
  -}
  -- 
  2.7.4

  
  >>>

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

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


[Kernel-packages] [Bug 1762928] Re: [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

2018-04-11 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: Triaged => In Progress

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

Title:
  [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

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

Bug description:
  ---Problem Description---
  tm_trap_test failed on P8 compat mode [16.04.04 daily build as well bionic ] 
guests on a P9 host running bionic final beta version.
   
  Contact Information = srikanth/bssrika...@in.ibm.com 
   
  ---uname output---

  16.04.04 Guest running in P8compat mode:

  Linux guest 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:18:22 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  18.04 guest running in P8compat mode:
  Linux ubuntu 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Log into P9 Ubuntu 18.04 host, take console of guest 
`srikanth_ubuntu160404`
  2. Run TM selftests
  git clone --depth 1 https://github.com/torvalds/linux.git;cd 
linux/tools/testing/selftests/powerpc/;git log --oneline -1;make;make -C tm 
run_tests

  We will observe one of the tm tests failing, mentioned below:

  selftests: tm-trap
  
  test: tm_trap_test
  tags: git_version:c18bb39
  Little-Endian machine detected. Checking if endianness flips inadvertently on 
trap in TM... yes!
  failure: tm_trap_test
  not ok 1..11 selftests:  tm-trap [FAIL]

  
  Expected result: All tm selftests should have been pass on the P8 compat 
guest.. giventhat we had TM workaround patches in latest Ubuntu BIONIC host 
kernel
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for srikanth/bssrika...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.


  == Comment: #2 - SRIKANTH AITHAL  - 2018-04-10
  01:32:00 ==

  
  == Comment: #3 - SRIKANTH AITHAL  - 2018-04-10 
01:33:41 ==

  
  == Comment: #4 - SRIKANTH AITHAL  - 2018-04-10 
01:34:02 ==

  
  Please pick 

   `1c200e63d055 ("powerpc/tm: Fix endianness flip on trap")`

  ie. the commit that the test was written for

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

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


[Kernel-packages] [Bug 1762928] Re: [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

2018-04-11 Thread Joseph Salisbury
Bionic request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-April/091525.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/1762928

Title:
  [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

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

Bug description:
  ---Problem Description---
  tm_trap_test failed on P8 compat mode [16.04.04 daily build as well bionic ] 
guests on a P9 host running bionic final beta version.
   
  Contact Information = srikanth/bssrika...@in.ibm.com 
   
  ---uname output---

  16.04.04 Guest running in P8compat mode:

  Linux guest 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:18:22 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  18.04 guest running in P8compat mode:
  Linux ubuntu 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Log into P9 Ubuntu 18.04 host, take console of guest 
`srikanth_ubuntu160404`
  2. Run TM selftests
  git clone --depth 1 https://github.com/torvalds/linux.git;cd 
linux/tools/testing/selftests/powerpc/;git log --oneline -1;make;make -C tm 
run_tests

  We will observe one of the tm tests failing, mentioned below:

  selftests: tm-trap
  
  test: tm_trap_test
  tags: git_version:c18bb39
  Little-Endian machine detected. Checking if endianness flips inadvertently on 
trap in TM... yes!
  failure: tm_trap_test
  not ok 1..11 selftests:  tm-trap [FAIL]

  
  Expected result: All tm selftests should have been pass on the P8 compat 
guest.. giventhat we had TM workaround patches in latest Ubuntu BIONIC host 
kernel
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for srikanth/bssrika...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.


  == Comment: #2 - SRIKANTH AITHAL  - 2018-04-10
  01:32:00 ==

  
  == Comment: #3 - SRIKANTH AITHAL  - 2018-04-10 
01:33:41 ==

  
  == Comment: #4 - SRIKANTH AITHAL  - 2018-04-10 
01:34:02 ==

  
  Please pick 

   `1c200e63d055 ("powerpc/tm: Fix endianness flip on trap")`

  ie. the commit that the test was written for

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

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


[Kernel-packages] [Bug 1762913] Re: [OPAL] Assert fail: core/mem_region.c:447:lock_held_by_me(>free_list_lock)

2018-04-11 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: New => In Progress

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: High
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

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

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

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

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

Title:
  [OPAL] Assert fail:
  core/mem_region.c:447:lock_held_by_me(>free_list_lock)

Status in The Ubuntu-power-systems project:
  Triaged
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 - Application Cdeadmin  -
  2018-04-03 05:20:56 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-04-05 01:30:56 ==
  --- Comment From pridhiviraj 2018-04-05 01:30:25 EDT ---
  The disto needs 47712a921bb781caf69fca9eae43be19968816cb this level of 
commits need to be backported as suggested by Nick piggin.

  == Comment: #2 - PAWAN K. SINGH <> - 2018-04-06 03:35:49 ==
  which is 
  >>>

  From 47712a921bb781caf69fca9eae43be19968816cb Mon Sep 17 00:00:00 2001
  From: Nicholas Piggin 
  Date: Wed, 17 Jan 2018 22:47:22 +1000
  Subject: [PATCH] powerpc/watchdog: remove arch_trigger_cpumask_backtrace

  The powerpc NMI IPIs may not be recoverable if they are taken in
  some sections of code, and also there have been and still are issues
  with taking NMIs (in KVM guest code, in firmware, etc) which makes them
  a bit dangerous to use.

  Generic code like softlockup detector and rcu stall detectors really
  hammer on trigger_*_backtrace, which has lead to further problems
  because we've implemented it with the NMI.

  So stop providing NMI backtraces for now. Importantly, the powerpc code
  uses NMI IPIs in crash/debug, and the SMP hardlockup watchdog. So if the
  softlockup and rcu hang detection traces are not being printed because
  the CPU is stuck with interrupts off, then the hard lockup watchdog
  should get it with the NMI IPI.

  Fixes: 2104180a5369 ("powerpc/64s: implement arch-specific hardlockup 
watchdog")
  Signed-off-by: Nicholas Piggin 
  Signed-off-by: Michael Ellerman 
  ---
   arch/powerpc/include/asm/nmi.h |  4 
   arch/powerpc/kernel/watchdog.c | 22 --
   2 files changed, 26 deletions(-)

  diff --git a/arch/powerpc/include/asm/nmi.h b/arch/powerpc/include/asm/nmi.h
  index e97f586..9c80939 100644
  --- a/arch/powerpc/include/asm/nmi.h
  +++ b/arch/powerpc/include/asm/nmi.h
  @@ -4,10 +4,6 @@
   
   #ifdef CONFIG_PPC_WATCHDOG
   extern void arch_touch_nmi_watchdog(void);
  -extern void arch_trigger_cpumask_backtrace(const cpumask_t *mask,
  -bool exclude_self);
  -#define arch_trigger_cpumask_backtrace arch_trigger_cpumask_backtrace
  -
   #else
   static inline void arch_touch_nmi_watchdog(void) {}
   #endif
  diff --git a/arch/powerpc/kernel/watchdog.c b/arch/powerpc/kernel/watchdog.c
  index 87da80c..3963baa 100644
  --- a/arch/powerpc/kernel/watchdog.c
  +++ b/arch/powerpc/kernel/watchdog.c
  @@ -393,25 +393,3 @@ int __init watchdog_nmi_probe(void)
}
return 0;
   }
  -
  -static void handle_backtrace_ipi(struct pt_regs *regs)
  -{
  - nmi_cpu_backtrace(regs);
  -}
  -
  -static void raise_backtrace_ipi(cpumask_t *mask)
  -{
  - unsigned int cpu;
  -
  - for_each_cpu(cpu, mask) {
  - if (cpu == smp_processor_id())
  - handle_backtrace_ipi(NULL);
  - else
  - smp_send_nmi_ipi(cpu, handle_backtrace_ipi, 100);
  - }
  -}
  -
  -void arch_trigger_cpumask_backtrace(const cpumask_t *mask, bool exclude_self)
  -{
  - nmi_trigger_cpumask_backtrace(mask, exclude_self, raise_backtrace_ipi);
  -}
  -- 
  2.7.4

  
  >>>

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

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


[Kernel-packages] [Bug 1763067] Re: zvol_id throws ioctl_get_msg failed:Inappropriate ioctl for device

2018-04-11 Thread Colin Ian King
** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  zvol_id throws ioctl_get_msg failed:Inappropriate ioctl for device

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Symlinks in /dev/zvol are not created because /lib/udev/zvol_id
  crashes with ioctl_get_msg failed:Inappropriate ioctl for device.

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Running  linux-generic-hwe-16.04-edge
  4.15.0-13-generic

  zfsutils-linux 0.6.5.6-0ubuntu19

  The version of zvol_id in zfsutils-linux_0.7.5-1ubuntu14_amd64 works
  without error.

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

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


[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

2018-04-11 Thread Nobuto Murata
FWIW, kernel trace happens with the kernel in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/comments/77

But I will let it running anyway since I'm not sure if it affects to the
testing or not.


[5.999557] rtc_cmos 00:00: setting system clock to 2018-04-11 15:52:23 UTC 
(1523461943)
[5.999637] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[5.999637] EDD information not available.
[6.856436] clocksource: tsc: mask: 0x max_cycles: 
0x229834d6ac9, max_idle_ns: 440795285103 ns
[6.872996] Freeing unused kernel memory: 1844K (81f71000 - 
8213e000)
[6.885727] Write protecting the kernel read-only data: 14336k
[6.897566] Freeing unused kernel memory: 1964K (880001815000 - 
880001a0)
[6.911315] Freeing unused kernel memory: 272K (880001dbc000 - 
880001e0)
[6.924438] [ cut here ]
[6.934158] WARNING: CPU: 16 PID: 1 at 
/home/jsalisbury/bugs/lp1753662/v4.4/linux/arch/x86/mm/dump_pagetables.c:225 
note_page+0x649/0x840()
[6.958330] x86/mm: Found insecure W+X mapping at address 
8801/0x8801
[6.973431] Modules linked in:
[6.982498] CPU: 16 PID: 1 Comm: swapper/0 Not tainted 4.4.0-040400-generic 
#201803261439
[6.997629] Hardware name: Dell Inc. PowerEdge R730/072T6D, BIOS 2.5.5 
08/16/2017
[7.012149]   9d064fa9 883f6576fd48 
813da8d8
[7.026822]  883f6576fd90 883f6576fd80 8107ec52 
883f6576fe90
[7.041667]  8163 0004  

[7.056684] Call Trace:
[7.066183]  [] dump_stack+0x44/0x5c
[7.078824]  [] warn_slowpath_common+0x82/0xc0
[7.092586]  [] warn_slowpath_fmt+0x5c/0x80
[7.106139]  [] note_page+0x649/0x840
[7.119215]  [] ptdump_walk_pgd_level_core+0x2f9/0x430
[7.134087]  [] ptdump_walk_pgd_level_checkwx+0x17/0x20
[7.149121]  [] mark_rodata_ro+0xec/0x100
[7.162852]  [] ? rest_init+0x80/0x80
[7.176273]  [] kernel_init+0x1d/0xe0
[7.189752]  [] ret_from_fork+0x3f/0x70
[7.203505]  [] ? rest_init+0x80/0x80
[7.217134] ---[ end trace 43f75b6421b8d01c ]---
[7.235677] x86/mm: Checked W+X mappings: FAILED, 235610 W+X pages found.

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel 

[Kernel-packages] [Bug 1762928] Re: [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

2018-04-11 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: New => In Progress

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Critical
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

Title:
  [LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

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

Bug description:
  ---Problem Description---
  tm_trap_test failed on P8 compat mode [16.04.04 daily build as well bionic ] 
guests on a P9 host running bionic final beta version.
   
  Contact Information = srikanth/bssrika...@in.ibm.com 
   
  ---uname output---

  16.04.04 Guest running in P8compat mode:

  Linux guest 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:18:22 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  18.04 guest running in P8compat mode:
  Linux ubuntu 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Log into P9 Ubuntu 18.04 host, take console of guest 
`srikanth_ubuntu160404`
  2. Run TM selftests
  git clone --depth 1 https://github.com/torvalds/linux.git;cd 
linux/tools/testing/selftests/powerpc/;git log --oneline -1;make;make -C tm 
run_tests

  We will observe one of the tm tests failing, mentioned below:

  selftests: tm-trap
  
  test: tm_trap_test
  tags: git_version:c18bb39
  Little-Endian machine detected. Checking if endianness flips inadvertently on 
trap in TM... yes!
  failure: tm_trap_test
  not ok 1..11 selftests:  tm-trap [FAIL]

  
  Expected result: All tm selftests should have been pass on the P8 compat 
guest.. giventhat we had TM workaround patches in latest Ubuntu BIONIC host 
kernel
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for srikanth/bssrika...@in.ibm.com: 
  -Attach sysctl -a output output to the bug.


  == Comment: #2 - SRIKANTH AITHAL  - 2018-04-10
  01:32:00 ==

  
  == Comment: #3 - SRIKANTH AITHAL  - 2018-04-10 
01:33:41 ==

  
  == Comment: #4 - SRIKANTH AITHAL  - 2018-04-10 
01:34:02 ==

  
  Please pick 

   `1c200e63d055 ("powerpc/tm: Fix endianness flip on trap")`

  ie. the commit that the test was written for

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

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


[Kernel-packages] [Bug 1762986] Re: Display resolution of monitor via HDMI incorrectly identified

2018-04-11 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16


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

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

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

Title:
  Display resolution of monitor via HDMI incorrectly identified

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use a Philips BDM4037U 40'', 4k monitor.
  Connecting it via DP to my Lenovo 910 4k does work (except for random display 
blackouts).

  But when connecting it via HDMI the display resolution is sometimes
  correctly set (I cannot see a pattern when this works) but sometimes
  the display resolution is just set to FullHD, 1920x1080 Pixel @ 60Hz.

  Due to limitations of the supported HDMI protocol on my laptop I can
  only drive the display with 30Hz when in 4k mode. Which is totally
  fine for me. But this mode isn't correctly identified, most of the
  time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thet   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 12:00:28 2018
  HibernationDevice: RESUME=UUID=bedd1248-32dd-43ca-be9f-28337086ea86
  InstallationDate: Installed on 2018-04-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: LENOVO 80VF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=998520ff-c841-45ab-8312-2bb876ae2a0b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Agera
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 910-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80VF
  dmi.product.version: Lenovo YOGA 910-13IKB
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1762989] Re: Display Port issues - screen blackouts

2018-04-11 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16


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

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

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

Title:
  Display Port issues - screen blackouts

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I use a Philips BDM4037U 40'', 4k monitor.
  Connecting it via DP to my Lenovo 910 4k gives me random blackouts.

  It appears to me that this mostly happens after some time of work,
  also more likely when the CPU has to handle more than average load,
  sooner in 30Hz than in 60Hz mode. But it happens for sure after some
  time, each day.

  I was unsure if this is a problem with the monitor itself (although when 
connected via HDMI this isn't an issue).
  I found similar bug reports for Windows, where it was suggested to update the 
firmware.
  My laptop has updated everything - a current BIOS (which dates back to June 
2017 or so), updated Windows, latest Ubuntu.
  The same problem existed in 17.10, with x-org and Wayland sessions.

  Note, there is another issue with this monitor filed by me, but
  unrelated AFAIK:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762986

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thet   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 12:07:06 2018
  HibernationDevice: RESUME=UUID=bedd1248-32dd-43ca-be9f-28337086ea86
  InstallationDate: Installed on 2018-04-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: LENOVO 80VF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=998520ff-c841-45ab-8312-2bb876ae2a0b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Agera
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 910-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80VF
  dmi.product.version: Lenovo YOGA 910-13IKB
  dmi.sys.vendor: LENOVO

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

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


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

2018-04-11 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16


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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Error occurred on startup.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/7581/fd/1023: Permission denied
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm5478 F pulseaudio
cseeley6982 F pulseaudio
  Date: Wed Apr 11 08:58:24 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: vbox_crtc_mode_set+0x3f6/0x420 [vboxvideo] RSP: a116c553b8a0
  Failure: oops
  InstallationDate: Installed on 2018-02-28 (41 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180202)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=faff59a2-db4a-433c-adda-fa5829520ea1 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0070
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1763067] [NEW] zvol_id throws ioctl_get_msg failed:Inappropriate ioctl for device

2018-04-11 Thread Clint Armstrong
Public bug reported:

Symlinks in /dev/zvol are not created because /lib/udev/zvol_id crashes
with ioctl_get_msg failed:Inappropriate ioctl for device.

Description:Ubuntu 16.04.4 LTS
Release:16.04

Running  linux-generic-hwe-16.04-edge
4.15.0-13-generic

zfsutils-linux 0.6.5.6-0ubuntu19

The version of zvol_id in zfsutils-linux_0.7.5-1ubuntu14_amd64 works
without error.

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

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

Title:
  zvol_id throws ioctl_get_msg failed:Inappropriate ioctl for device

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Symlinks in /dev/zvol are not created because /lib/udev/zvol_id
  crashes with ioctl_get_msg failed:Inappropriate ioctl for device.

  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Running  linux-generic-hwe-16.04-edge
  4.15.0-13-generic

  zfsutils-linux 0.6.5.6-0ubuntu19

  The version of zvol_id in zfsutils-linux_0.7.5-1ubuntu14_amd64 works
  without error.

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

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


[Kernel-packages] [Bug 1763062] [NEW] LSM stacking patches for bionic

2018-04-11 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

LSM stacking patches for bionic

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

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


** Tags: bionic

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

Title:
  LSM stacking patches for bionic

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  LSM stacking patches for bionic

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

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


[Kernel-packages] [Bug 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el

2018-04-11 Thread Joseph Salisbury
** Tags removed: kernel-key

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

Title:
  [regression] bionic 4.15.0-13-generic panics on qemu ppc64el

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

Bug description:
  When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel
  panics before initrd.  Going back to xenial 4.4.0 works correctly.

  linux-image-4.15.0-13-generic:
Installed: 4.15.0-13.14
Candidate: 4.15.0-13.14
Version table:
   *** 4.15.0-13.14 500
  500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main 
ppc64el Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic ppc64le
  .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 16:11 seq
   crw-rw 1 root audio 116, 33 Apr  5 16:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: ppc64el
  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:
  Date: Thu Apr  5 16:13:28 2018
  HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic 
root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro
  ProcLoadAvg: 3.04 2.18 0.92 3/119 1643
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1225 00:12:470 0 EOF
   2: POSIX  ADVISORY  WRITE 841 00:12:459 0 EOF
   3: FLOCK  ADVISORY  WRITE 832 00:12:449 0 EOF
   4: POSIX  ADVISORY  WRITE 802 00:12:432 0 EOF
   5: POSIX  ADVISORY  WRITE 350 00:12:294 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/vda3   partition1408960 0   -1
  ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP 
Mon Apr 2 16:08:02 UTC 2018
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-119-generic N/A
   linux-backports-modules-4.4.0-119-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago)
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

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


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

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

apport-collect 1763062

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: bionic

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

Title:
  LSM stacking patches for bionic

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  LSM stacking patches for bionic

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

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


[Kernel-packages] [Bug 1734130] Re: [18.04 FEAT] Add kvm_stat from kernel tree

2018-04-11 Thread Joseph Salisbury
** Tags removed: kernel-key

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

Title:
  [18.04 FEAT] Add kvm_stat from kernel tree

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Improves RAS characterics of systems running KVM by providing kvm_stat script:
  https://github.com/torvalds/linux/tree/master/tools/kvm/kvm_stat

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

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


[Kernel-packages] [Bug 1759787] Re: Very inaccurate TSC clocksource on HP ProLiant DL380 Gen10 with kernel 4.13

2018-04-11 Thread Joseph Salisbury
** Tags removed: kernel-key
** Tags added: kernel-da-key

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

Title:
  Very inaccurate TSC clocksource on HP ProLiant DL380 Gen10 with kernel
  4.13

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

Bug description:
  On kernel 4.13.0-37-generic, HP ProLiant DL380 Gen10 systems have been
  observed with very large clock offsets, as measured by NTP.  Over the
  past few days on one of our production systems, we've used 3 different
  kernels: https://pastebin.ubuntu.com/p/nDkkgRqdtv/

  All of these kernels default to the TSC clocksource, which is supposed
  to be very reliable on Skylake-X CPUs.  On 4.4 (linux-image-generic-
  lts-xenial) it works as expected; on 3.13 (trusty default kernel) it
  works a little worse, and on 4.13 (linux-image-generic-hwe-16.04) it
  is much worse.  Today I switched 4.13 from the TSC clocksource to the
  HPET clocksource and it improved the situation dramatically.

  I've produced loopstats & peerstats graphs from NTP corresponding to
  the dates in the pastebin above and placed them at
  https://people.canonical.com/~paulgear/ntp/.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: User Name 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 27 18:26 seq
   crw-rw 1 root audio 116, 33 Mar 27 18:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [ 6280.259121] perf: interrupt took too long (2505 > 2500), lowering 
kernel.perf_event_max_sample_rate to 79750
   [10463.378558] perf: interrupt took too long (3133 > 3131), lowering 
kernel.perf_event_max_sample_rate to 63750
   [32314.949747] perf: interrupt took too long (4000 > 3916), lowering 
kernel.perf_event_max_sample_rate to 5
   [129804.100274] clocksource: Switched to clocksource hpet
   [132747.312089] perf: interrupt took too long (5004 > 5000), lowering 
kernel.perf_event_max_sample_rate to 39750
  Date: Thu Mar 29 07:45:22 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 0bda:0329 Realtek Semiconductor Corp. 
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 0424:2660 Standard Microsystems Corp. Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HPE ProLiant DL380 Gen10
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=b33fdcbd-a949-41a0-86d2-03d0c6808284 ro console=tty0 
console=ttyS0,115200
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 02/15/2018
  dmi.bios.vendor: HPE
  dmi.bios.version: U30
  dmi.board.name: ProLiant DL380 Gen10
  dmi.board.vendor: HPE
  dmi.chassis.type: 23
  dmi.chassis.vendor: HPE
  dmi.modalias: 
dmi:bvnHPE:bvrU30:bd02/15/2018:svnHPE:pnProLiantDL380Gen10:pvr:rvnHPE:rnProLiantDL380Gen10:rvr:cvnHPE:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL380 Gen10
  dmi.sys.vendor: HPE

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

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


  1   2   >