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

2018-05-08 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 1770073

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

Title:
  4.15.0-20 kernel bug, not found Ethernet controller RTL8111/8168/8411

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Release Linux Mint 18.3 Sylvia 64-bit, MATE 1.18.0

  >sudo lspci -vnvn
  05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
   Subsystem: ASRock Incorporation Motherboard (one of many) [1849:8168]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770073/+subscriptions

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


[Kernel-packages] [Bug 1770073] [NEW] 4.15.0-20 kernel bug, not found Ethernet controller RTL8111/8168/8411

2018-05-08 Thread Dmitry
Public bug reported:

Release Linux Mint 18.3 Sylvia 64-bit, MATE 1.18.0

>sudo lspci -vnvn
05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
 Subsystem: ASRock Incorporation Motherboard (one of many) [1849:8168]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- sudo lspci -vnvn
  05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
-   Subsystem: ASRock Incorporation Motherboard (one of many) [1849:8168]
-   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
-   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- sudo lspci -vnvn
  05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
   Subsystem: ASRock Incorporation Motherboard (one of many) [1849:8168]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1770073

Title:
  4.15.0-20 kernel bug, not found Ethernet controller RTL8111/8168/8411

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Release Linux Mint 18.3 Sylvia 64-bit, MATE 1.18.0

  >sudo lspci -vnvn
  05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
   Subsystem: ASRock Incorporation Motherboard (one of many) [1849:8168]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770073/+subscriptions

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


[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

2018-05-08 Thread ChristianEhrhardt
Hmm,
so it is not even burning CPU for anything neither in the Host (usr ~=qemu, sys 
~=kernel) nor in the guest itself (~=guest).
The KVM exits confirm that, it doesn't do a a lot entry/exit is the pass in/out 
of guest context and the only meaningful exit means it emulates an instruction.

So if it is not hogged on a CPU it is waiting for something.
Unfortunately this is too windows and x86-arch specific for me to read,
even if you get the info. BTW getting the info what instructions it is
spinning on can be done via [1] - this might be helpful for others
coming by to help. To bad that I still can't reproduce that locally :-/,
but at least I haven't heard of anyone else hitting this yet so it must
be sort of special to maybe your guest?

Especially I can't see yet how a host kernel update would trigger this :-/
Sorry, but this is up for the kernel Team to consider the changes that happened 
between those versions in regard to this issue.

[1]: https://lkml.org/lkml/2012/6/27/241

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

Title:
  Kernel 4.4.0-122 Breaks qemu-system-x86

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu-
  system-x86: black screen displays and qemu-system-x86 runs at 100% cpu
  indefinitely. Boot the same system with kernel 4.4.0-119 and qemu-
  system-x86 works fine running a Windows 10 VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic i686
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sun Apr 29 15:58:25 2018
  InstallationDate: Installed on 2014-04-29 (1460 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0   394 2  0.0 [kvm-irqfd-clean]
  MachineType: Dell Inc. Inspiron 518
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic 
root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash 
nmi_watchdog=0
  SourcePackage: qemu
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago)
  dmi.bios.date: 03/30/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.8
  dmi.board.name: 0K068D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 518
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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


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

2018-05-08 Thread bugproxy
--- Comment From p...@au1.ibm.com 2018-05-09 00:25 EDT---
Is it essential to have two NUMA nodes for the guest memory to see this bug? 
Can we reproduce it without the NUMA node stuff in the xml?

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running
  with IO stress crashed@security_file_permission+0xf4/0x160.

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

Bug description:
  Problem Description: Migration Guest running with IO stress
  crashed@security_file_permission+0xf4/0x160 after couple of
  migrations.

  Steps to re-create:

  Source host - boslcp3
  Destination host - boslcp4

  1.boslcp3 & boslcp4 installed with latest kernel
  root@boslcp3:~# uname -a
  Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:~#

  root@boslcp4:~# uname -a
  Linux boslcp4 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:~#

  2. Installed guest boslcp3g1 with kernel and started LTP run from
  boslcp3 host

  root@boslcp3g1:~# uname -a
  Linux boslcp3g1 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux

  3. Started migrating boslcp3g1 guest from source to destination & viceversa.
  4. After couple of migrations it crashed at boslcp4 & enters into xmon

  8:mon> t
  [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160
  [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120
  [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0
  [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110
  [c004f8a23e30] c000b184 system_call+0x58/0x6c
  --- Exception: c01 (System Call) at 71f1779fe280
  SP (7fffe99ece50) is in userspace
  8:mon> S
  msr= 80001033  sprg0 = 
  pvr= 004e1202  sprg1 = c7a85800
  dec= 591e3e03  sprg2 = c7a85800
  sp = c004f8a234a0  sprg3 = 00010008
  toc= c16eae00  dar   = 023c
  srr0   = c00c355c  srr1  = 80001033 dsisr  = 4000
  dscr   =   ppr   = 0010 pir= 0011
  amr=   uamor = 
  dpdes  =   tir   =  cir= 
  fscr   = 05000180  tar   =  pspb   = 
  mmcr0  = 8000  mmcr1 =  mmcr2  = 
  pmc1   =  pmc2 =   pmc3 =   pmc4   = 
  mmcra  =    siar =  pmc5   = 026c
  sdar   =    sier =  pmc6   = 0861
  ebbhr  =   ebbrr =  bescr  = 
  iamr   = 4000
  pidr   = 0034  tidr  = 
  cpu 0x8: Vector: 700 (Program Check) at [c004f8a23220]
  pc: c00e4854: xmon_core+0x1f24/0x3520
  lr: c00e4850: xmon_core+0x1f20/0x3520
  sp: c004f8a234a0
     msr: 80041033
    current = 0xc004f89faf00
    paca= 0xc7a85800   softe: 0irq_happened: 0x01
  pid   = 24028, comm = top
  Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 (Ubuntu 
4.15.0-20.21-generic 4.15.17)
  cpu 0x8: Exception 700 (Program Check) in xmon, returning to main loop
  [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160
  [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120
  [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0
  [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110
  [c004f8a23e30] c000b184 system_call+0x58/0x6c
  --- Exception: c01 (System Call) at 71f1779fe280
  SP (7fffe99ece50) is in userspace
  8:mon> r
  R00 = c043b7fc   R16 = 
  R01 = c004f8a23c90   R17 = ff70
  R02 = c16eae00   R18 = 0a51b4bebfc8
  R03 = c00279557200   R19 = 7fffe99edbb0
  R04 = c003242499c0   R20 = 0a51b4c04db0
  R05 = 0002   R21 = 0a51b4c20e90
  R06 = 0004   R22 = 00040f00
  R07 = ff81   R23 = 0a51b4c06560
  R08 = ff80   R24 = ff80
  R09 =    R25 = 0a51b4bec2b8
  R10 =    R26 = 71f177bb0b20
  R11 =    R27 = 
  R12 = 2000   R28 = c00279557200
  R13 = c7a85800   R29 = c004c7734210
  R14 =    R30 = 
  R15 =    R31 = c003242499c0
  pc  = c043b808 __fsnotify_parent+0x88/0x1a0
  cfar= 

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

2018-05-08 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 1702666

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

Title:
  [Dell Precision 7720] Unable to change brightness on this I+A laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When you press the hotkey to adjust the screen brightness, the
  brightness level indicator will change accordingly, but the actual
  brightness does not.

  And from watching the brightness file in
  /sys/class/backlight/amdgpu_bl0, when the brightness control hotkey
  was pressed, it will change the value here (1~255).

  $ ls /sys/class/backlight/
  amdgpu_bl0  intel_backlight

  This issue existed since 16.04.2 + 4.8 HWE kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-27-generic 4.10.0-27.30~16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Thu Jul  6 06:37:41 2017
  InstallationDate: Installed on 2017-07-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170209)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1754621] Re: Builtin touchpad is not seen in 'DELL Latitude E5550' after the reboot during update.

2018-05-08 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/1754621

Title:
  Builtin touchpad is not seen in 'DELL Latitude E5550' after the reboot
  during update.

Status in linux package in Ubuntu:
  Expired

Bug description:
  After an unexpected reboot, cursor disappeared. The only thing, which
  helped -- typing

  gsettings set org.gnome.settings-daemon.plugins.cursor active false

  and rebooting again. However, cursor now doesn't move with a touchpad.
  I have found this https://wiki.ubuntu.com/DebuggingTouchpadDetection.
  I have checked, if cursor moves with a mouse and it does. And there's
  no touchpad in /proc/bus/input/devices. So, I was recommended there to
  put it here as a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-143-generic 3.13.0-143.192
  ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-143-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Mar  9 13:37:03 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  HibernationDevice: RESUME=UUID=84feb423-aad7-4d48-bf01-2631937bc0e2
  InstallationDate: Installed on 2016-04-22 (685 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Latitude E5550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-143-generic 
root=UUID=c6bfbf1a-d3f5-4a1b-9de8-728f56bc9c6d ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 
video.use_native_backlight=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-143-generic N/A
   linux-backports-modules-3.13.0-143-generic  N/A
   linux-firmware  1.127.24
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0THWR2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/11/2016:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0THWR2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5550
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1753304] Re: No Internet when waking from suspend

2018-05-08 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/1753304

Title:
  No Internet when waking from suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ever since I updated my computer later last week I have had no
  internet access after waking from a suspend. This is all I get as a
  response to these ping commands:

  $ ping google.ca
  PING google.ca (216.58.217.195) 56(84) bytes of data.

  $ ping 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

  localhost works, and I am still able to login to my router over
  wireless. No other computer or phone in my house has any problem with
  the internet, so the problem is specific only to my computer and only
  after the software update.

  the nm-applet is alive and I am able to see the wireless connections
  available to me. If I reconnect to the wifi connection it makes no
  difference.

  If I run "sudo service network-manager restart" it also makes no
  difference.

  The only solution I have found so far to fix the problem is to
  completely restart the computer.

  Any help or advice would be appreciated. If I missed some valuable
  information let me know and I will come back with more info.

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

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


[Kernel-packages] [Bug 1702666] Re: [Dell Precision 7720] Unable to change brightness on this I+A laptop

2018-05-08 Thread Kai-Heng Feng
This should be fixed in latest gnome-settings-daemon.

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

Title:
  [Dell Precision 7720] Unable to change brightness on this I+A laptop

Status in linux package in Ubuntu:
  New

Bug description:
  When you press the hotkey to adjust the screen brightness, the
  brightness level indicator will change accordingly, but the actual
  brightness does not.

  And from watching the brightness file in
  /sys/class/backlight/amdgpu_bl0, when the brightness control hotkey
  was pressed, it will change the value here (1~255).

  $ ls /sys/class/backlight/
  amdgpu_bl0  intel_backlight

  This issue existed since 16.04.2 + 4.8 HWE kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-27-generic 4.10.0-27.30~16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Thu Jul  6 06:37:41 2017
  InstallationDate: Installed on 2017-07-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170209)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1769421] Re: [18.04] [Bionic]drm_kms_helper causes long delay at boot

2018-05-08 Thread Scott Testerman
apport information

** Tags added: apport-collected

** Description changed:

  System upgraded from 16.04 to 18.04 experiences long delays at boot --
  generally 4-5 minutes.  The same system experienced no significant
  delays prior to the upgrade.  dmesg reports problems with
  drm_kms_helper.
  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  linux-generic:
Installed: 4.15.0.20.23
Candidate: 4.15.0.20.23
Version table:
   *** 4.15.0.20.23 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  
  Expected to happen:
  System boots in reasonable amount of time, consistent with prior LTS release.
  
  What happened:
  System is very slow to boot, on the order of several minutes to reach a login 
screen.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.20.23
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1012 F pulseaudio
scott  2346 F pulseaudio
  Date: Sat May  5 23:19:14 2018
  HibernationDevice: RESUME=UUID=a816bb7e-ab3e-49ea-9bbe-0f1d0e016b0e
  InstallationDate: Installed on 2017-09-05 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 0769AK8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=a3217eb0-fa66-4420-9eb3-5f3a38cb1af0 ro splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET37WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET37WW:bd07/29/2008:svnLENOVO:pn0769AK8:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 0769AK8
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-09-05 (245 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ Tags:  bionic
+ Uname: Linux 4.17.0-041700rc4-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

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

Title:
  [18.04] [Bionic]drm_kms_helper causes long delay at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System upgraded from 16.04 to 18.04 experiences long delays at boot --
  generally 4-5 minutes.  The same system experienced no significant
  delays prior to the upgrade.  dmesg reports problems with
  drm_kms_helper.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  linux-generic:
Installed: 4.15.0.20.23
Candidate: 4.15.0.20.23
Version table:
   *** 4.15.0.20.23 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected to happen:
  System boots in reasonable amount of time, consistent with prior LTS release.

  What happened:
  System is very slow to boot, on the order of several minutes to reach a login 
screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.20.23
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1012 F pulseaudio
scott  

[Kernel-packages] [Bug 1769421] Re: [18.04] [Bionic]drm_kms_helper causes long delay at boot

2018-05-08 Thread Scott Testerman
With mainline kernel 4.17rc4, flip_done is still timing out, so it's
exactly the same behavior as the 18.04LTS kernel.

** Attachment added: "dmesg from mainline kernel 4.17.0-041700rc4"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769421/+attachment/5136521/+files/dmesg-mainline-4.17.0-041700rc4-generic.txt

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

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

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

Title:
  [18.04] [Bionic]drm_kms_helper causes long delay at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System upgraded from 16.04 to 18.04 experiences long delays at boot --
  generally 4-5 minutes.  The same system experienced no significant
  delays prior to the upgrade.  dmesg reports problems with
  drm_kms_helper.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  linux-generic:
Installed: 4.15.0.20.23
Candidate: 4.15.0.20.23
Version table:
   *** 4.15.0.20.23 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected to happen:
  System boots in reasonable amount of time, consistent with prior LTS release.

  What happened:
  System is very slow to boot, on the order of several minutes to reach a login 
screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-generic 4.15.0.20.23
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1012 F pulseaudio
scott  2346 F pulseaudio
  Date: Sat May  5 23:19:14 2018
  HibernationDevice: RESUME=UUID=a816bb7e-ab3e-49ea-9bbe-0f1d0e016b0e
  InstallationDate: Installed on 2017-09-05 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 0769AK8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=a3217eb0-fa66-4420-9eb3-5f3a38cb1af0 ro splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 68ET37WW
  dmi.board.name: IEL10
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr68ET37WW:bd07/29/2008:svnLENOVO:pn0769AK8:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 0769AK8
  dmi.product.version: 3000 N200
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (245 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.0-041700rc4-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1752044] Re: Update Qualcomm QCA6174-HMC (DW1820) to comply with CE-RED (Radio Emissions Directive)

2018-05-08 Thread AceLan Kao
** Tags added: verification-done-xenial

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

Title:
  Update Qualcomm QCA6174-HMC (DW1820) to comply with CE-RED (Radio
  Emissions Directive)

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Bionic:
  Fix Released

Bug description:
  SRU Justification

  Impact: New ath10k firmware is needed for compliance with CE-RED.

  Fix: Updated firmware files.

  Regression Potential: This update has been in upstream linux-firmware
  for a while now. While regressions are possible, the firmware should
  have seen a lot of use by now.

  ---

  To comply with CE-RED (Radio Emissions Directive),
  ath10k/QCA6174/hw3.0/board-2.bin and
  ath10k/QCA6174/hw3.0/firmware-6.bin have to be updated.

  The commits are:

  commit 1d1dd4be21cde408b0fb12774d477293bc8d4cc2
  Author: Kalle Valo 
  AuthorDate: Thu Feb 15 15:10:51 2018 +0200
  Commit: Kalle Valo 
  CommitDate: Thu Feb 15 15:10:51 2018 +0200

  ath10k: QCA6174 hw3.0: update board-2.bin

  Signed-off-by: Kalle Valo 

  commit 6f1d3b7cfeef426f3c3d79bf916e3bef8f82a3dc
  Author: Kalle Valo 
  AuthorDate: Thu Feb 15 15:10:51 2018 +0200
  Commit: Kalle Valo 
  CommitDate: Thu Feb 15 15:10:51 2018 +0200

  ath10k: QCA6174 hw3.0: update firmware-6.bin to
  WLAN.RM.4.4.1-00079-QCARMSWPZ-1

  Signed-off-by: Kalle Valo 

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

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


[Kernel-packages] [Bug 1764645] Re: Bluetooth not working

2018-05-08 Thread Edison Wong
After today `apt update && apt -y full-upgrade`, my bluetooth mouse
works again with `vanilla-gnome-desktop` ;-)

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

Title:
  Bluetooth not working

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

Bug description:
  I've installed the Ubuntu Bionic Beta 2 and everything works fine but
  the bluetooth (perfectly working with Xenial). In bluetooth control
  panel the slider is impossible to move to "on".

  1) Ubuntu Release (via 'lsb_release -rd')
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) Version of package (apt-cache policy gnome-bluetooth)
  gnome-bluetooth:
Installato: 3.28.0-2
Candidato:  3.28.0-2
Tabella versione:
   *** 3.28.0-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  I expected to switch on the bluetooth.

  4) What happened instead
  Bluetooth won't switch on.

  5) Output of rfkill list is:
  0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
  1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

  6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
  03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless 
  Network Adapter [168c:0034] (rev 01)
  Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- 
  size Mini PCIe Card [1a56:2003]
  Kernel driver in use: ath9k
  Kernel modules: ath9k
  04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit 
  Ethernet [1969:10a1] (rev 10)
  Bus 002 Device 002: ID 8087:8000 Intel Corp. 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:8008 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd 
  Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. 
   
  AR3012 Bluetooth 4.0
  Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. 
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [   17.715399] Bluetooth: Core ver 2.22
  [   17.715414] Bluetooth: HCI device and connection manager initialized
  [   17.715416] Bluetooth: HCI socket layer initialized
  [   17.715418] Bluetooth: L2CAP socket layer initialized
  [   17.715422] Bluetooth: SCO socket layer initialized
  [   17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
  [   18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   18.600649] Bluetooth: BNEP filters: protocol multicast
  [   18.600651] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stormy 1484 F pulseaudio
   /dev/snd/controlC0:  stormy 1484 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 08:46:30 2018
  HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: ASUSTeK COMPUTER INC. G750JH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G750JH.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G750JH
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG750JH.206:bd12/02/2013:svnASUSTeKCOMPUTERINC.:pnG750JH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G750JH
  dmi.product.version: 1.0
  

[Kernel-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0%

2018-05-08 Thread Daniel van Vugt
Please try some different kernels, old and new:

http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

and tell us which ones work and which don't.

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

2018-05-08 Thread Skipper
sudo pidstat -t -p 4063
Linux 4.4.0-124-generic (desktop)   05/08/2018  _i686_  (2 CPU)

09:43:39 PM   UID  TGID   TID%usr %system  %guest%CPU   CPU  
Command
09:43:39 PM  1000  4063 -0.013.010.013.04 1  
qemu-system-i38
09:43:39 PM  1000 -  40630.020.000.000.02 1  
|__qemu-system-i38
09:43:39 PM  1000 -  40640.000.000.000.00 1  
|__qemu-system-i38
09:43:39 PM  1000 -  40660.003.010.013.02 0  
|__qemu-system-i38
09:43:39 PM  1000 -  40680.000.000.000.00 1  
|__qemu-system-i38


sudo perf stat -e 'kvm:*' -a sleep 1h
^Csleep: Interrupt

 Performance counter stats for 'system wide':

 4,221,248  kvm:kvm_entry   
  (100.00%)
 0  kvm:kvm_hypercall   
  (100.00%)
 0  kvm:kvm_hv_hypercall
  (100.00%)
 0  kvm:kvm_pio 
  (100.00%)
 0  kvm:kvm_fast_mmio   
  (100.00%)
 0  kvm:kvm_cpuid   
  (100.00%)
 0  kvm:kvm_apic
  (100.00%)
 4,222,925  kvm:kvm_exit
  (100.00%)
 0  kvm:kvm_inj_virq
  (100.00%)
 0  kvm:kvm_inj_exception   
  (100.00%)
 0  kvm:kvm_page_fault  
  (100.00%)
 0  kvm:kvm_msr 
  (100.00%)
 0  kvm:kvm_cr  
  (100.00%)
 0  kvm:kvm_pic_set_irq 
  (100.00%)
 0  kvm:kvm_apic_ipi
  (100.00%)
 0  kvm:kvm_apic_accept_irq 
  (100.00%)
 0  kvm:kvm_eoi 
  (100.00%)
 0  kvm:kvm_pv_eoi  
  (100.00%)
 0  kvm:kvm_nested_vmrun
  (100.00%)
 0  kvm:kvm_nested_intercepts   
  (100.00%)
 0  kvm:kvm_nested_vmexit   
  (100.00%)
 0  kvm:kvm_nested_vmexit_inject
 (100.00%)
 0  kvm:kvm_nested_intr_vmexit  
   (100.00%)
 0  kvm:kvm_invlpga 
  (100.00%)
 0  kvm:kvm_skinit  
  (100.00%)
   169,094,024  kvm:kvm_emulate_insn
  (100.00%)
 0  kvm:vcpu_match_mmio 
  (100.00%)
 0  kvm:kvm_write_tsc_offset
  (100.00%)
 0  kvm:kvm_pml_full
  (100.00%)
 0  kvm:kvm_ple_window  
  (100.00%)
 0  kvm:kvm_pvclock_update  
  (100.00%)
 0  kvm:kvm_wait_lapic_expire   
  (100.00%)
 0  kvm:kvm_enter_smm   
  (100.00%)
 0  kvm:kvm_pi_irte_update  
  (100.00%)
 0  kvm:kvm_userspace_exit  
  (100.00%)
 0  kvm:kvm_vcpu_wakeup 
  (100.00%)
 0  kvm:kvm_set_irq 
  (100.00%)
 0  kvm:kvm_ioapic_set_irq  
  (100.00%)
 0  kvm:kvm_ioapic_delayed_eoi_inj  
   (100.00%)
 0  kvm:kvm_msi_set_irq 
  (100.00%)
 0  kvm:kvm_ack_irq 
  (100.00%)
 0  kvm:kvm_mmio
  (100.00%)
 0  kvm:kvm_fpu 
  (100.00%)
 0  kvm:kvm_age_page   

[Kernel-packages] [Bug 1768115] (FIXED) Traces of QEMU RAM migrations relative to dirty bitmap syncing

2018-05-08 Thread bugproxy
--- Comment on attachment From mdr...@us.ibm.com 2018-05-08 21:27 EDT---


Please disregard previous attachment, the traces were from the previous 
(unrelated) migration.

** Attachment added: "(FIXED) Traces of QEMU RAM migrations relative to dirty 
bitmap syncing"
   
https://bugs.launchpad.net/bugs/1768115/+attachment/5136476/+files/vm0.log.iteration2a.boslcp6.success.postmigrate.trimmed-fixed

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running
  with IO stress crashed@security_file_permission+0xf4/0x160.

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

Bug description:
  Problem Description: Migration Guest running with IO stress
  crashed@security_file_permission+0xf4/0x160 after couple of
  migrations.

  Steps to re-create:

  Source host - boslcp3
  Destination host - boslcp4

  1.boslcp3 & boslcp4 installed with latest kernel
  root@boslcp3:~# uname -a
  Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:~#

  root@boslcp4:~# uname -a
  Linux boslcp4 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:~#

  2. Installed guest boslcp3g1 with kernel and started LTP run from
  boslcp3 host

  root@boslcp3g1:~# uname -a
  Linux boslcp3g1 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux

  3. Started migrating boslcp3g1 guest from source to destination & viceversa.
  4. After couple of migrations it crashed at boslcp4 & enters into xmon

  8:mon> t
  [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160
  [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120
  [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0
  [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110
  [c004f8a23e30] c000b184 system_call+0x58/0x6c
  --- Exception: c01 (System Call) at 71f1779fe280
  SP (7fffe99ece50) is in userspace
  8:mon> S
  msr= 80001033  sprg0 = 
  pvr= 004e1202  sprg1 = c7a85800
  dec= 591e3e03  sprg2 = c7a85800
  sp = c004f8a234a0  sprg3 = 00010008
  toc= c16eae00  dar   = 023c
  srr0   = c00c355c  srr1  = 80001033 dsisr  = 4000
  dscr   =   ppr   = 0010 pir= 0011
  amr=   uamor = 
  dpdes  =   tir   =  cir= 
  fscr   = 05000180  tar   =  pspb   = 
  mmcr0  = 8000  mmcr1 =  mmcr2  = 
  pmc1   =  pmc2 =   pmc3 =   pmc4   = 
  mmcra  =    siar =  pmc5   = 026c
  sdar   =    sier =  pmc6   = 0861
  ebbhr  =   ebbrr =  bescr  = 
  iamr   = 4000
  pidr   = 0034  tidr  = 
  cpu 0x8: Vector: 700 (Program Check) at [c004f8a23220]
  pc: c00e4854: xmon_core+0x1f24/0x3520
  lr: c00e4850: xmon_core+0x1f20/0x3520
  sp: c004f8a234a0
     msr: 80041033
    current = 0xc004f89faf00
    paca= 0xc7a85800   softe: 0irq_happened: 0x01
  pid   = 24028, comm = top
  Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 (Ubuntu 
4.15.0-20.21-generic 4.15.17)
  cpu 0x8: Exception 700 (Program Check) in xmon, returning to main loop
  [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160
  [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120
  [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0
  [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110
  [c004f8a23e30] c000b184 system_call+0x58/0x6c
  --- Exception: c01 (System Call) at 71f1779fe280
  SP (7fffe99ece50) is in userspace
  8:mon> r
  R00 = c043b7fc   R16 = 
  R01 = c004f8a23c90   R17 = ff70
  R02 = c16eae00   R18 = 0a51b4bebfc8
  R03 = c00279557200   R19 = 7fffe99edbb0
  R04 = c003242499c0   R20 = 0a51b4c04db0
  R05 = 0002   R21 = 0a51b4c20e90
  R06 = 0004   R22 = 00040f00
  R07 = ff81   R23 = 0a51b4c06560
  R08 = ff80   R24 = ff80
  R09 =    R25 = 0a51b4bec2b8
  R10 =    R26 = 71f177bb0b20
  R11 =    R27 = 
  R12 = 2000   R28 = c00279557200
  R13 = 

[Kernel-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

2018-05-08 Thread Launchpad Bug Tracker
This bug was fixed in the package alsa-lib - 1.1.6-1ubuntu1

---
alsa-lib (1.1.6-1ubuntu1) cosmic; urgency=medium

  * 
debian/patches/0008-ucm-adding-the-folder-of-card_long_name-when-finding.patch
  * debian/patches/0009-conf-ucm-increase-the-input-volume-for-LineIn.patch
 - Backport 2 patches to make audio work on Lenovo machines with dual 
codecs.
   (LP: #1768830)

 -- Hui Wang   Tue, 08 May 2018 03:28:26 +

** Changed in: alsa-lib (Ubuntu)
   Status: New => Fix Released

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  New

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  SRU Document:

  [Impact]

  We have several Lenovo machines like Lenovo P520 which have 2 analogue
  audio codecs on them, the internal speaker and front headset are
  connected to the 1st codec, the Rear mic, Line in and Line out are
  connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
  lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
  front headset) on the 1st codec can work. To make all audio devices
  work on this machine, upstream provided 3 patches for kernel audio
  driver and 5 patches for alsa-lib. The kernel patches are already in
  the linux-4.12, so this is not a problem anymore under 18.04 since we
  use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to
  backport them to v1.1.3-5, the 5 patches are list as below:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
  4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
  181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
  81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)

  Some explanation for these 5 patches, to make the audio work, the
  alsa-lib needs to add an audio configuration file and verb conf file
  for lenovo machines with dual codecs, these two files are put in a
  folder named by card_long_name, and the name of configuration file
  itself is also named by card_long_name, this is implemented by the
  patches of NO. 3rd and 5th.

  But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
   
  [Test Case]

  On the Lenovo machines with dual codecs (p520), I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can find the conf file and can parse the conf file
  successfully, and I tested the internal speaker, front headset, rear
  mic, line out and line in, all audio devices work well.

  On a HP and Dell machines without dual codecs, I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can't find conf file by card_long_name and card_name, the
  pulseaudio will drive the sound card as before, so all audio functions
  worked well as before.

  [Regression Potential]

  After adding these 5 patches, there 2 two changes introduced into the
  alsa-lib v1.1.3-5ubuntu1:

  1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
  2) before: the ucm parser will search the conf file/folder by card_name only; 
 after: the ucm parser will search the conf file/foler by card_long_name first, 
if it fails, it will fallback to use card_name to search again. So this change 
is compatible with old version.

  There is no regression since there is only one folder named by
  card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with
  dual codecs, it will find the conf file by card_long_name, if it runs
  on other machines, the search by card_long_name will definitely fail
  and fall back to search by card_name, then it will be same as before.
  So the objective of these 5 patches is to let lenovo machines with
  dual codecs find the conf file 

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

2018-05-08 Thread Skipper
qemu-system-x86 broken when running kernel 4.4.0-124 as well - same
result (black screen displays and qemu-system-x86 runs at 100% cpu
indefinitely).

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

Title:
  Kernel 4.4.0-122 Breaks qemu-system-x86

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu-
  system-x86: black screen displays and qemu-system-x86 runs at 100% cpu
  indefinitely. Boot the same system with kernel 4.4.0-119 and qemu-
  system-x86 works fine running a Windows 10 VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic i686
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sun Apr 29 15:58:25 2018
  InstallationDate: Installed on 2014-04-29 (1460 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0   394 2  0.0 [kvm-irqfd-clean]
  MachineType: Dell Inc. Inspiron 518
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic 
root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash 
nmi_watchdog=0
  SourcePackage: qemu
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago)
  dmi.bios.date: 03/30/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.8
  dmi.board.name: 0K068D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 518
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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


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

2018-05-08 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 1770046

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

Title:
  Realtek ethernet network adapter kernel driver r8169 does not load

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Realtek kernel driver r8169 does not load on kernel 4.15.0-20.

  $ lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %
  03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11)
Subsystem: ASRock Incorporation Motherboard (one of many)

  $ lsb_release -rd
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3

  $ apt-cache policy 4.15.0-20
  linux-headers-4.15.0-20:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
i386 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
  linux-modules-4.15.0-20-generic:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  linux-headers-4.15.0-20-generic:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  linux-image-4.15.0-20-generic:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

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

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


[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value

2018-05-08 Thread Glen Ditchfield
Upstream kernel 4.17.0-rc4 didn't change performance.

Recall that I installed Kubuntu.  Since then I have installed ubuntu-
gnome-desktop, in case that provided some missing configuration file.

With either kernel, I get this behavior:
- I boot the laptop.
- Instead of logging into a desktop environment, I use virtual terminals.
- Usually /proc/cpuinfo shows all 8 CPUs running at 900 MHz, give or take a few 
Hz.  Sometimes it shows 400 MHz, but it soon rises to 900 MHz.
- I run the c-ray benchmark.  CPU frequency rises to 2400 MHz, and stays there 
for tens of seconds, then drops to 400 MHz.
- The laptop does not become warm, and the fans do not spin up.
- I kill c-ray.  A few minutes later, CPU frequency rises from 400 MHz back up 
to 900 MHz.
- kern.log contains "intel_powerclamp: Start idle injection to reduce power" 
within seconds of  the times when the frequency drops to 400 MHz, and 
"intel_powerclamp: Stop forced idle injection" when it rises to 900 MHz.

Is the cooling system failing to activate the fans, or overreacting to
CPU temperatures in some way?

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

Title:
  CPU frequency stuck at minimum value

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13
  laptop.  Performance is poor.  The CPU (an i7-8550U) is running at
  400MHz, and never speeds up, even when running some of the Phoronix
  Test Suite benchmarks.

  I can use cpupower to switch to the "performance" cpufreq governor,
  but cannot change the frequency with either governor.

  Here is the output of some experiments I ran while Phoronix's c-ray test was 
running.
  __

  gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz
  cpu MHz : 400.008
  cpu MHz : 400.002
  cpu MHz : 400.002
  cpu MHz : 400.003
  cpu MHz : 400.005
  cpu MHz : 400.003
  cpu MHz : 400.001
  cpu MHz : 400.004

  gjditchf@copperplate:/var/log$ cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 400 MHz - 4.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 1.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 400 MHz (asserted by call to kernel)
boost state support:
  Supported: yes
  Active: yes

  gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz
  Setting cpu: 0
  Error setting new values. Common errors:
  - Do you have proper administration rights? (super-user?)
  - Is the governor you requested available and modprobed?
  - Trying to set an invalid policy?
  - Trying to set a specific frequency, but userspace governor is not available,
 for example because of hardware which cannot be set to a specific frequency
 or because the userspace governor isn't loaded?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May  4 12:57:25 2018
  InstallationDate: Installed on 2018-04-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gjditchf   1190 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (10 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre Laptop 13-af0xx
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   

[Kernel-packages] [Bug 1770046] Re: Realtek ethernet network adapter kernel driver r8169 does not load

2018-05-08 Thread Nick Perez
adding version.log attachment

** Attachment added: "version log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770046/+attachment/5136460/+files/version.log

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

Title:
  Realtek ethernet network adapter kernel driver r8169 does not load

Status in linux package in Ubuntu:
  New

Bug description:
  Realtek kernel driver r8169 does not load on kernel 4.15.0-20.

  $ lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %
  03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11)
Subsystem: ASRock Incorporation Motherboard (one of many)

  $ lsb_release -rd
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3

  $ apt-cache policy 4.15.0-20
  linux-headers-4.15.0-20:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
i386 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
  linux-modules-4.15.0-20-generic:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  linux-headers-4.15.0-20-generic:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  linux-image-4.15.0-20-generic:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

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

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


[Kernel-packages] [Bug 1770046] [NEW] Realtek ethernet network adapter kernel driver r8169 does not load

2018-05-08 Thread Nick Perez
Public bug reported:

Realtek kernel driver r8169 does not load on kernel 4.15.0-20.

$ lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 11)
Subsystem: ASRock Incorporation Motherboard (one of many)

$ lsb_release -rd
Description:Linux Mint 18.3 Sylvia
Release:18.3

$ apt-cache policy 4.15.0-20
linux-headers-4.15.0-20:
  Installed: 4.15.0-20.21~16.04.1
  Candidate: 4.15.0-20.21~16.04.1
  Version table:
 *** 4.15.0-20.21~16.04.1 500
500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main amd64 
Packages
500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main i386 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages
100 /var/lib/dpkg/status
linux-modules-4.15.0-20-generic:
  Installed: 4.15.0-20.21~16.04.1
  Candidate: 4.15.0-20.21~16.04.1
  Version table:
 *** 4.15.0-20.21~16.04.1 500
500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
linux-headers-4.15.0-20-generic:
  Installed: 4.15.0-20.21~16.04.1
  Candidate: 4.15.0-20.21~16.04.1
  Version table:
 *** 4.15.0-20.21~16.04.1 500
500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
linux-image-4.15.0-20-generic:
  Installed: 4.15.0-20.21~16.04.1
  Candidate: 4.15.0-20.21~16.04.1
  Version table:
 *** 4.15.0-20.21~16.04.1 500
500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status

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

** Attachment added: "lscpci-vnvn log"
   
https://bugs.launchpad.net/bugs/1770046/+attachment/5136459/+files/lspci-vnvn.log

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

Title:
  Realtek ethernet network adapter kernel driver r8169 does not load

Status in linux package in Ubuntu:
  New

Bug description:
  Realtek kernel driver r8169 does not load on kernel 4.15.0-20.

  $ lspci | awk '/[Nn]et/ {print $1}' | xargs -i% lspci -ks %
  03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11)
Subsystem: ASRock Incorporation Motherboard (one of many)

  $ lsb_release -rd
  Description:  Linux Mint 18.3 Sylvia
  Release:  18.3

  $ apt-cache policy 4.15.0-20
  linux-headers-4.15.0-20:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
i386 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
  linux-modules-4.15.0-20-generic:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  linux-headers-4.15.0-20-generic:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  linux-image-4.15.0-20-generic:
Installed: 4.15.0-20.21~16.04.1
Candidate: 4.15.0-20.21~16.04.1
Version table:
   *** 4.15.0-20.21~16.04.1 500
  500 http://mirrordenver.fdcservers.net/ubuntu xenial-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

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

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


[Kernel-packages] [Bug 1767808] Re: "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated Graphics with Kernel 4.15

2018-05-08 Thread Ryan C. Underwood
@jsalisbury It is definitely not fixed upstream.  See
https://bugs.freedesktop.org/show_bug.cgi?id=93782

** Bug watch added: freedesktop.org Bugzilla #93782
   https://bugs.freedesktop.org/show_bug.cgi?id=93782

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

Title:
  "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated
  Graphics with Kernel 4.15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With Ubuntu 18.04 + Kernel 4.15, at boot time there are many periods when the 
boot freezes before the timeout of 10 seconds with Intel Mobile GM965/GL960 
Integrated Graphics (driver i915).
  In total it is 198 seconds that are lost in these timeouts during boot, more 
than 3 minutes!

  Regression is present since linux kernel 4.8 (with Ubuntu 16.04).

  To fix, explicitly disable the port with an i915 module setting with 
video=SVIDEO-1:d in the kernel command line parameter in the bootloader.
  1/ sudo gedit /etc/default/grub
  2/ add "video=SVIDEO-1:d" to "GRUB_CMDLINE_LINUX_DEFAULT" line
  3/ sudo update-grub

  After applying this, the system boots up much faster, there are no
  "drm ... timed out" messages.

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

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


[Kernel-packages] [Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

2018-05-08 Thread Joseph Salisbury
If there are too many required patches, a bug fix would not pass the SRU
requirements[1].  The SRU process requires the least amount of changes
to implement the fix.

How did you go about identifying all of the required commits in the bug
description?  Is that the minimum number of commits required to fix the
bug?  Is it possible to "Reverse" bisect down to a fewer number of
commits?

Is there a specific commit that you know of that introduced this bug in
Bionic?  One other option could be to find the offending commit and
revert it.

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

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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:
  Dear Canonical,

  We found that the current Ubuntu kernel contains a problem related to
  qla2xxx driver which causes:

  [   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-20-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-20.21-generic 4.15.20)
  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

  We were able to get rid of this problem cherry picking some of the
  upstream patches. Do you think they might fit in the SRU criteria?

  The commit ids are below and they were easily cherry picked.

  eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug 
after firmware timeout
  6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin 
trigger from sending too many commands
  7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in 
qla2x00_async_iocb_timeout()
  045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call 
dma_free_coherent with IRQ disabled.
  1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session 
free in qlt_free_session_done
  d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session 
deletion by using work_lock
  Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: 
Fixup locking for session deletion')
  94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused 
argument from qlt_schedule_sess_for_dele?   
  9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup 
for N2N

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

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


[Kernel-packages] [Bug 1753439] Re: Redpine: BLE scanning for nearby beacons per second is too low and result high loss rate.

2018-05-08 Thread Shrirang Bagul
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Redpine: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in linux-firmware source package in Bionic:
  Invalid

Bug description:
  SRU Justification

  Impact: BLE scanning for nearby beacons per second is too low and
  result high loss rate.

  Fix: Updated firmware.

  Test Case: Test on affected hardware using instructions below.

  Regression Potential: Limited to specific hardware.

  ---

  Steps to replicate the issue:

  1. Power on the BT device, then change the terminal by "Ctil+F1" or open 
another putty to ssh SUT.
  2.Use command below to discover BLE device.
  $ sudo stdbuf -i0-o0 -e0 /snap/bluez/current/usr/bin/hcitool lescan 
--duplicates --passive | perl -nle 'print scalar(localtime), " ",$_'
  3. log as attachment.

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

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

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


[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue

2018-05-08 Thread Shrirang Bagul
** Tags added: verification-done-xenial

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

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Incomplete
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Radio stops capturing advertisements after several hours.

  Fix: Updated firmware.

  Test Case: See below.

  Regression Potential: Limited to specific hardware.

  ---

  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

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

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


[Kernel-packages] [Bug 1757180] Re: nvidia-prime can't switch off the discrete GPU

2018-05-08 Thread Tom
Confirm the issue seems everybody on 18.04 and Nvidia GeForce is
suffering...

Duplicates ? 
 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053
   https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363

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

Title:
  nvidia-prime can't switch off the discrete GPU

Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released

Bug description:
  nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a
  change in the nvidia packaging, and a change of behaviour in logind,
  broke this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+subscriptions

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


[Kernel-packages] [Bug 1769490] kernel-bug-exists-upstream

2018-05-08 Thread Volodymyr Nerovnia
The mainline kernel does not fix this bug.
This result I get on Ubuntu 18.4 and next kernels:

Linux Inspiron-5567 4.17.0-041700rc4-generic #201805070430 SMP Mon May 7 
04:31:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Linux Inspiron-5567 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


07.05.18 19:00, Joseph Salisbury write:
> 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.17 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.17-rc4
>
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>


** Attachment added: "dmesg-4.15.txt"
   
https://bugs.launchpad.net/bugs/1769490/+attachment/5136421/+files/dmesg-4.15.txt

** Attachment added: "dmesg-4.17.txt"
   
https://bugs.launchpad.net/bugs/1769490/+attachment/5136422/+files/dmesg-4.17.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/1769490

Title:
  Ubuntu 16.4, 18.4, LUbuntu 17.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04, 18.04, LUbuntu 17.10 
  I am  getting the following error:

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-36-generic.
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  volodymyr   1376 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xd2328000 irq 282'
 Mixer name : 'Realtek ALC3246'
 Components : 'HDA:10ec0256,10280767,0012 
HDA:8086280b,80860101,0010'
 Controls  : 55
 Simple ctrls  : 17
  CurrentDesktop: LXDE
  Date: Sun May  6 19:55:30 2018
  HibernationDevice: RESUME=UUID=15f52af1-64a3-4923-838e-9eec9bd36d3a
  InstallationDate: Installed on 2018-02-20 (75 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20180105)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 8564:1000 Transcend Information, Inc. JetFlash
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=c45563b0-f313-439e-ae37-67fabf2839ab ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.2
  dmi.board.name: 02YHJP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.2:bd04/10/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn02YHJP:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1769816] Re: bootup low resolution can't unlock crypt volume

2018-05-08 Thread affinity
I've removed the 4.17rc4 packages and have returned to my original
state.

That is, I cannot use 4.15.0-20, but I can use 4.15.0.15 okay.

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

Title:
  bootup low resolution can't unlock crypt volume

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

Bug description:
  linux-headers-4.15.0-20

  On boot, the screen for entering cryptsetup pass phrase looks like vga
  size and I cannot enter the pass phrase to unlock FDE  Booting older
  kernel works fine.

  Revert to older kernel for boot with older kernel, have the following
  inxi details:

  System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) 
Desktop: Cinnamon 3.6.7
 Distro: Linux Mint 18.3 Sylvia
  Machine:   System: TOSHIBA (portable) product: Satellite P50-A v: 
PSPMHA-01D00L serial: XXM
 Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 
1.90 date: 09/19/2014
  CPU:   Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz
  Graphics:  Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller
 Card-2: NVIDIA GK107M [GeForce GT 745M]
 Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
FAILED: nouveau
 tty size: 200x60 Advanced Data: N/A for root
  Network:   Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter 
driver: ath9k
 Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrewm2561 F pulseaudio
   /dev/snd/controlC0:  andrewm2561 F pulseaudio
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409
  InstallationDate: Installed on 2016-09-10 (604 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  MachineType: TOSHIBA Satellite P50-A
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=/dev/mapper/mint--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.157.17
  Tags:  sylvia sylvia
  Uname: Linux 4.15.0-15-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite P50-A
  dmi.product.version: PSPMHA-01D00L
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1619815] Re: [Asus N752VX] Resuming after suspend restarts laptop (when on battery)

2018-05-08 Thread Christopher M. Penalver
Alex (alex-khv), it will help immensely if you use the computer the problem is 
reproducible with, and provide necessary debugging logs by filing a new report 
with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Summary changed:

- Resuming after suspend restarts laptop (when on battery)
+ [Asus N752VX] Resuming after suspend restarts laptop (when on battery)

** Tags removed: latest-bios-204
** Tags added: regression-potential

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

Title:
  [Asus N752VX] Resuming after suspend restarts laptop (when on battery)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When suspending via closing lid or sudo pm-suspend, doesn't always suspend 
and when resuming the laptop restarts. Suspend resume works fine when the 
laptop is plugged in, the problem always appears when on battery.
  The laptop is asus N752VX

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nikola 3842 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Sep  3 01:56:38 2016
  HibernationDevice: RESUME=UUID=9c2c64a9-c98c-4d02-ae32-ace578c39024
  InstallationDate: Installed on 2016-07-01 (63 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. N752VX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=3a04fbec-8e67-4764-8754-1d4ee730e82c ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N752VX.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N752VX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN752VX.204:bd01/26/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N752VX
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1769816] Re: bootup low resolution can't unlock crypt volume

2018-05-08 Thread affinity
2018-05-09 07:36:14 startup archives install
2018-05-09 07:36:14 install linux-headers-4.17.0-041700rc4:all  
4.17.0-041700rc4.201805070430
2018-05-09 07:36:14 status half-installed linux-headers-4.17.0-041700rc4:all 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:17 status unpacked linux-headers-4.17.0-041700rc4:all 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:17 status unpacked linux-headers-4.17.0-041700rc4:all 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:17 install linux-headers-4.17.0-041700rc4-generic:amd64  
4.17.0-041700rc4.201805070430
2018-05-09 07:36:17 status half-installed 
linux-headers-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status unpacked 
linux-headers-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status unpacked 
linux-headers-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 install linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
 4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status half-installed 
linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status unpacked 
linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status unpacked 
linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 install linux-modules-4.17.0-041700rc4-generic:amd64  
4.17.0-041700rc4.201805070430
2018-05-09 07:36:19 status half-installed 
linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status unpacked 
linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status unpacked 
linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 configure linux-headers-4.17.0-041700rc4:all 
4.17.0-041700rc4.201805070430 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status unpacked linux-headers-4.17.0-041700rc4:all 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status half-configured linux-headers-4.17.0-041700rc4:all 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status installed linux-headers-4.17.0-041700rc4:all 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 configure linux-modules-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status unpacked 
linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status half-configured 
linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status installed 
linux-modules-4.17.0-041700rc4-generic:amd64 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 configure 
linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430 4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status unpacked 
linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:24 status half-configured 
linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:25 status installed 
linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:25 status triggers-pending 
linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430
2018-05-09 07:36:25 trigproc 
linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430 4.17.0-041700rc4.201805070430
2018-05-09 07:36:25 status half-configured 
linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430
2018-05-09 07:37:21 status installed 
linux-image-unsigned-4.17.0-041700rc4-generic:amd64 
4.17.0-041700rc4.201805070430

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

Title:
  bootup low resolution can't unlock crypt volume

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

Bug description:
  linux-headers-4.15.0-20

  On boot, the screen for entering cryptsetup pass phrase looks like vga
  size and I cannot enter the pass phrase to unlock FDE  Booting older
  kernel works fine.

  Revert to older kernel for boot with older kernel, have the following
  inxi details:

  System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) 
Desktop: Cinnamon 3.6.7
 Distro: Linux Mint 18.3 Sylvia
  Machine:   System: TOSHIBA (portable) product: Satellite P50-A v: 
PSPMHA-01D00L serial: XXM
 Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 
1.90 date: 09/19/2014
  CPU:   Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz
  Graphics:  Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller
 Card-2: NVIDIA GK107M [GeForce GT 745M]
 Display Server: X.org 

[Kernel-packages] [Bug 1769816] Re: bootup low resolution can't unlock crypt volume

2018-05-08 Thread affinity
Should I remove the rc4 kernel?  If not, how can I fix the broken
status?

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

Title:
  bootup low resolution can't unlock crypt volume

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

Bug description:
  linux-headers-4.15.0-20

  On boot, the screen for entering cryptsetup pass phrase looks like vga
  size and I cannot enter the pass phrase to unlock FDE  Booting older
  kernel works fine.

  Revert to older kernel for boot with older kernel, have the following
  inxi details:

  System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) 
Desktop: Cinnamon 3.6.7
 Distro: Linux Mint 18.3 Sylvia
  Machine:   System: TOSHIBA (portable) product: Satellite P50-A v: 
PSPMHA-01D00L serial: XXM
 Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 
1.90 date: 09/19/2014
  CPU:   Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz
  Graphics:  Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller
 Card-2: NVIDIA GK107M [GeForce GT 745M]
 Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
FAILED: nouveau
 tty size: 200x60 Advanced Data: N/A for root
  Network:   Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter 
driver: ath9k
 Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrewm2561 F pulseaudio
   /dev/snd/controlC0:  andrewm2561 F pulseaudio
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409
  InstallationDate: Installed on 2016-09-10 (604 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  MachineType: TOSHIBA Satellite P50-A
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=/dev/mapper/mint--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.157.17
  Tags:  sylvia sylvia
  Uname: Linux 4.15.0-15-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite P50-A
  dmi.product.version: PSPMHA-01D00L
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1769816] Re: bootup low resolution can't unlock crypt volume

2018-05-08 Thread affinity
Side effect messages from mintupdate:


You have 1 broken package on your system!

Use the "Broken" filter to locate it.

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

Title:
  bootup low resolution can't unlock crypt volume

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

Bug description:
  linux-headers-4.15.0-20

  On boot, the screen for entering cryptsetup pass phrase looks like vga
  size and I cannot enter the pass phrase to unlock FDE  Booting older
  kernel works fine.

  Revert to older kernel for boot with older kernel, have the following
  inxi details:

  System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) 
Desktop: Cinnamon 3.6.7
 Distro: Linux Mint 18.3 Sylvia
  Machine:   System: TOSHIBA (portable) product: Satellite P50-A v: 
PSPMHA-01D00L serial: XXM
 Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 
1.90 date: 09/19/2014
  CPU:   Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz
  Graphics:  Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller
 Card-2: NVIDIA GK107M [GeForce GT 745M]
 Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
FAILED: nouveau
 tty size: 200x60 Advanced Data: N/A for root
  Network:   Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter 
driver: ath9k
 Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrewm2561 F pulseaudio
   /dev/snd/controlC0:  andrewm2561 F pulseaudio
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409
  InstallationDate: Installed on 2016-09-10 (604 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  MachineType: TOSHIBA Satellite P50-A
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=/dev/mapper/mint--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.157.17
  Tags:  sylvia sylvia
  Uname: Linux 4.15.0-15-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite P50-A
  dmi.product.version: PSPMHA-01D00L
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1769816] Re: bootup low resolution can't unlock crypt volume

2018-05-08 Thread affinity
Installed deb packages above.

Tag added as requested:

'kernel-fixed-upstream'


** Tags added: kernel-fixed-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/1769816

Title:
  bootup low resolution can't unlock crypt volume

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

Bug description:
  linux-headers-4.15.0-20

  On boot, the screen for entering cryptsetup pass phrase looks like vga
  size and I cannot enter the pass phrase to unlock FDE  Booting older
  kernel works fine.

  Revert to older kernel for boot with older kernel, have the following
  inxi details:

  System:Host: Satellite-P50-A Kernel: 4.15.0-15-generic x86_64 (64 bit) 
Desktop: Cinnamon 3.6.7
 Distro: Linux Mint 18.3 Sylvia
  Machine:   System: TOSHIBA (portable) product: Satellite P50-A v: 
PSPMHA-01D00L serial: XXM
 Mobo: TOSHIBA model: VG10S serial: XXX Bios: TOSHIBA v: 
1.90 date: 09/19/2014
  CPU:   Quad core Intel Core i7-4700MQ (-HT-MCP-) speed/max: 1596/3400 MHz
  Graphics:  Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller
 Card-2: NVIDIA GK107M [GeForce GT 745M]
 Display Server: X.org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
FAILED: nouveau
 tty size: 200x60 Advanced Data: N/A for root
  Network:   Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter 
driver: ath9k
 Card-2: Qualcomm Atheros QCA8171 Gigabit Ethernet driver: alx
  --- 
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andrewm2561 F pulseaudio
   /dev/snd/controlC0:  andrewm2561 F pulseaudio
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=94440034-9fd5-4211-a6b3-456ff2fd0409
  InstallationDate: Installed on 2016-09-10 (604 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  MachineType: TOSHIBA Satellite P50-A
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=/dev/mapper/mint--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.157.17
  Tags:  sylvia sylvia
  Uname: Linux 4.15.0-15-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMHA-01D00L:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.family: PEGA Family
  dmi.product.name: Satellite P50-A
  dmi.product.version: PSPMHA-01D00L
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1768971] Re: Warnings/hang during error handling of SATA disks on SAS controller

2018-05-08 Thread dann frazier
** Description changed:

  [Impact]
  When a SATA device, attached to a SAS controller, begins generating errors 
(e.g. device failing, or someone yanked it), the SAS error handling will 
complete, but may leave zombie ATA commands that never get properly 
processed/freed. This can cause some ugly messages on the console, and 
eventually leads to a system hang-up.
  
- WARNING: CPU: 0 PID: 28512 at drivers/ata/libata-eh.c:4037
- ata_eh_finish+0xb4/0xcc
- CPU: 0 PID: 28512 Comm: kworker/u32:2 Tainted: G W  OE 4.14.0#1
- ..
- Call trace:
- [] ata_eh_finish+0xb4/0xcc
- [] ata_do_eh+0xc4/0xd8
- [] ata_std_error_handler+0x44/0x8c
- [] ata_scsi_port_error_handler+0x480/0x694
- [] async_sas_ata_eh+0x4c/0x80
- [] async_run_entry_fn+0x4c/0x170
- [] process_one_work+0x144/0x390
- [] worker_thread+0x144/0x418
- [] kthread+0x10c/0x138
- [] ret_from_fork+0x10/0x18
+ WARNING: CPU: 0 PID: 28512 at drivers/ata/libata-eh.c:4037
+ ata_eh_finish+0xb4/0xcc
+ CPU: 0 PID: 28512 Comm: kworker/u32:2 Tainted: G W  OE 4.14.0#1
+ ..
+ Call trace:
+ [] ata_eh_finish+0xb4/0xcc
+ [] ata_do_eh+0xc4/0xd8
+ [] ata_std_error_handler+0x44/0x8c
+ [] ata_scsi_port_error_handler+0x480/0x694
+ [] async_sas_ata_eh+0x4c/0x80
+ [] async_run_entry_fn+0x4c/0x170
+ [] process_one_work+0x144/0x390
+ [] worker_thread+0x144/0x418
+ [] kthread+0x10c/0x138
+ [] ret_from_fork+0x10/0x18
  
  [Test Case]
  I don't have a reliable reproducer for this, but one possible test is to yank 
an active/hotpluggable SATA disk from its controller and see if the above 
symptoms occur.
  
+ [Fix] 
+ The solution here is to call into libata to have it process the remaining 
commands, allowing us to free up the zombie commands, preventing the leak and 
eventual starvation.
+ 
  [Regression Risk]
  This is a clean cherry-pick from upstream, so any regressions should have 
upstream support. As of this writing, there are no changesets in linux-next 
marked as Fixing this commit, implying that upstream has not yet found/fixed 
any bugs related to it.

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

Title:
  Warnings/hang during error handling of SATA disks on SAS controller

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

Bug description:
  [Impact]
  When a SATA device, attached to a SAS controller, begins generating errors 
(e.g. device failing, or someone yanked it), the SAS error handling will 
complete, but may leave zombie ATA commands that never get properly 
processed/freed. This can cause some ugly messages on the console, and 
eventually leads to a system hang-up.

  WARNING: CPU: 0 PID: 28512 at drivers/ata/libata-eh.c:4037
  ata_eh_finish+0xb4/0xcc
  CPU: 0 PID: 28512 Comm: kworker/u32:2 Tainted: G W  OE 4.14.0#1
  ..
  Call trace:
  [] ata_eh_finish+0xb4/0xcc
  [] ata_do_eh+0xc4/0xd8
  [] ata_std_error_handler+0x44/0x8c
  [] ata_scsi_port_error_handler+0x480/0x694
  [] async_sas_ata_eh+0x4c/0x80
  [] async_run_entry_fn+0x4c/0x170
  [] process_one_work+0x144/0x390
  [] worker_thread+0x144/0x418
  [] kthread+0x10c/0x138
  [] ret_from_fork+0x10/0x18

  [Test Case]
  I don't have a reliable reproducer for this, but one possible test is to yank 
an active/hotpluggable SATA disk from its controller and see if the above 
symptoms occur.

  [Fix] 
  The solution here is to call into libata to have it process the remaining 
commands, allowing us to free up the zombie commands, preventing the leak and 
eventual starvation.

  [Regression Risk]
  This is a clean cherry-pick from upstream, so any regressions should have 
upstream support. As of this writing, there are no changesets in linux-next 
marked as Fixing this commit, implying that upstream has not yet found/fixed 
any bugs related to it.

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

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


[Kernel-packages] [Bug 1767409] Re: linux-kvm: 4.15.0-1009.9 -proposed tracker

2018-05-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Kamal Mostafa 
(kamalmostafa)

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1767397
  phase: Uploaded
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Tuesday, 08. May 2018 21:36 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 --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1767397
  phase: Uploaded
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Tuesday, 08. May 2018 21:36 UTC

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

Title:
  linux-kvm: 4.15.0-1009.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Invalid

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1767397
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1768948] Re: Hotplugging a SATA disk into a SAS controller may cause crash

2018-05-08 Thread dann frazier
** Description changed:

  [Impact]
  Hotplugging a SATA disk into a SAS controller may trigger a NULL pointer 
dereference, leading to a crash:
  
  [ 2366.923208] Unable to handle kernel NULL pointer dereference
  at virtual address 07b8
  ...
  [ 2368.766334] Call trace:
  [ 2368.781712] [] sas_find_dev_by_rphy+0x48/0x118
  [ 2368.800394] [] sas_target_alloc+0x28/0x98
  [ 2368.817975] [] scsi_alloc_target+0x248/0x308
  [ 2368.835570] [] __scsi_add_device+0xb8/0x160
  [ 2368.853034] [] ata_scsi_scan_host+0x190/0x230
  [ 2368.871614] [] ata_scsi_hotplug+0xc8/0xe8
  [ 2368.889152] [] process_one_work+0x164/0x438
  [ 2368.908003] [] worker_thread+0x144/0x4b0
  [ 2368.924613] [] kthread+0xfc/0x110
  
  [Test Case]
  Unplug a SATA disk from a SAS controller and insert a new SATA disk in its 
place.
  
+ [Fix]
+ The ATA_PFLAG_SCSI_HOTPLUG flag is what causes libsas to attempt to handle 
hot add/remove. However, for ata devices on a SAS controller, this should be 
handled by libata. The solution is to not set this flag for ATA devices on a 
SAS controller.
+ 
  [Regression Risk]
  The fix is a clean cherry-pick from upstream that is tagged for stable. No 
subsequent patches in linux-next have a "Fixes:" marker referencing this patch, 
suggesting no regressions have been found since its introduction.

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

Title:
  Hotplugging a SATA disk into a SAS controller may cause crash

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

Bug description:
  [Impact]
  Hotplugging a SATA disk into a SAS controller may trigger a NULL pointer 
dereference, leading to a crash:

  [ 2366.923208] Unable to handle kernel NULL pointer dereference
  at virtual address 07b8
  ...
  [ 2368.766334] Call trace:
  [ 2368.781712] [] sas_find_dev_by_rphy+0x48/0x118
  [ 2368.800394] [] sas_target_alloc+0x28/0x98
  [ 2368.817975] [] scsi_alloc_target+0x248/0x308
  [ 2368.835570] [] __scsi_add_device+0xb8/0x160
  [ 2368.853034] [] ata_scsi_scan_host+0x190/0x230
  [ 2368.871614] [] ata_scsi_hotplug+0xc8/0xe8
  [ 2368.889152] [] process_one_work+0x164/0x438
  [ 2368.908003] [] worker_thread+0x144/0x4b0
  [ 2368.924613] [] kthread+0xfc/0x110

  [Test Case]
  Unplug a SATA disk from a SAS controller and insert a new SATA disk in its 
place.

  [Fix]
  The ATA_PFLAG_SCSI_HOTPLUG flag is what causes libsas to attempt to handle 
hot add/remove. However, for ata devices on a SAS controller, this should be 
handled by libata. The solution is to not set this flag for ATA devices on a 
SAS controller.

  [Regression Risk]
  The fix is a clean cherry-pick from upstream that is tagged for stable. No 
subsequent patches in linux-next have a "Fixes:" marker referencing this patch, 
suggesting no regressions have been found since its introduction.

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

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


[Kernel-packages] [Bug 598664] Re: resume fails for Lenovo Ideapad S10-3t

2018-05-08 Thread Christopher M. Penalver
Philippe Coval (rzr), it will help immensely if you use the computer the 
problem is reproducible with, and provide necessary debugging logs by filing a 
new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  resume fails for Lenovo Ideapad S10-3t

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

Bug description:
  This is an issue that was previously working in Lucid's kernel
  (2.6.32) but now occurs in 2.6.34 and 2.6.35 whether using the kernel
  ppa in Lucid or using Maverick. The hard drive light blinks for a sec
  and then goes out and the power light remains on but the screen never
  comes on and the machine's network interface doesn't come up (no
  ping/SSH).

  
  I followed the DebuggingKernelSuspend wiki page and will be attaching the 
dmesg output.

  [0.700716]   Magic number: 14:722:197
  [0.700793] acpi PNP0100:00: hash matches

  I will test the mainline kernel soon and update this ticket.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: linux-image-2.6.35-5-generic 2.6.35-5.6
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-5.6-generic 2.6.35-rc3
  Uname: Linux 2.6.35-5-generic i686
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nathan 1323 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf040 irq 44'
 Mixer name : 'Conexant CX20582 (Pebble)'
 Components : 'HDA:14f15066,17aa4003,00100302'
 Controls  : 12
 Simple ctrls  : 10
  Date: Fri Jun 25 16:31:51 2010
  HibernationDevice: RESUME=UUID=dd8123e5-46df-4207-b0c6-9a06461174a9
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
  MachineType: LENOVO 20040M18
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-5-generic 
root=UUID=b49c4dbf-a609-4d3d-b275-9123f51fe464 ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.37
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  dmi.bios.date: 03/12/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 24CN22WW
  dmi.board.name: Caucasus2
  dmi.board.vendor: LENOVO
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr24CN22WW:bd03/12/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
  dmi.product.name: 20040M18
  dmi.product.version: Lenovo Ideapad S10-3t
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1766604] Re: linux: 4.4.0-123.147 -proposed tracker

2018-05-08 Thread Stefan Bader
*** This bug is a duplicate of bug 1770011 ***
https://bugs.launchpad.net/bugs/1770011

** This bug has been marked a duplicate of bug 1770011
   linux: 4.4.0-125.149 -proposed tracker

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

Title:
  linux: 4.4.0-123.147 -proposed tracker

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

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

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

  backports: bug 1766605 (linux-aws), bug 1766607 (linux-lts-xenial)
  derivatives: bug 1766608 (linux-snapdragon), bug 1766610 (linux-kvm), bug 
1766611 (linux-euclid), bug 1766612 (linux-raspi2), bug 1766614 (linux-aws)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

2018-05-08 Thread Manoj Iyer
The patches identified here does no seem to cleanly cherry-pick. How
ever I cherry-picked several of the dependencies and came up with this
list.

scsi: qla2xxx: Fix double free bug after firmware timeout
scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
scsi: qla2xxx: Serialize session free in qlt_free_session_done
scsi: qla2xxx: Serialize session deletion by using work_lock
scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_deletion()
scsi: qla2xxx: Prevent relogin trigger from sending too many commands
scsi: qla2xxx: Prevent multiple active discovery commands per session
scsi: qla2xxx: Delay loop id allocation at login
scsi: qla2xxx: Allow relogin and session creation after reset
scsi: qla2xxx: Add ability to use GPNFT/GNNFT for RSCN handling
scsi: qla2xxx: Properly extract ADISC error codes
scsi: qla2xxx: Fix GPNFT/GNNFT error handling
scsi: qla2xxx: Fix login state machine freeze
scsi: qla2xxx: Add lock protection around host lookup
scsi: qla2xxx: Add switch command to simplify fabric discovery
scsi: qla2xxx: Fix session cleanup for N2N
scsi: qla2xxx: Allow target mode to accept PRLI in dual mode 
scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
scsi: qla2xxx: Add ability to send PRLO 
scsi: qla2xxx: Add option for use reserve exch for ELS 
scsi: qla2xxx: Move work element processing out of DPC thread
scsi: qla2xxx: Replace GPDB with async ADISC command
scsi: qla2xxx: Fix Firmware dump size for Extended login and Exchange Offload
scsi: qla2xxx: Use IOCB path to submit Control VP MBX command

It is a longer list of patches to the drive, please let me know if this
is acceptable ?

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

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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:
  Dear Canonical,

  We found that the current Ubuntu kernel contains a problem related to
  qla2xxx driver which causes:

  [   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-20-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-20.21-generic 4.15.20)
  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

  We were able to get rid of this problem cherry picking some of the
  upstream patches. Do you think they might fit in the SRU criteria?

  The commit ids are below and they were easily cherry picked.

  eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug 
after firmware timeout
  6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin 
trigger from sending too many commands
  7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in 
qla2x00_async_iocb_timeout()
  045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call 
dma_free_coherent with IRQ disabled.
  1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session 
free in qlt_free_session_done
  d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session 
deletion by using work_lock
  Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: 
Fixup locking for session deletion')
  94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused 
argument from qlt_schedule_sess_for_dele?   
  9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup 
for N2N

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1767409] Re: linux-kvm: 4.15.0-1009.9 -proposed tracker

2018-05-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1767397
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Tuesday, 08. May 2018 21:05 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-stable-master-bug: 1767397
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Tuesday, 08. May 2018 21:05 UTC
+ phase: Uploaded

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

Title:
  linux-kvm: 4.15.0-1009.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Invalid

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

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

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

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


[Kernel-packages] [Bug 1757445] Re: Suspend does not always resume

2018-05-08 Thread cascagrossa
Same fault with Dell Inspiron 5557. On resume it takes about 4 seconds
and then the lock screen appears, when trying to unlock it accepts four
to five digits and then hangs completely (nor REISUB works). The only
option is manually power off.

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

Title:
  Suspend does not always resume

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

Bug description:
  Dell XPS 13 9350 on AC power left running overnight, suspends after a
  given timeout. When coming back the next morning sometimes the laptop
  resumes to an aubergine desktop (just the screen, no GDM) and cursor
  and sits there forever. Sometimes it resumes to a black screen and
  cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 14:15:04 2018
  InstallationDate: Installed on 2018-02-13 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=bc5b647b-38ca-4206-9e96-774a5ac6b833 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1766598] Re: linux-azure: -proposed tracker

2018-05-08 Thread Stefan Bader
*** This bug is a duplicate of bug 1769997 ***
https://bugs.launchpad.net/bugs/1769997

** This bug has been marked a duplicate of bug 1769997
   linux-azure:  -proposed tracker

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

Title:
  linux-azure:  -proposed tracker

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

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

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

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

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


[Kernel-packages] [Bug 1766599] Re: linux-oem: 4.13.0-1025.28 -proposed tracker

2018-05-08 Thread Stefan Bader
*** This bug is a duplicate of bug 1769996 ***
https://bugs.launchpad.net/bugs/1769996

** This bug has been marked a duplicate of bug 1769996
   linux-oem:  -proposed tracker

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

Title:
  linux-oem: 4.13.0-1025.28 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1766592
  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/1766599/+subscriptions

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


[Kernel-packages] [Bug 1770011] [NEW] linux: -proposed tracker

2018-05-08 Thread Stefan Bader
Public bug reported:

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.04.23-2 kernel-sru-master-kernel xenial

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

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

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   

[Kernel-packages] [Bug 1770013] [NEW] linux-aws: -proposed tracker

2018-05-08 Thread Stefan Bader
Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-aws (Ubuntu Trusty)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1770011 kernel-sru-cycle-2018.04.23-2 trusty

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

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

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

** Tags added: trusty

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 

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

2018-05-08 Thread Stefan Bader
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- backports: bug 1769996 (linux-oem), bug 1769997 (linux-azure), bug 176 
(linux-azure-edge), bug 1770001 (linux-hwe), bug 1770002 (linux-gcp)
+ backports: bug 1769996 (linux-oem), bug 1769997 (linux-azure), bug 1766595 
(linux-azure-edge), bug 1770001 (linux-hwe), bug 1770002 (linux-gcp)
  derivatives: bug 1769995 (linux-raspi2)

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

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

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

  backports: bug 1769996 (linux-oem), bug 1769997 (linux-azure), bug 1766595 
(linux-azure-edge), bug 1770001 (linux-hwe), bug 1770002 (linux-gcp)
  derivatives: bug 1769995 (linux-raspi2)

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

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


[Kernel-packages] [Bug 1766596] Re: linux-gcp: 4.13.0-1014.18 -proposed tracker

2018-05-08 Thread Stefan Bader
*** This bug is a duplicate of bug 1770002 ***
https://bugs.launchpad.net/bugs/1770002

** This bug has been marked a duplicate of bug 1770002
   linux-gcp:  -proposed tracker

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

Title:
  linux-gcp: 4.13.0-1014.18 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1766592
  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/1766596/+subscriptions

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


[Kernel-packages] [Bug 1769913] Re: package linux-image-4.4.0-109-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2018-05-08 Thread hans uffing
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  package linux-image-4.4.0-109-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  sorry, but Iḿ not very versed in ubuntu

  hans@hans-NUC:~$ 
  hans@hans-NUC:~$ cat/proc/version>version.log
  bash: cat/proc/version: No such file or directory
  hans@hans-NUC:~$ sudo lspci-vnvn.log
  [sudo] password for hans: 
  sudo: lspci-vnvn.log: command not found
  hans@hans-NUC:~$

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-109-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Jan 20 19:27:25 2018
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=97dda6f4-e126-4583-a120-80c283d0f120 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: linux
  Title: package linux-image-4.4.0-109-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.board.name: NUC6i3SYB

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

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


[Kernel-packages] [Bug 1770011] Re: linux: 4.4.0-125.149 -proposed tracker

2018-05-08 Thread Stefan Bader
** Summary changed:

- linux:  -proposed tracker
+ linux: 4.4.0-125.149 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

Title:
  linux: 4.4.0-125.149 -proposed tracker

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

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

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

  backports: bug 1770013 (linux-aws), bug 1770015 (linux-lts-xenial)
  derivatives: bug 1770016 (linux-aws), bug 1770018 (linux-euclid), bug 1770019 
(linux-kvm), bug 1770020 (linux-raspi2), bug 1770023 (linux-snapdragon)

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

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


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

2018-05-08 Thread bugproxy
--- Comment From mdr...@us.ibm.com 2018-05-08 16:37 EDT---
Hit another instance of the RAM inconsistencies prior to resuming guest on 
target side (this one is migrating from boslcp6 to boslcp5 and crashing after 
it resumes execution on boslcp5). The signature is eerily similar to the ones 
above... the workload is blast from LTP but it's strange that 3 out of 3 so far 
have been the same data structure. Maybe there's a relationship between 
something the process is doing and dirty syncing?

root@boslcp5:~/vm_logs/1525768538/dumps# xxd -s 20250624 -l 128 
0-2.vm0.iteration2a
0135:          
01350010:          
01350020:          
01350030:          
01350040:          
01350050:          
01350060:          
01350070:          
root@boslcp5:~/vm_logs/1525768538/dumps# xxd -s 20250624 -l 128 
0-2.vm0.iteration2a.boslcp6
0135: d603 0100   2f62 6c61 7374 2f76  /blast/v
01350010: 6463 3400        dc4.
01350020:          
01350030:          
01350040:          
01350050:          
01350060:          
01350070:          

For this run I included traces of the various stages of memory migration
on the QEMU side relative to dirty bitmap sync (attached above). The 3
phases are:

"ram_save_setup": enables dirty logging and sets up data structures used
for tracking dirty pages. does the initial bitmap sync. QEMU keeps it's
own copy which gets OR'd with the one provided by KVM on each bitmap
sync. There's 2 blocks (ram-node0/ram-node1) each with their own bitmap
/ KVM memslot since guest was defined with 2 NUMA nodes. Only ram-node0
would be relevant here since it has offset 0 in guest physical memory
address space.

"ram_save_pending": called before each iteration to see if there are
pages still pending. When number of dirty pages in the QEMU bitmap drop
below a certain value it does another sync with KVM's bitmap.

"ram_save_iterate": walks the QEMU dirty bitmap and sends corresponding
pages until there's none left or some other limit (e.g. bandwidth
throttling or max-pages-per-iteration) is hit.

"ram_save_pending"/"ram_save_iterate" keeps repeating until no more
pages are left.

"ram_save_complete" does a final sync with KVM bitmap, sends final set
of pages, then disables dirty logging and completes the migration.

"vm_stop" denotes with the guest VCPUs have all exited and stopped
execution.

There's 2 migrations reflected in the posted traces, the first one can
be ignored (everything between first ram_save_setup and first
ram_save_complete), it's just a backup of the VM. After that the VM is
backup up it resumes execution and that's the state we're migrating here
and seeing a crash with on other end.

The sequences of events in this run are comparable to previous
successful runs, no strange orderings or missed calls to sync with KVM
dirty bitmap/etc. The condensed version of the trace are below, but it
looks like there's a sync prior to vm_stop, and a sync afterward, and
given that these syncs are OR'd into a persistent bitmap maintained by
QEMU, there's shouldn't be any loss of dirty page information with this
particular ordering of events.

117401@1525770831.423435: >ram_save_setup
117401@1525770831.424386: migration_bitmap_sync, count: 4
117401@1525770831.424400: qemu_global_log_sync
117401@1525770831.424410: qemu_global_log_sync, name: ram-node0, addr: 0
117401@1525770831.424419: kvm_log_sync, addr: 0, size: 28000
117401@1525770831.445270: qemu_global_log_sync, name: ram-node1, addr: 28000
117401@1525770831.445279: kvm_log_sync, addr: 28000, size: 28000
117401@1525770831.545805: qemu_global_log_sync, name: vga.vram, addr: 8000
117401@1525770831.545814: kvm_log_sync, addr: 20008000, size: 100
117401@1525770831.545831: qemu_global_log_sync, name: ram-node0, addr: 0
117401@1525770831.545905: qemu_global_log_sync, name: ram-node1, addr: 28000
117401@1525770831.545959: qemu_global_log_sync, name: vga.vram, addr: 8000
117401@1525770831.545965: migration_bitmap_sync, id: ram-node0, 
block->mr->name: ram-node0, block->used_length: 28000h
117401@1525770831.547606: migration_bitmap_sync, id: ram-node1, 
block->mr->name: ram-node1, block->used_length: 28000h
117401@1525770831.548986: ram_save_pending, dirty pages remaining: 5247120, 
page size: 4096

[Kernel-packages] [Bug 1770016] [NEW] linux-aws: -proposed tracker

2018-05-08 Thread Stefan Bader
Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-aws (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.04.23-2 kernel-sru-derivative-of-1770011 xenial

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

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

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: 

[Kernel-packages] [Bug 1766610] Re: linux-kvm: 4.4.0-1022.27 -proposed tracker

2018-05-08 Thread Stefan Bader
*** This bug is a duplicate of bug 1770019 ***
https://bugs.launchpad.net/bugs/1770019

** This bug has been marked a duplicate of bug 1770019
   linux-kvm:  -proposed tracker

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

Title:
  linux-kvm: 4.4.0-1022.27 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1766604
  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/1766610/+subscriptions

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


[Kernel-packages] [Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

2018-05-08 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: New => Triaged

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

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

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

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

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

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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:
  Dear Canonical,

  We found that the current Ubuntu kernel contains a problem related to
  qla2xxx driver which causes:

  [   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-20-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-20.21-generic 4.15.20)
  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

  We were able to get rid of this problem cherry picking some of the
  upstream patches. Do you think they might fit in the SRU criteria?

  The commit ids are below and they were easily cherry picked.

  eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug 
after firmware timeout
  6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin 
trigger from sending too many commands
  7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in 
qla2x00_async_iocb_timeout()
  045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call 
dma_free_coherent with IRQ disabled.
  1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session 
free in qlt_free_session_done
  d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session 
deletion by using work_lock
  Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: 
Fixup locking for session deletion')
  94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused 
argument from qlt_schedule_sess_for_dele?   
  9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup 
for N2N

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

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


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

2018-05-08 Thread Stefan Bader
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1770013 (linux-aws), bug 1770015 (linux-lts-xenial)
+ derivatives: bug 1770016 (linux-aws), bug 1770018 (linux-euclid), bug 1770019 
(linux-kvm), bug 1770020 (linux-raspi2), bug 1770023 (linux-snapdragon)

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

Title:
  linux:  -proposed tracker

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

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

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

  backports: bug 1770013 (linux-aws), bug 1770015 (linux-lts-xenial)
  derivatives: bug 1770016 (linux-aws), bug 1770018 (linux-euclid), bug 1770019 
(linux-kvm), bug 1770020 (linux-raspi2), bug 1770023 (linux-snapdragon)

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

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


[Kernel-packages] [Bug 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

2018-05-08 Thread Seth Forshee
I'm not sure here whether the xenial nomination is meant to apply to the
linux package. If so ...

That list of kernel patches is probably correct for bionic. Xenial
however is going to require additional patches. The wmm rules are only
available with the newer, extensible regdb format which is supported in
4.15 but not in 4.4. So to have any hope of using the wmm rules with 4.4
there would need to be a number of additional backports.

The wireless-regdb changes for xenial will also need some consideration.
With the new regdb format there was also a transition to loading the
regdb as a firmware file signed with a key whose public half is baked
into the kernel. My thinking is that we should just stop building the
regdb files from source and ship the pre-built (and pre-signed) upstream
binaries. I think this should be fine for xenial but we will need to
verify.

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

Title:
  Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement

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

Bug description:
  Intel wireless driver and firmware require updates in order to meet
  the new ETSI regulation [1] for OEM machines shipped from factories.

  Intel provided us the following information for what are required to
  update:

  1. Kernel driver:

  https://patchwork.kernel.org/patch/10322121/
  https://patchwork.kernel.org/patch/10312731/
  https://patchwork.kernel.org/patch/10312735/
  https://patchwork.kernel.org/patch/10312733/

  - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches
  - 8000 series requires 4.16.
  - 9000 series requires 4.17.

  2. linux-firmware
  Requires latest versions from linux-firmware.git

  3. wireless-regdb update

  [1]
  
http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf

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

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


[Kernel-packages] [Bug 1766592] Re: linux: 4.13.0-40.45 -proposed tracker

2018-05-08 Thread Stefan Bader
*** This bug is a duplicate of bug 1769993 ***
https://bugs.launchpad.net/bugs/1769993

** This bug has been marked a duplicate of bug 1769993
   linux:  -proposed tracker

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

Title:
  linux: 4.13.0-40.45 -proposed tracker

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

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

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

  backports: bug 1766594 (linux-hwe), bug 1766595 (linux-azure-edge), bug 
1766596 (linux-gcp), bug 1766598 (linux-azure), bug 1766599 (linux-oem)
  derivatives: bug 1766593 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1767403] Re: linux-aws: 4.15.0-1008.8 -proposed tracker

2018-05-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1767397
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Tuesday, 08. May 2018 20:36 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1767397
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Tuesday, 08. May 2018 20:36 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1767397
  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/1767403/+subscriptions

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


[Kernel-packages] [Bug 1766614] Re: linux-aws: 4.4.0-1056.65 -proposed tracker

2018-05-08 Thread Stefan Bader
*** This bug is a duplicate of bug 1770016 ***
https://bugs.launchpad.net/bugs/1770016

** This bug has been marked a duplicate of bug 1770016
   linux-aws:  -proposed tracker

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

Title:
  linux-aws: 4.4.0-1056.65 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1766604
  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/1766614/+subscriptions

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


[Kernel-packages] [Bug 1769080] Re: linux-lts-trusty: -proposed tracker

2018-05-08 Thread Stefan Bader
** Information type changed from Private to Public

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

Title:
  linux-lts-trusty:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

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

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

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


[Kernel-packages] [Bug 1770019] [NEW] linux-kvm: -proposed tracker

2018-05-08 Thread Stefan Bader
Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-kvm (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.04.23-2 kernel-sru-derivative-of-1770011 xenial

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

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

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-proposed
 

[Kernel-packages] [Bug 1766605] Re: linux-aws: 4.4.0-1018.18 -proposed tracker

2018-05-08 Thread Stefan Bader
*** This bug is a duplicate of bug 1770013 ***
https://bugs.launchpad.net/bugs/1770013

** This bug has been marked a duplicate of bug 1770013
   linux-aws:  -proposed tracker

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

Title:
  linux-aws: 4.4.0-1018.18 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1766604
  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/1766605/+subscriptions

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


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

2018-05-08 Thread Stefan Bader
** Information type changed from Private 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/1769077

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

  backports: bug 1769080 (linux-lts-trusty)
  derivatives:

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

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


[Kernel-packages] [Bug 1766601] Re: linux: 3.13.0-146.195 -proposed tracker

2018-05-08 Thread Stefan Bader
*** This bug is a duplicate of bug 1769077 ***
https://bugs.launchpad.net/bugs/1769077

** This bug has been marked a duplicate of bug 1769077
   linux:  -proposed tracker

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

Title:
  linux: 3.13.0-146.195 -proposed tracker

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

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

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

  backports: bug 1766603 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()

2018-05-08 Thread Treviño
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  from meta_renderer_native_finish_frame()

Status in gnome-shell package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/70
  https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665

  ---

  The crash was reported after booting and logging in to an X.Org
  session.

  $ lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ apt-cache policy gnome-shell
  gnome-shell:
    Instalovaná verze: 3.27.92-0ubuntu1
    Kandidát:  3.27.92-0ubuntu1
    Tabulka verzí:
   *** 3.27.92-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Mar 11 11:08:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-12-19 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f3fee5d2f17 : 
mov0x20(%rax),%rcx
   PC (0x7f3fee5d2f17) ok
   source "0x20(%rax)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_renderer_native_finish_frame () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
   () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
  Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions

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


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

2018-05-08 Thread Stefan Bader
*** This bug is a duplicate of bug 1769080 ***
https://bugs.launchpad.net/bugs/1769080

** This bug has been marked a duplicate of bug 1769080
   linux-lts-trusty:  -proposed tracker

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1766601
  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/1766603/+subscriptions

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


[Kernel-packages] [Bug 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu

2018-05-08 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-meta-hwe - 4.13.0.41.60

---
linux-meta-hwe (4.13.0.41.60) xenial; urgency=medium

  * Bump ABI 4.13.0-41

  * need to ensure microcode updates are available to all bare-metal installs of
Ubuntu (LP: #1738259)
- Revert "UBUNTU: Make kernel image packages depend on cpu microcode 
updates"

linux-meta-hwe (4.13.0.40.59) xenial; urgency=medium

  * Bump ABI 4.13.0-40

  * need to ensure microcode updates are available to all bare-metal installs of
Ubuntu (LP: #1738259)
- Make kernel image packages depend on cpu microcode updates

 -- Kleber Sacilotto de Souza   Thu, 03 May
2018 11:35:12 +0200

** Changed in: linux-meta (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  need to ensure microcode updates are available to all bare-metal
  installs of Ubuntu

Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-hwe-edge package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  Fix Released
Status in linux-meta-oem package in Ubuntu:
  Invalid
Status in linux-meta source package in Precise:
  New
Status in linux-meta source package in Trusty:
  Fix Released
Status in linux-meta source package in Xenial:
  Fix Released
Status in linux-meta-hwe source package in Xenial:
  Fix Released
Status in linux-meta-hwe-edge source package in Xenial:
  Fix Released
Status in linux-meta-lts-xenial source package in Xenial:
  Fix Committed
Status in linux-meta-oem source package in Xenial:
  Fix Committed
Status in linux-meta source package in Zesty:
  Invalid
Status in linux-meta source package in Artful:
  Fix Released
Status in linux-meta source package in Bionic:
  Triaged

Bug description:
  From time to time, CPU vendors release updates to microcode that can
  be loaded into the CPU from the OS.  For x86, we have these updates
  available in the archive as amd64-microcode and intel-microcode.

  Sometimes, these microcode updates have addressed security issues with
  the CPU.  They almost certainly will again in the future.

  We should ensure that all users of Ubuntu on baremetal x86 receive
  these security updates, and have them applied to the CPU in early boot
  where at all feasible.

  Because these are hardware-dependent packages which we don't want to
  install except on baremetal (so: not in VMs or containers), the
  logical place to pull them into the system is via the kernel, so that
  only the kernel baremetal flavors pull them in.  This is analogous to
  linux-firmware, which is already a dependency of the linux-
  image-{lowlatency,generic} metapackages, and whose contents are
  applied to the hardware by the kernel similar to microcode.

  So, please update the linux-image-{lowlatency,generic} metapackages to
  add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
  and the corresponding hwe metapackages also.

  Please time this change to coincide with the next updates of the
  microcode packages in the archive.

  I believe we will also need to promote the *-microcode packages to
  main from restricted as part of this (again, by analogy with linux-
  firmware).

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

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


[Kernel-packages] [Bug 1770003] [NEW] qla2xxx: Fix page fault at kmem_cache_alloc_node()

2018-05-08 Thread bugproxy
Public bug reported:

Dear Canonical,

We found that the current Ubuntu kernel contains a problem related to
qla2xxx driver which causes:

[   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-20-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-20.21-generic 4.15.20)
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

We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?

The commit ids are below and they were easily cherry picked.

eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug 
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin 
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in 
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call 
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session free 
in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session 
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: 
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused argument 
from qlt_schedule_sess_for_dele?   
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup 
for N2N

** Affects: ubuntu-power-systems
 Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Triaged

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


** Tags: architecture-ppc64le bugnameltc-167562 severity-high 
targetmilestone-inin1804 triage-g

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

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

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

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

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

Bug description:
  Dear Canonical,

  We found that the current Ubuntu kernel contains a problem related to
  qla2xxx driver which causes:

  [   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-20-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-20.21-generic 4.15.20)
  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
  

[Kernel-packages] [Bug 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu

2018-05-08 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-meta - 4.13.0.41.44

---
linux-meta (4.13.0.41.44) artful; urgency=medium

  * Bump ABI 4.13.0-41

  * need to ensure microcode updates are available to all bare-metal installs of
Ubuntu (LP: #1738259)
- Revert "UBUNTU: Make kernel image packages depend on cpu microcode 
updates"

linux-meta (4.13.0.40.43) artful; urgency=medium

  * Bump ABI 4.13.0-40

  * need to ensure microcode updates are available to all bare-metal installs of
Ubuntu (LP: #1738259)
- Make kernel image packages depend on cpu microcode updates

 -- Kleber Sacilotto de Souza   Wed, 02 May
2018 12:46:37 +0200

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

Title:
  need to ensure microcode updates are available to all bare-metal
  installs of Ubuntu

Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-hwe-edge package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  Fix Released
Status in linux-meta-oem package in Ubuntu:
  Invalid
Status in linux-meta source package in Precise:
  New
Status in linux-meta source package in Trusty:
  Fix Released
Status in linux-meta source package in Xenial:
  Fix Released
Status in linux-meta-hwe source package in Xenial:
  Fix Released
Status in linux-meta-hwe-edge source package in Xenial:
  Fix Released
Status in linux-meta-lts-xenial source package in Xenial:
  Fix Committed
Status in linux-meta-oem source package in Xenial:
  Fix Committed
Status in linux-meta source package in Zesty:
  Invalid
Status in linux-meta source package in Artful:
  Fix Released
Status in linux-meta source package in Bionic:
  Triaged

Bug description:
  From time to time, CPU vendors release updates to microcode that can
  be loaded into the CPU from the OS.  For x86, we have these updates
  available in the archive as amd64-microcode and intel-microcode.

  Sometimes, these microcode updates have addressed security issues with
  the CPU.  They almost certainly will again in the future.

  We should ensure that all users of Ubuntu on baremetal x86 receive
  these security updates, and have them applied to the CPU in early boot
  where at all feasible.

  Because these are hardware-dependent packages which we don't want to
  install except on baremetal (so: not in VMs or containers), the
  logical place to pull them into the system is via the kernel, so that
  only the kernel baremetal flavors pull them in.  This is analogous to
  linux-firmware, which is already a dependency of the linux-
  image-{lowlatency,generic} metapackages, and whose contents are
  applied to the hardware by the kernel similar to microcode.

  So, please update the linux-image-{lowlatency,generic} metapackages to
  add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
  and the corresponding hwe metapackages also.

  Please time this change to coincide with the next updates of the
  microcode packages in the archive.

  I believe we will also need to promote the *-microcode packages to
  main from restricted as part of this (again, by analogy with linux-
  firmware).

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

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


[Kernel-packages] [Bug 1708191] Re: Xubuntu complete freeze with Intel atomic i915

2018-05-08 Thread Ubuntu Kernel Bot
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  Xubuntu complete freeze with Intel atomic i915

Status in linux package in Ubuntu:
  New

Bug description:
  Xubuntu version:
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  Ubuntu and Xubuntu crash after any length of time and seemingly randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-28-generic 4.10.0-28.32~16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Aug  2 11:28:20 2017
  InstallationDate: Installed on 2017-08-02 (0 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ethan  1371 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1b2199a9-d780-44b3-87d9-af18abe4f32e
  InstallationDate: Installed on 2017-08-02 (0 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Inspiron 20-3052
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic.efi.signed 
root=UUID=3bc79766-cfa3-436e-abd8-03cd79ef1561 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-28-generic N/A
   linux-backports-modules-4.10.0-28-generic  N/A
   linux-firmware 1.157.8
  Tags:  xenial
  Uname: Linux 4.10.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.8.3
  dmi.board.name: 0C2YT8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.8.3:bd05/16/2017:svnDellInc.:pnInspiron20-3052:pvr3.8.3:rvnDellInc.:rn0C2YT8:rvrA00:cvnDellInc.:ct13:cvrNotSpecified:
  dmi.product.name: Inspiron 20-3052
  dmi.product.version: 3.8.3
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1699511] Re: package linux-headers-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

2018-05-08 Thread Ubuntu Kernel Bot
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  package linux-headers-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to
  install/upgrade: проблемы зависимостей — оставляем не настроенным

Status in linux package in Ubuntu:
  New

Bug description:
  Problem.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.8.0-56-generic 4.8.0-56.61~16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun 21 17:57:41 2017
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2017-06-03 (18 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-hwe
  Title: package linux-headers-4.8.0-56-generic 4.8.0-56.61~16.04.1 failed to 
install/upgrade: проблемы зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1769996] [NEW] linux-oem: -proposed tracker

2018-05-08 Thread Stefan Bader
Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-oem (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1769993 kernel-sru-cycle-2018.04.23-2 xenial

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

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

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team 

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

2018-05-08 Thread Sandy Patterson
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1768139/+attachment/5136293/+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/1768139

Title:
  Kernel crash when booting laptop with hdmi monitor connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot a Dell Inspiron 7559 with an external monitor connected to
  the hdmi port I get a crash on bootup. I can see the following stack
  trace in journalctl:

  
  syslog contains:
   kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
    Installed: 4.15.0-20.21
    Candidate: 4.15.0-20.21
    Version table:
   *** 4.15.0-20.21 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  3) What you expected to happen
  I expected the laptop to boot to the login screen.
  4) What happened instead
  I see a blank screen after grub and have to hard power off the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:22:20 2018
  InstallationDate: Installed on 2018-04-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

  This is a fresh install. I have modified grub defaults to include 
"acpi_osi=!Windows 2015"
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   1965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash 
"acpi_osi=!Windows 2015"
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.5
  dmi.sys.vendor: Dell Inc.

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

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


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

2018-05-08 Thread chrone
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1758621/+attachment/5136343/+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/1758621

Title:
  Ubuntu Xenial HWE Kernel 4.13 Direct Sync Write Performance Regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Ubuntu,

  Just found out today that when using Ubuntu Xenial HWE kernel 4.13 in
  a VM on top of Proxmox VE 5.1.x, the direct synchronous write
  performance is 93% slower than on kernel 4.4. Kernel 4.13 direct sync
  4KB write could only achieve 303KB/s while kernel 4.4 could achieve
  4.5MB/s.

  The VM is using ext4 filesystem and running on top of ZFS ZVOL on ZFS
  RAID1 with virtio-scsi, qemu disk cache none, and qemu disk discard
  enabled. The underlying physical disks are Samsung Enterprise SSD
  SM863a 480GB series.

  The reason I need to run kernel 4.13 to mount CephFS Luminous with
  kernel client. Hopefully CephFS Luminous kernel client will be back
  ported to kernel 4.4 in the near future.

  Is this from Ubuntu Xenial kernel 4.13 performance regression or from
  Proxmox VE 5.1 kernel 4.13 virtio-scsi performance regression?

  The test results:

  ##
  # ubuntu xenial kernel 4.13. the direct synchronous write performance is 93% 
slower than kernel 4.4
  ##
  root@localhost:~# uname -a
  Linux localhost 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 3.46369 s, 303 kB/s

  ##
  # ubuntu xenial kernel 4.4. the direct synchronous write performance is 14x 
faster than kernel 4.13
  ##
  root@localhost:~# uname -a
  Linux localhost 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.231176 s, 4.5 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Mar 25 13:43:34 2018
  InstallationDate: Installed on 2018-03-22 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 22:23 seq
   crw-rw 1 root audio 116, 33 May  7 22:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/localhost-swap
  InstallationDate: Installed on 2018-03-22 (47 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-39-generic 
root=/dev/mapper/localhost-root ro
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  dmi.product.name: 

[Kernel-packages] [Bug 1707925] Re: package linux-image-extra-4.8.0-54-generic 4.8.0-54.57~16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befo

2018-05-08 Thread Ubuntu Kernel Bot
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  package linux-image-extra-4.8.0-54-generic 4.8.0-54.57~16.04.1 failed
  to install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  New

Bug description:
  I dont know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.8.0-54-generic 4.8.0-54.57~16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Aug  1 10:16:53 2017
  DuplicateSignature:
   package:linux-image-extra-4.8.0-54-generic:4.8.0-54.57~16.04.1
   Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
   dpkg: error processing package linux-image-extra-4.8.0-54-generic 
(--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-24 (69 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-hwe
  Title: package linux-image-extra-4.8.0-54-generic 4.8.0-54.57~16.04.1 failed 
to install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1674905] Re: build for linux-signed-4.8.0-43-46 has failed

2018-05-08 Thread Ubuntu Kernel Bot
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)

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

Title:
  build for linux-signed-4.8.0-43-46 has failed

Status in linux package in Ubuntu:
  New

Bug description:
  The linux-signed build has failed leading to me being unable to
  upgrade my kernel. I do not wish to risk an upgrade that might make my
  laptop unbootable. The kernel itself was built ok (and works on my
  non-UEFI install machines). I am on the proposed update branch.

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

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


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

2018-05-08 Thread chrone
apport information

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

Title:
  Ubuntu Xenial HWE Kernel 4.13 Direct Sync Write Performance Regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Ubuntu,

  Just found out today that when using Ubuntu Xenial HWE kernel 4.13 in
  a VM on top of Proxmox VE 5.1.x, the direct synchronous write
  performance is 93% slower than on kernel 4.4. Kernel 4.13 direct sync
  4KB write could only achieve 303KB/s while kernel 4.4 could achieve
  4.5MB/s.

  The VM is using ext4 filesystem and running on top of ZFS ZVOL on ZFS
  RAID1 with virtio-scsi, qemu disk cache none, and qemu disk discard
  enabled. The underlying physical disks are Samsung Enterprise SSD
  SM863a 480GB series.

  The reason I need to run kernel 4.13 to mount CephFS Luminous with
  kernel client. Hopefully CephFS Luminous kernel client will be back
  ported to kernel 4.4 in the near future.

  Is this from Ubuntu Xenial kernel 4.13 performance regression or from
  Proxmox VE 5.1 kernel 4.13 virtio-scsi performance regression?

  The test results:

  ##
  # ubuntu xenial kernel 4.13. the direct synchronous write performance is 93% 
slower than kernel 4.4
  ##
  root@localhost:~# uname -a
  Linux localhost 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 3.46369 s, 303 kB/s

  ##
  # ubuntu xenial kernel 4.4. the direct synchronous write performance is 14x 
faster than kernel 4.13
  ##
  root@localhost:~# uname -a
  Linux localhost 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.231176 s, 4.5 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Mar 25 13:43:34 2018
  InstallationDate: Installed on 2018-03-22 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 22:23 seq
   crw-rw 1 root audio 116, 33 May  7 22:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/localhost-swap
  InstallationDate: Installed on 2018-03-22 (47 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-39-generic 
root=/dev/mapper/localhost-root ro
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  

[Kernel-packages] [Bug 1769997] [NEW] linux-azure: -proposed tracker

2018-05-08 Thread Stefan Bader
Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: Joshua R. Poulson (jrp)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-azure (Ubuntu Xenial)
 Importance: Medium
 Status: Confirmed


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1769993 kernel-sru-cycle-2018.04.23-2 xenial

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

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

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

** Tags added: xenial

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: 

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

2018-05-08 Thread Sandy Patterson
apport information

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

Title:
  Kernel crash when booting laptop with hdmi monitor connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot a Dell Inspiron 7559 with an external monitor connected to
  the hdmi port I get a crash on bootup. I can see the following stack
  trace in journalctl:

  
  syslog contains:
   kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
    Installed: 4.15.0-20.21
    Candidate: 4.15.0-20.21
    Version table:
   *** 4.15.0-20.21 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  3) What you expected to happen
  I expected the laptop to boot to the login screen.
  4) What happened instead
  I see a blank screen after grub and have to hard power off the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:22:20 2018
  InstallationDate: Installed on 2018-04-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

  This is a fresh install. I have modified grub defaults to include 
"acpi_osi=!Windows 2015"
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   1965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash 
"acpi_osi=!Windows 2015"
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.5
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1701972] Re: package linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1 [origin: Ubuntu] failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código

2018-05-08 Thread Ubuntu Kernel Bot
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  package linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1 [origin:
  Ubuntu] failed to install/upgrade: el subproceso script pre-
  installation nuevo devolvió el código de salida de error 128

Status in linux package in Ubuntu:
  New

Bug description:
  The system reported me on launch

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Mon Jul  3 00:38:22 2017
  ErrorMessage: el subproceso script pre-installation nuevo devolvió el código 
de salida de error 128
  InstallationDate: Installed on 2017-07-02 (0 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-hwe
  Title: package linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1 [origin: 
Ubuntu] failed to install/upgrade: el subproceso script pre-installation nuevo 
devolvió el código de salida de error 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2018-05-08 Thread Sandy Patterson
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1768139/+attachment/5136300/+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/1768139

Title:
  Kernel crash when booting laptop with hdmi monitor connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot a Dell Inspiron 7559 with an external monitor connected to
  the hdmi port I get a crash on bootup. I can see the following stack
  trace in journalctl:

  
  syslog contains:
   kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
    Installed: 4.15.0-20.21
    Candidate: 4.15.0-20.21
    Version table:
   *** 4.15.0-20.21 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  3) What you expected to happen
  I expected the laptop to boot to the login screen.
  4) What happened instead
  I see a blank screen after grub and have to hard power off the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:22:20 2018
  InstallationDate: Installed on 2018-04-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

  This is a fresh install. I have modified grub defaults to include 
"acpi_osi=!Windows 2015"
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   1965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash 
"acpi_osi=!Windows 2015"
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.5
  dmi.sys.vendor: Dell Inc.

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

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


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

2018-05-08 Thread Sandy Patterson
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1768139/+attachment/5136301/+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/1768139

Title:
  Kernel crash when booting laptop with hdmi monitor connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot a Dell Inspiron 7559 with an external monitor connected to
  the hdmi port I get a crash on bootup. I can see the following stack
  trace in journalctl:

  
  syslog contains:
   kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
    Installed: 4.15.0-20.21
    Candidate: 4.15.0-20.21
    Version table:
   *** 4.15.0-20.21 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  3) What you expected to happen
  I expected the laptop to boot to the login screen.
  4) What happened instead
  I see a blank screen after grub and have to hard power off the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:22:20 2018
  InstallationDate: Installed on 2018-04-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

  This is a fresh install. I have modified grub defaults to include 
"acpi_osi=!Windows 2015"
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   1965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash 
"acpi_osi=!Windows 2015"
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.5
  dmi.sys.vendor: Dell Inc.

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

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


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

2018-05-08 Thread chrone
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1758621/+attachment/5136345/+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/1758621

Title:
  Ubuntu Xenial HWE Kernel 4.13 Direct Sync Write Performance Regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Ubuntu,

  Just found out today that when using Ubuntu Xenial HWE kernel 4.13 in
  a VM on top of Proxmox VE 5.1.x, the direct synchronous write
  performance is 93% slower than on kernel 4.4. Kernel 4.13 direct sync
  4KB write could only achieve 303KB/s while kernel 4.4 could achieve
  4.5MB/s.

  The VM is using ext4 filesystem and running on top of ZFS ZVOL on ZFS
  RAID1 with virtio-scsi, qemu disk cache none, and qemu disk discard
  enabled. The underlying physical disks are Samsung Enterprise SSD
  SM863a 480GB series.

  The reason I need to run kernel 4.13 to mount CephFS Luminous with
  kernel client. Hopefully CephFS Luminous kernel client will be back
  ported to kernel 4.4 in the near future.

  Is this from Ubuntu Xenial kernel 4.13 performance regression or from
  Proxmox VE 5.1 kernel 4.13 virtio-scsi performance regression?

  The test results:

  ##
  # ubuntu xenial kernel 4.13. the direct synchronous write performance is 93% 
slower than kernel 4.4
  ##
  root@localhost:~# uname -a
  Linux localhost 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 3.46369 s, 303 kB/s

  ##
  # ubuntu xenial kernel 4.4. the direct synchronous write performance is 14x 
faster than kernel 4.13
  ##
  root@localhost:~# uname -a
  Linux localhost 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.231176 s, 4.5 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Mar 25 13:43:34 2018
  InstallationDate: Installed on 2018-03-22 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 22:23 seq
   crw-rw 1 root audio 116, 33 May  7 22:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/localhost-swap
  InstallationDate: Installed on 2018-03-22 (47 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-39-generic 
root=/dev/mapper/localhost-root ro
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  dmi.product.name: Standard PC (i440FX + 

[Kernel-packages] [Bug 1707107] Re: HWE 4.10: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module i915_bpo

2018-05-08 Thread Ubuntu Kernel Bot
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  HWE 4.10: Possible missing firmware
  /lib/firmware/i915/kbl_dmc_ver1.bin for module i915_bpo

Status in linux package in Ubuntu:
  New

Bug description:
  During kernel update the above message is output. For 4.4 kernel it
  was fixed in https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/1624164, but it is still present in HWE 4.10 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-28-generic 4.10.0-28.32~16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 28 06:46:18 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-07-02 (756 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2018-05-08 Thread Sandy Patterson
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1768139/+attachment/5136297/+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/1768139

Title:
  Kernel crash when booting laptop with hdmi monitor connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot a Dell Inspiron 7559 with an external monitor connected to
  the hdmi port I get a crash on bootup. I can see the following stack
  trace in journalctl:

  
  syslog contains:
   kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
    Installed: 4.15.0-20.21
    Candidate: 4.15.0-20.21
    Version table:
   *** 4.15.0-20.21 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  3) What you expected to happen
  I expected the laptop to boot to the login screen.
  4) What happened instead
  I see a blank screen after grub and have to hard power off the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:22:20 2018
  InstallationDate: Installed on 2018-04-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

  This is a fresh install. I have modified grub defaults to include 
"acpi_osi=!Windows 2015"
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   1965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash 
"acpi_osi=!Windows 2015"
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.5
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1700205] Re: package linux-image-4.8.0-57-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2018-05-08 Thread Ubuntu Kernel Bot
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  package linux-image-4.8.0-57-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  software not getting installed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.8.0-57-generic (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-55.58~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-55-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.7
  Architecture: amd64
  Date: Fri Jun 23 23:41:20 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-10 (13 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-hwe
  Title: package linux-image-4.8.0-57-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2018-05-08 Thread Sandy Patterson
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1768139/+attachment/5136304/+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/1768139

Title:
  Kernel crash when booting laptop with hdmi monitor connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot a Dell Inspiron 7559 with an external monitor connected to
  the hdmi port I get a crash on bootup. I can see the following stack
  trace in journalctl:

  
  syslog contains:
   kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
    Installed: 4.15.0-20.21
    Candidate: 4.15.0-20.21
    Version table:
   *** 4.15.0-20.21 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  3) What you expected to happen
  I expected the laptop to boot to the login screen.
  4) What happened instead
  I see a blank screen after grub and have to hard power off the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:22:20 2018
  InstallationDate: Installed on 2018-04-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

  This is a fresh install. I have modified grub defaults to include 
"acpi_osi=!Windows 2015"
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   1965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash 
"acpi_osi=!Windows 2015"
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.5
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1708607] Re: package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 failed to install/upgrade: package linux-image-extra-4.10.0-27-generic is not ready for configurati

2018-05-08 Thread Ubuntu Kernel Bot
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2
  failed to install/upgrade: package linux-image-extra-4.10.0-27-generic
  is not ready for configuration  cannot configure (current status
  'half-installed')

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to update system but updater can not configure linux-image-
  extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 failed to
  install/upgrade: package linux-image-extra-4.10.0-27-generic is not
  ready for configuration  cannot configure (current status 'half-
  installed')

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Aug  4 09:35:15 2017
  DuplicateSignature:
   package:linux-image-extra-4.10.0-27-generic:4.10.0-27.30~16.04.2
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package linux-image-extra-4.10.0-27-generic 
(--configure):
package linux-image-extra-4.10.0-27-generic is not ready for configuration
  ErrorMessage: package linux-image-extra-4.10.0-27-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-07-27 (7 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: linux-hwe
  Title: package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 
failed to install/upgrade: package linux-image-extra-4.10.0-27-generic is not 
ready for configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1701273] Re: package linux-image-4.8.0-58-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2018-05-08 Thread Ubuntu Kernel Bot
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  package linux-image-4.8.0-58-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Estava instal·lant des del gestor d'actualitzacions i ha fallat la
  instal·lació.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.8.0-58-generic (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Thu Jun 29 15:39:24 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-18 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-hwe
  Title: package linux-image-4.8.0-58-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2018-05-08 Thread chrone
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1758621/+attachment/5136338/+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/1758621

Title:
  Ubuntu Xenial HWE Kernel 4.13 Direct Sync Write Performance Regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Ubuntu,

  Just found out today that when using Ubuntu Xenial HWE kernel 4.13 in
  a VM on top of Proxmox VE 5.1.x, the direct synchronous write
  performance is 93% slower than on kernel 4.4. Kernel 4.13 direct sync
  4KB write could only achieve 303KB/s while kernel 4.4 could achieve
  4.5MB/s.

  The VM is using ext4 filesystem and running on top of ZFS ZVOL on ZFS
  RAID1 with virtio-scsi, qemu disk cache none, and qemu disk discard
  enabled. The underlying physical disks are Samsung Enterprise SSD
  SM863a 480GB series.

  The reason I need to run kernel 4.13 to mount CephFS Luminous with
  kernel client. Hopefully CephFS Luminous kernel client will be back
  ported to kernel 4.4 in the near future.

  Is this from Ubuntu Xenial kernel 4.13 performance regression or from
  Proxmox VE 5.1 kernel 4.13 virtio-scsi performance regression?

  The test results:

  ##
  # ubuntu xenial kernel 4.13. the direct synchronous write performance is 93% 
slower than kernel 4.4
  ##
  root@localhost:~# uname -a
  Linux localhost 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 3.46369 s, 303 kB/s

  ##
  # ubuntu xenial kernel 4.4. the direct synchronous write performance is 14x 
faster than kernel 4.13
  ##
  root@localhost:~# uname -a
  Linux localhost 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.231176 s, 4.5 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Mar 25 13:43:34 2018
  InstallationDate: Installed on 2018-03-22 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 22:23 seq
   crw-rw 1 root audio 116, 33 May  7 22:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/localhost-swap
  InstallationDate: Installed on 2018-03-22 (47 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-39-generic 
root=/dev/mapper/localhost-root ro
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  dmi.product.name: Standard PC (i440FX + PIIX, 

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

2018-05-08 Thread chrone
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1758621/+attachment/5136311/+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/1758621

Title:
  Ubuntu Xenial HWE Kernel 4.13 Direct Sync Write Performance Regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Ubuntu,

  Just found out today that when using Ubuntu Xenial HWE kernel 4.13 in
  a VM on top of Proxmox VE 5.1.x, the direct synchronous write
  performance is 93% slower than on kernel 4.4. Kernel 4.13 direct sync
  4KB write could only achieve 303KB/s while kernel 4.4 could achieve
  4.5MB/s.

  The VM is using ext4 filesystem and running on top of ZFS ZVOL on ZFS
  RAID1 with virtio-scsi, qemu disk cache none, and qemu disk discard
  enabled. The underlying physical disks are Samsung Enterprise SSD
  SM863a 480GB series.

  The reason I need to run kernel 4.13 to mount CephFS Luminous with
  kernel client. Hopefully CephFS Luminous kernel client will be back
  ported to kernel 4.4 in the near future.

  Is this from Ubuntu Xenial kernel 4.13 performance regression or from
  Proxmox VE 5.1 kernel 4.13 virtio-scsi performance regression?

  The test results:

  ##
  # ubuntu xenial kernel 4.13. the direct synchronous write performance is 93% 
slower than kernel 4.4
  ##
  root@localhost:~# uname -a
  Linux localhost 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 3.46369 s, 303 kB/s

  ##
  # ubuntu xenial kernel 4.4. the direct synchronous write performance is 14x 
faster than kernel 4.13
  ##
  root@localhost:~# uname -a
  Linux localhost 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.231176 s, 4.5 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Mar 25 13:43:34 2018
  InstallationDate: Installed on 2018-03-22 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 22:23 seq
   crw-rw 1 root audio 116, 33 May  7 22:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/localhost-swap
  InstallationDate: Installed on 2018-03-22 (47 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-39-generic 
root=/dev/mapper/localhost-root ro
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  dmi.product.name: 

[Kernel-packages] [Bug 1758621] WifiSyslog.txt

2018-05-08 Thread chrone
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1758621/+attachment/5136314/+files/WifiSyslog.txt

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

** Tags added: bionic

** Description changed:

  Hi Ubuntu,
  
  Just found out today that when using Ubuntu Xenial HWE kernel 4.13 in a
  VM on top of Proxmox VE 5.1.x, the direct synchronous write performance
  is 93% slower than on kernel 4.4. Kernel 4.13 direct sync 4KB write
  could only achieve 303KB/s while kernel 4.4 could achieve 4.5MB/s.
  
  The VM is using ext4 filesystem and running on top of ZFS ZVOL on ZFS
  RAID1 with virtio-scsi, qemu disk cache none, and qemu disk discard
  enabled. The underlying physical disks are Samsung Enterprise SSD SM863a
  480GB series.
  
  The reason I need to run kernel 4.13 to mount CephFS Luminous with
  kernel client. Hopefully CephFS Luminous kernel client will be back
  ported to kernel 4.4 in the near future.
  
  Is this from Ubuntu Xenial kernel 4.13 performance regression or from
  Proxmox VE 5.1 kernel 4.13 virtio-scsi performance regression?
  
  The test results:
  
  ##
  # ubuntu xenial kernel 4.13. the direct synchronous write performance is 93% 
slower than kernel 4.4
  ##
  root@localhost:~# uname -a
  Linux localhost 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  
  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 3.46369 s, 303 kB/s
  
  ##
  # ubuntu xenial kernel 4.4. the direct synchronous write performance is 14x 
faster than kernel 4.13
  ##
  root@localhost:~# uname -a
  Linux localhost 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  
  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.231176 s, 4.5 MB/s
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Mar 25 13:43:34 2018
  InstallationDate: Installed on 2018-03-22 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 22:23 seq
   crw-rw 1 root audio 116, 33 May  7 22:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/localhost-swap
  InstallationDate: Installed on 2018-03-22 (47 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-39-generic 
root=/dev/mapper/localhost-root ro
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.11
  dmi.sys.vendor: QEMU
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw+ 1 root audio 116,  1 May  9 01:40 seq
+  

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

2018-05-08 Thread chrone
apport information

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

Title:
  Ubuntu Xenial HWE Kernel 4.13 Direct Sync Write Performance Regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Ubuntu,

  Just found out today that when using Ubuntu Xenial HWE kernel 4.13 in
  a VM on top of Proxmox VE 5.1.x, the direct synchronous write
  performance is 93% slower than on kernel 4.4. Kernel 4.13 direct sync
  4KB write could only achieve 303KB/s while kernel 4.4 could achieve
  4.5MB/s.

  The VM is using ext4 filesystem and running on top of ZFS ZVOL on ZFS
  RAID1 with virtio-scsi, qemu disk cache none, and qemu disk discard
  enabled. The underlying physical disks are Samsung Enterprise SSD
  SM863a 480GB series.

  The reason I need to run kernel 4.13 to mount CephFS Luminous with
  kernel client. Hopefully CephFS Luminous kernel client will be back
  ported to kernel 4.4 in the near future.

  Is this from Ubuntu Xenial kernel 4.13 performance regression or from
  Proxmox VE 5.1 kernel 4.13 virtio-scsi performance regression?

  The test results:

  ##
  # ubuntu xenial kernel 4.13. the direct synchronous write performance is 93% 
slower than kernel 4.4
  ##
  root@localhost:~# uname -a
  Linux localhost 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 3.46369 s, 303 kB/s

  ##
  # ubuntu xenial kernel 4.4. the direct synchronous write performance is 14x 
faster than kernel 4.13
  ##
  root@localhost:~# uname -a
  Linux localhost 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.231176 s, 4.5 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Mar 25 13:43:34 2018
  InstallationDate: Installed on 2018-03-22 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 22:23 seq
   crw-rw 1 root audio 116, 33 May  7 22:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/localhost-swap
  InstallationDate: Installed on 2018-03-22 (47 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-39-generic 
root=/dev/mapper/localhost-root ro
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  dmi.product.name: Standard PC (i440FX + 

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

2018-05-08 Thread Sandy Patterson
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1768139/+attachment/5136303/+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/1768139

Title:
  Kernel crash when booting laptop with hdmi monitor connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot a Dell Inspiron 7559 with an external monitor connected to
  the hdmi port I get a crash on bootup. I can see the following stack
  trace in journalctl:

  
  syslog contains:
   kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
    Installed: 4.15.0-20.21
    Candidate: 4.15.0-20.21
    Version table:
   *** 4.15.0-20.21 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  3) What you expected to happen
  I expected the laptop to boot to the login screen.
  4) What happened instead
  I see a blank screen after grub and have to hard power off the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:22:20 2018
  InstallationDate: Installed on 2018-04-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

  This is a fresh install. I have modified grub defaults to include 
"acpi_osi=!Windows 2015"
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   1965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash 
"acpi_osi=!Windows 2015"
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.5
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected

2018-05-08 Thread Sandy Patterson
I also confirmed the issue still persists as I captured the apport data.

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

Title:
  Kernel crash when booting laptop with hdmi monitor connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot a Dell Inspiron 7559 with an external monitor connected to
  the hdmi port I get a crash on bootup. I can see the following stack
  trace in journalctl:

  
  syslog contains:
   kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
    Installed: 4.15.0-20.21
    Candidate: 4.15.0-20.21
    Version table:
   *** 4.15.0-20.21 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Linux exposure 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  3) What you expected to happen
  I expected the laptop to boot to the login screen.
  4) What happened instead
  I see a blank screen after grub and have to hard power off the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 17:22:20 2018
  InstallationDate: Installed on 2018-04-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

  This is a fresh install. I have modified grub defaults to include 
"acpi_osi=!Windows 2015"
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apatterson   1965 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash 
"acpi_osi=!Windows 2015"
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.5
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.5
  dmi.sys.vendor: Dell Inc.

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

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


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

2018-05-08 Thread chrone
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1758621/+attachment/5136307/+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/1758621

Title:
  Ubuntu Xenial HWE Kernel 4.13 Direct Sync Write Performance Regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Ubuntu,

  Just found out today that when using Ubuntu Xenial HWE kernel 4.13 in
  a VM on top of Proxmox VE 5.1.x, the direct synchronous write
  performance is 93% slower than on kernel 4.4. Kernel 4.13 direct sync
  4KB write could only achieve 303KB/s while kernel 4.4 could achieve
  4.5MB/s.

  The VM is using ext4 filesystem and running on top of ZFS ZVOL on ZFS
  RAID1 with virtio-scsi, qemu disk cache none, and qemu disk discard
  enabled. The underlying physical disks are Samsung Enterprise SSD
  SM863a 480GB series.

  The reason I need to run kernel 4.13 to mount CephFS Luminous with
  kernel client. Hopefully CephFS Luminous kernel client will be back
  ported to kernel 4.4 in the near future.

  Is this from Ubuntu Xenial kernel 4.13 performance regression or from
  Proxmox VE 5.1 kernel 4.13 virtio-scsi performance regression?

  The test results:

  ##
  # ubuntu xenial kernel 4.13. the direct synchronous write performance is 93% 
slower than kernel 4.4
  ##
  root@localhost:~# uname -a
  Linux localhost 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 3.46369 s, 303 kB/s

  ##
  # ubuntu xenial kernel 4.4. the direct synchronous write performance is 14x 
faster than kernel 4.13
  ##
  root@localhost:~# uname -a
  Linux localhost 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.231176 s, 4.5 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Mar 25 13:43:34 2018
  InstallationDate: Installed on 2018-03-22 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 22:23 seq
   crw-rw 1 root audio 116, 33 May  7 22:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/localhost-swap
  InstallationDate: Installed on 2018-03-22 (47 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-39-generic 
root=/dev/mapper/localhost-root ro
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  dmi.product.name: Standard 

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

2018-05-08 Thread chrone
apport information

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

Title:
  Ubuntu Xenial HWE Kernel 4.13 Direct Sync Write Performance Regression

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Ubuntu,

  Just found out today that when using Ubuntu Xenial HWE kernel 4.13 in
  a VM on top of Proxmox VE 5.1.x, the direct synchronous write
  performance is 93% slower than on kernel 4.4. Kernel 4.13 direct sync
  4KB write could only achieve 303KB/s while kernel 4.4 could achieve
  4.5MB/s.

  The VM is using ext4 filesystem and running on top of ZFS ZVOL on ZFS
  RAID1 with virtio-scsi, qemu disk cache none, and qemu disk discard
  enabled. The underlying physical disks are Samsung Enterprise SSD
  SM863a 480GB series.

  The reason I need to run kernel 4.13 to mount CephFS Luminous with
  kernel client. Hopefully CephFS Luminous kernel client will be back
  ported to kernel 4.4 in the near future.

  Is this from Ubuntu Xenial kernel 4.13 performance regression or from
  Proxmox VE 5.1 kernel 4.13 virtio-scsi performance regression?

  The test results:

  ##
  # ubuntu xenial kernel 4.13. the direct synchronous write performance is 93% 
slower than kernel 4.4
  ##
  root@localhost:~# uname -a
  Linux localhost 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 3.46369 s, 303 kB/s

  ##
  # ubuntu xenial kernel 4.4. the direct synchronous write performance is 14x 
faster than kernel 4.13
  ##
  root@localhost:~# uname -a
  Linux localhost 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  root@localhost:~# dd if=/dev/zero of=/mnt/test/test bs=4K count=256 
oflag=direct,sync status=progress; rm /mnt/test/test
  1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.231176 s, 4.5 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Mar 25 13:43:34 2018
  InstallationDate: Installed on 2018-03-22 (2 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 22:23 seq
   crw-rw 1 root audio 116, 33 May  7 22:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/localhost-swap
  InstallationDate: Installed on 2018-03-22 (47 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-39-generic 
root=/dev/mapper/localhost-root ro
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-39-generic N/A
   linux-backports-modules-4.13.0-39-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.11
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.11.0-0-g63451fca13-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.11:cvnQEMU:ct1:cvrpc-i440fx-2.11:
  

[Kernel-packages] [Bug 1770006] [NEW] Test Bug

2018-05-08 Thread Joseph Salisbury
Public bug reported:

Test bug reported by jsalisbury.

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

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

Title:
  Test Bug

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Test bug reported by jsalisbury.

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

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


[Kernel-packages] [Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

2018-05-08 Thread Devin Taietta
Same here

ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND 
(20170831/dswload-210)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Exception: AE_NOT_FOUND, During 
name lookup/catalog (20170831/psobject-252)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Exception: AE_NOT_FOUND, 
(SSDT:xh_rvp10) while loading table (20170831/tbxfload-228)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: 1 table load failures, 12 
successful (20170831/tbxfload-246)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ENERGY_PERF_BIAS: Set to 'normal', 
was 'performance'
mag 08 21:41:17 devin-XPS-15-9550 kernel: ENERGY_PERF_BIAS: View and update 
with x86_energy_perf_policy(8)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: 
[\_SB_.PCI0.LPCB.H_EC.CHRG] Namespace lookup failure, AE_NOT_FOUND 
(20170831/psargs-364)
mag 08 21:41:17 devin-XPS-15-9550 kernel: No Local Variables are initialized 
for Method [PNOT]
mag 08 21:41:17 devin-XPS-15-9550 kernel: No Arguments are initialized for 
method [PNOT]
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: Method parse/execution 
failed \PNOT, AE_NOT_FOUND (20170831/psparse-550)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: Method parse/execution 
failed \_SB.AC._PSR, AE_NOT_FOUND (20170831/psparse-550)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Exception: AE_NOT_FOUND, Error 
reading AC Adapter state (20170831/ac-139)
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: 
[\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND 
(20170831/psargs-364)
mag 08 21:41:17 devin-XPS-15-9550 kernel: 
  Initialized Local Variables for 
Method [FNCL]:
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local0: 371c4672   
 Integer 0001
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local1: 9fadc1b6   
 Integer 
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local2: a1728e58   
 Integer 
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local3: 29024229   
 Integer 
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local4: 236db817   
 Integer 
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local5: 9a01c773   
 Integer 
mag 08 21:41:17 devin-XPS-15-9550 kernel:   Local6: c88fc2bf   
 Integer 
mag 08 21:41:17 devin-XPS-15-9550 kernel: No Arguments are initialized for 
method [FNCL]
mag 08 21:41:17 devin-XPS-15-9550 kernel: ACPI Error: Method parse/execution 
failed \_TZ.FNCL, AE_NOT_FOUND (20170831/psparse-550)

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

Title:
  ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure,
  AE_NOT_FOUND (20150930/dswload-210)

Status in linux package in Ubuntu:
  Invalid

Bug description:
  [ 0.016192] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, 
AE_NOT_FOUND (20150930/dswload-210)
  [ 0.016195] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog 
(20150930/psobject-227)
  [ 0.016222] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20150930/tbxfload-193)
  [ 0.021348] ACPI Error: 1 table load failures, 7 successful 
(20150930/tbxfload-214)

  
  I have noticed this ACPI error persisting in my syslog and dmesg. Based on 
what I have learnt from  ACPI, acpitool -w and lspci, I think the error is 
related to Namespaces provided in the DDST on \_SB_.PCI0.XHC_.RHUB.HS11, which 
I think concerns the Root → System bus tree → PCI bus  → USB controller: Intel 
Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) in my system. I 
have not found what .RHUB.HS11 refers too. I have tried changing my UEFI USB 
settings but to no avail. Appreciate help to fix this bug. 

  I reported it as a question
  https://answers.launchpad.net/ubuntu/+question/293489 and to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553690.
  https://launchpad.net/~penalvch advice me to make this ubuntu-bug
  report.

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

  $ uname -r
  4.4.0-22-generic

  MB Bios: ASUS z170m-plus version 0704

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sunbear1604   1905 F pulseaudio
   /dev/snd/controlC0:  sunbear1604   1905 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 07:48:53 2016
  HibernationDevice: RESUME=UUID=c1eef599-9978-461e-a399-a04370b6ae59
  InstallationDate: Installed on 2016-05-01 (20 days ago)
  

[Kernel-packages] [Bug 1768115] Traces of QEMU RAM migrations relative to dirty bitmap syncing

2018-05-08 Thread bugproxy
--- Comment (attachment only) From mdr...@us.ibm.com 2018-05-08 15:57 
EDT---


** Attachment added: "Traces of QEMU RAM migrations relative to dirty bitmap 
syncing"
   
https://bugs.launchpad.net/bugs/1768115/+attachment/5136365/+files/vm0.log.iteration2a.boslcp6.success.postmigrate.trimmed

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running
  with IO stress crashed@security_file_permission+0xf4/0x160.

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

Bug description:
  Problem Description: Migration Guest running with IO stress
  crashed@security_file_permission+0xf4/0x160 after couple of
  migrations.

  Steps to re-create:

  Source host - boslcp3
  Destination host - boslcp4

  1.boslcp3 & boslcp4 installed with latest kernel
  root@boslcp3:~# uname -a
  Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:~#

  root@boslcp4:~# uname -a
  Linux boslcp4 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:~#

  2. Installed guest boslcp3g1 with kernel and started LTP run from
  boslcp3 host

  root@boslcp3g1:~# uname -a
  Linux boslcp3g1 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux

  3. Started migrating boslcp3g1 guest from source to destination & viceversa.
  4. After couple of migrations it crashed at boslcp4 & enters into xmon

  8:mon> t
  [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160
  [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120
  [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0
  [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110
  [c004f8a23e30] c000b184 system_call+0x58/0x6c
  --- Exception: c01 (System Call) at 71f1779fe280
  SP (7fffe99ece50) is in userspace
  8:mon> S
  msr= 80001033  sprg0 = 
  pvr= 004e1202  sprg1 = c7a85800
  dec= 591e3e03  sprg2 = c7a85800
  sp = c004f8a234a0  sprg3 = 00010008
  toc= c16eae00  dar   = 023c
  srr0   = c00c355c  srr1  = 80001033 dsisr  = 4000
  dscr   =   ppr   = 0010 pir= 0011
  amr=   uamor = 
  dpdes  =   tir   =  cir= 
  fscr   = 05000180  tar   =  pspb   = 
  mmcr0  = 8000  mmcr1 =  mmcr2  = 
  pmc1   =  pmc2 =   pmc3 =   pmc4   = 
  mmcra  =    siar =  pmc5   = 026c
  sdar   =    sier =  pmc6   = 0861
  ebbhr  =   ebbrr =  bescr  = 
  iamr   = 4000
  pidr   = 0034  tidr  = 
  cpu 0x8: Vector: 700 (Program Check) at [c004f8a23220]
  pc: c00e4854: xmon_core+0x1f24/0x3520
  lr: c00e4850: xmon_core+0x1f20/0x3520
  sp: c004f8a234a0
     msr: 80041033
    current = 0xc004f89faf00
    paca= 0xc7a85800   softe: 0irq_happened: 0x01
  pid   = 24028, comm = top
  Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 (Ubuntu 
4.15.0-20.21-generic 4.15.17)
  cpu 0x8: Exception 700 (Program Check) in xmon, returning to main loop
  [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160
  [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120
  [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0
  [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110
  [c004f8a23e30] c000b184 system_call+0x58/0x6c
  --- Exception: c01 (System Call) at 71f1779fe280
  SP (7fffe99ece50) is in userspace
  8:mon> r
  R00 = c043b7fc   R16 = 
  R01 = c004f8a23c90   R17 = ff70
  R02 = c16eae00   R18 = 0a51b4bebfc8
  R03 = c00279557200   R19 = 7fffe99edbb0
  R04 = c003242499c0   R20 = 0a51b4c04db0
  R05 = 0002   R21 = 0a51b4c20e90
  R06 = 0004   R22 = 00040f00
  R07 = ff81   R23 = 0a51b4c06560
  R08 = ff80   R24 = ff80
  R09 =    R25 = 0a51b4bec2b8
  R10 =    R26 = 71f177bb0b20
  R11 =    R27 = 
  R12 = 2000   R28 = c00279557200
  R13 = c7a85800   R29 = c004c7734210
  R14 =    R30 = 
  R15 = 

[Kernel-packages] [Bug 1767409] Re: linux-kvm: 4.15.0-1009.9 -proposed tracker

2018-05-08 Thread Thadeu Lima de Souza Cascardo
** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.15.0-1009.9 -proposed tracker

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

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

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

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

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

Title:
  linux-kvm: 4.15.0-1009.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Invalid

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

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

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

-- 
Mailing list: https://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   3   4   5   6   7   8   >