date:20180626

The bt works on a cold boot.

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

Title:
  Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install
  has flakey wifi and no BT Bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On fresh install on Yoga920 of Bionic Beaver 18, wifi and bluetooth
  work.  Then they degrade with BT not working withing a day or five,
  and wifi is consistently inconsistent.  On the bluetooth gui, user is
  unable to turn bt on or off and the CLI shows no blocking on bt but it
  doesn't work.

  I think this has to do with the Qualcomm QCA6174 [168c:003e] (rev 32)
  on Ubuntu Bionic and the ath10k_pci driver but Qualcomm nor Lenovo
  have answers.

  https://paste.ubuntu.com/p/XC5PWRFywp/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.19
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 16 08:57:46 2018
  InstallationDate: Installed on 2018-06-09 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  phelix 1834 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=0690300c-b74d-4b47-925d-49298e311243
  InstallationDate: Installed on 2018-06-16 (7 days ago)
  InstallationMedia: Ubuntu 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 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Y7
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-16 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.18.0-041800rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1778844] KDump kernel captures dump successfully using regular/default initrd

2018-06-26 Thread bugproxy

Default Comment by Bridge

** Attachment added: "KDump kernel captures dump successfully using 
regular/default initrd"
   
https://bugs.launchpad.net/bugs/1778844/+attachment/5157007/+files/kdump-success-with-default-initrd.log

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in linux package in Ubuntu:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

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

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

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 0e4f79d8d5d8 0001  
7efce644
  [   73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 
0002
  [   73.058099]

[Kernel-packages] [Bug 1778844] [NEW] ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

You have been subscribed to a public bug:

Problem Description:
===
After triggering crash ,kdump is not working & system enters into initramfs 
state

Steps to re-create:
==

>. woo is installed ubuntu180401 kernel

root@woo:~# uname -a
Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le 
ppc64le ppc64le GNU/Linux
root@woo:~#

>. Crashkernel value as below

root@woo:~# free -h
  totalusedfree  shared  buff/cache   available
Mem:   503G2.0G501G 13M279M499G
Swap:  2.0G  0B2.0G

root@woo:~# cat /proc/cmdline
root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M

>  kdump status

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

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

kexec command:
  /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb 
ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib 
nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

root@woo:~# dmesg | grep Reser
[0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 
524288MB)
[0.00] cma: Reserved 26224 MiB at 0x20399500
[3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term 
"Broadcom" refers to Broadcom Limited and/or its subsidiaries.

> Triggered crash

root@woo:~# echo 1 > /proc/sys/kernel/sysrq
root@woo:~# echo c > /proc/sysrq-trigger
[   73.056308] sysrq: SysRq : Trigger a crash
[   73.056357] Unable to handle kernel paging request for data at address 
0x
[   73.056459] Faulting instruction address: 0xc07f24c8
[   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
[   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
[   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) 
ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload 
esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) 
rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto 
crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
[   73.057601]  tg3 libahci nvme_core pnv_php
[   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
[   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: c07f24a0
[   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE 
(4.15.0-23-generic)
[   73.057986] MSR:  90009033   CR: 2822  
XER: 2004
[   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
[   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
[   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
[   73.058099] GPR08: 0007 0001  
90001003
[   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

[   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
[   73.058099] GPR20: 0e4f79d8d5d8 0001  
7efce644
[   73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 
0002
[   73.058099] GPR28: 0063 0004 c1572b1c 
c15e9e68
[   73.059060] NIP [c07f24c8] sysrq_handle_crash+0x28/0x30
[   73.059142] LR [c07f3568] __handle_sysrq+0xf8/0x2c0
[   73.059215] Call Trace:
[   73.059254] [c03f8269fc70] [c07f3548] __handle_sysrq+0xd8/0x2c0 
(unreliable)
[   73.059358] [c03f8269fd10] [c07f3d74] 
write_sysrq_trigger+0x64/0x90
[   73.059456] [c03f8269fd40] [c0481248] proc_reg_write+0x88/0xd0
[   73.059543] [c03f8269fd70] [c03d43fc] __vfs_write+0x3c/0x70
[   73.059627] [c03f8269fd90] [c03d4658] vfs_write+0xd8/0x220
[   73.059716] [c03f8269fde0] [c03d4978] SyS_write+0x68/0x110
[   73.059809] [c03f8269fe30] [c000b284] system_call+0x58/0x6c
[   73.059896] Instruction dump:
[

[Kernel-packages] [Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck

2018-06-26 Thread Brian Burch

Thanks for your comment, Kai-Heng, but I did try the latest upstrem
kernel at the weekend. Please refer to my post #8.

Is there a good reason to try a kernel more recent than:-

linux-image-
unsigned-4.17.0-041700-lowlatency_4.17.0-041700.201806041953_amd64.deb

... along with its associated headers and modules packages?

If you think there is, then I'll certainly install another and test it -
I would really like to get this bug pinned down quickly, even if it
can't be fixed straight away.

It takes me an hour or so and I am rather busy at the moment, so I don't
want to waste time just to "test" a few extra but irrelevant changes...

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

Title:
  iwlwifi-29 kernel timeout queue active on fifo 2 and stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is
  down!

  Happens sometimes after a few minutes, never more than 30 minutes.
  Easy to capture journalctl when the network connection hangs. Intel
  fails on 2.4 GHz or 5 GHz, using several different AP's.

  The same system runs stable and perfect with a USB dongle Realtek
  RTL8188CUS, but I have to blacklist iwlwifi in
  /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network
  activity while simply scanning and not connected to an AP.

  I've had similar problems with this system under 17.10, but it has
  become more reproducible under 18.04. I've back-levelled the driver as
  far as possible, but they all hang the network. Because version 29
  firmware is the latest in the bionic repository, and also on the intel
  support web site, I won't confuse matters by reporting earlier ubuntu
  kernels or iwlwifi versions

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

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

Re: [Kernel-packages] [Bug 1777258] Re: Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install has flakey wifi and no BT Bluetooth

I can see BT stuff when cold booting.  Unable to test right now, but the
ability to see devices was not available before, so I think it probably
works.  It must be a resume and warm boot issue?

On Tue, Jun 26, 2018 at 9:37 PM Joshua Freedman 
wrote:

> [0.00] Linux version 4.18.0-041800rc1-generic (kernel@tangerine)
> (gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17
> 00:34:22 UTC 2018
> [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic
> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
> [0.00] KERNEL supported cpus:
> [0.00]   Intel GenuineIntel
> [0.00]   AMD AuthenticAMD
> [0.00]   Centaur CentaurHauls
> [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating
> point registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds
> registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
> [0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
> [0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
> [0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
> [0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960
> bytes, using 'compacted' format.
> [0.00] BIOS-provided physical RAM map:
> [0.00] BIOS-e820: [mem 0x-0x00057fff]
> usable
> [0.00] BIOS-e820: [mem 0x00058000-0x00058fff]
> reserved
> [0.00] BIOS-e820: [mem 0x00059000-0x0009dfff]
> usable
> [0.00] BIOS-e820: [mem 0x0009e000-0x000f]
> reserved
> [0.00] BIOS-e820: [mem 0x0010-0x27498fff]
> usable
> [0.00] BIOS-e820: [mem 0x27499000-0x27499fff] ACPI
> NVS
> [0.00] BIOS-e820: [mem 0x2749a000-0x2749afff]
> reserved
> [0.00] BIOS-e820: [mem 0x2749b000-0x28827fff]
> usable
> [0.00] BIOS-e820: [mem 0x28828000-0x29127fff]
> reserved
> [0.00] BIOS-e820: [mem 0x29128000-0x2ed3dfff]
> usable
> [0.00] BIOS-e820: [mem 0x2ed3e000-0x2ef3dfff] type
> 20
> [0.00] BIOS-e820: [mem 0x2ef3e000-0x2f72dfff]
> reserved
> [0.00] BIOS-e820: [mem 0x2f72e000-0x2ff7dfff] ACPI
> NVS
> [0.00] BIOS-e820: [mem 0x2ff7e000-0x2fffdfff] ACPI
> data
> [0.00] BIOS-e820: [mem 0x2fffe000-0x2fffefff]
> usable
> [0.00] BIOS-e820: [mem 0x2000-0x3cff]
> reserved
> [0.00] BIOS-e820: [mem 0xe000-0xefff]
> reserved
> [0.00] BIOS-e820: [mem 0xfd00-0xfe7f]
> reserved
> [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff]
> reserved
> [0.00] BIOS-e820: [mem 0xfed0-0xfed00fff]
> reserved
> [0.00] BIOS-e820: [mem 0xfed1-0xfed19fff]
> reserved
> [0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff]
> reserved
> [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff]
> reserved
> [0.00] BIOS-e820: [mem 0xffa0-0x]
> reserved
> [0.00] BIOS-e820: [mem 0x0001-0x0004c1ff]
> usable
> [0.00] NX (Execute Disable) protection: active
> [0.00] efi: EFI v2.50 by INSYDE Corp.
> [0.00] efi:  ACPI 2.0=0x2fffd014  SMBIOS=0x2efb2000  SMBIOS
> 3.0=0x2efb  ESRT=0x2efaedd8  MEMATTR=0x2ce55018
> [0.00] SMBIOS 3.0.0 present.
> [0.00] DMI: LENOVO 80Y7/LNVNB161216, BIOS 5NCN38WW 02/22/2018
> [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
> [0.00] e820: remove [mem 0x000a-0x000f] usable
> [0.00] last_pfn = 0x4c2000 max_arch_pfn = 0x4
> [0.00] MTRR default type: write-back
> [0.00] MTRR fixed ranges enabled:
> [0.00]   0-9 write-back
> [0.00]   A-B uncachable
> [0.00]   C-F write-protect
> [0.00] MTRR variable ranges enabled:
> [0.00]   0 base 008000 mask 7F8000 uncachable
> [0.00]   1 base 004000 mask 7FC000 uncachable
> [0.00]   2 base 003C00 mask 7FFC00 uncachable
> [0.00]   3 base 003A00 mask 7FFE00 uncachable
> [0.00]   4 base 003900 mask 7FFF00 uncachable
> [0.00]   5 base 003880 mask 7FFF80 uncachable
> [0.00]   6 base 20 mask 70 uncachable
> [0.00]   7 disabled
> [0.00]   8 disabled
> [0.00]   9 disabled
> [0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC-
> WT
> [0.00]

Re: [Kernel-packages] [Bug 1777258] Re: Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install has flakey wifi and no BT Bluetooth

[0.00] Linux version 4.18.0-041800rc1-generic (kernel@tangerine)
(gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17
00:34:22 UTC 2018
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960
bytes, using 'compacted' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x00057fff] usable
[0.00] BIOS-e820: [mem 0x00058000-0x00058fff]
reserved
[0.00] BIOS-e820: [mem 0x00059000-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x000f]
reserved
[0.00] BIOS-e820: [mem 0x0010-0x27498fff] usable
[0.00] BIOS-e820: [mem 0x27499000-0x27499fff] ACPI
NVS
[0.00] BIOS-e820: [mem 0x2749a000-0x2749afff]
reserved
[0.00] BIOS-e820: [mem 0x2749b000-0x28827fff] usable
[0.00] BIOS-e820: [mem 0x28828000-0x29127fff]
reserved
[0.00] BIOS-e820: [mem 0x29128000-0x2ed3dfff] usable
[0.00] BIOS-e820: [mem 0x2ed3e000-0x2ef3dfff] type
20
[0.00] BIOS-e820: [mem 0x2ef3e000-0x2f72dfff]
reserved
[0.00] BIOS-e820: [mem 0x2f72e000-0x2ff7dfff] ACPI
NVS
[0.00] BIOS-e820: [mem 0x2ff7e000-0x2fffdfff] ACPI
data
[0.00] BIOS-e820: [mem 0x2fffe000-0x2fffefff] usable
[0.00] BIOS-e820: [mem 0x2000-0x3cff]
reserved
[0.00] BIOS-e820: [mem 0xe000-0xefff]
reserved
[0.00] BIOS-e820: [mem 0xfd00-0xfe7f]
reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff]
reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff]
reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed19fff]
reserved
[0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff]
reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff]
reserved
[0.00] BIOS-e820: [mem 0xffa0-0x]
reserved
[0.00] BIOS-e820: [mem 0x0001-0x0004c1ff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.50 by INSYDE Corp.
[0.00] efi:  ACPI 2.0=0x2fffd014  SMBIOS=0x2efb2000  SMBIOS
3.0=0x2efb  ESRT=0x2efaedd8  MEMATTR=0x2ce55018
[0.00] SMBIOS 3.0.0 present.
[0.00] DMI: LENOVO 80Y7/LNVNB161216, BIOS 5NCN38WW 02/22/2018
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] last_pfn = 0x4c2000 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 008000 mask 7F8000 uncachable
[0.00]   1 base 004000 mask 7FC000 uncachable
[0.00]   2 base 003C00 mask 7FFC00 uncachable
[0.00]   3 base 003A00 mask 7FFE00 uncachable
[0.00]   4 base 003900 mask 7FFF00 uncachable
[0.00]   5 base 003880 mask 7FFF80 uncachable
[0.00]   6 base 20 mask 70 uncachable
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC-
WT
[0.00] last_pfn = 0x2 max_arch_pfn = 0x4
[0.00] esrt: Reserving ESRT space from 0x2efaedd8 to
0x2efaee60.
[0.00] Scanning 1 areas for low memory corruption
[0.00] Base memory trampoline at [(ptrval)] 98000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x35295a000, 0x35295afff] PGTABLE
[0.00] BRK [0x35295b000, 0x35295bfff] PGTABLE
[0.00] BRK

[Kernel-packages] [Bug 1762989] Re: Display Port issues - screen blackouts

[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/1762989

Title:
  Display Port issues - screen blackouts

Status in linux package in Ubuntu:
  Expired

Bug description:
  I use a Philips BDM4037U 40'', 4k monitor.
  Connecting it via DP to my Lenovo 910 4k gives me random blackouts.

  It appears to me that this mostly happens after some time of work,
  also more likely when the CPU has to handle more than average load,
  sooner in 30Hz than in 60Hz mode. But it happens for sure after some
  time, each day.

  I was unsure if this is a problem with the monitor itself (although when 
connected via HDMI this isn't an issue).
  I found similar bug reports for Windows, where it was suggested to update the 
firmware.
  My laptop has updated everything - a current BIOS (which dates back to June 
2017 or so), updated Windows, latest Ubuntu.
  The same problem existed in 17.10, with x-org and Wayland sessions.

  Note, there is another issue with this monitor filed by me, but
  unrelated AFAIK:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762986

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thet   1429 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 11 12:07:06 2018
  HibernationDevice: RESUME=UUID=bedd1248-32dd-43ca-be9f-28337086ea86
  InstallationDate: Installed on 2018-04-09 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: LENOVO 80VF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=998520ff-c841-45ab-8312-2bb876ae2a0b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Agera
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 910-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80VF
  dmi.product.version: Lenovo YOGA 910-13IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1767443] Re: regular hard lockup on bionic kernel

[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/1767443

Title:
  regular hard lockup on bionic kernel

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

Bug description:
  Hi guys,

  I'm sorry I have no real information to add to this, but Serge
  encouraged me to file a bug to get you guys to help me to debug this,
  so blame him.

  I've been running the bionic kernels on a thinkpad X1 carbon 3rd
  generation for several months, and experiencing 2x hard lockups per
  day. Nothing in /var/log/kern.log looks very obvious to me, and I'm
  not lucky enough to get a stack trace or anything.

  Attached are the `ubuntu-bug linux` things that are uploaded
  automatically, but I'm happy to do whatever science experiments are
  necessary to get further info.

  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
  Date: Fri Apr 27 10:45:49 2018
  InstallationDate: Installed on 2017-11-13 (164 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (48 days ago)

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

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

[Kernel-packages] [Bug 1767443] Re: regular hard lockup on bionic kernel

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

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

Title:
  regular hard lockup on bionic kernel

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

Bug description:
  Hi guys,

  I'm sorry I have no real information to add to this, but Serge
  encouraged me to file a bug to get you guys to help me to debug this,
  so blame him.

  I've been running the bionic kernels on a thinkpad X1 carbon 3rd
  generation for several months, and experiencing 2x hard lockups per
  day. Nothing in /var/log/kern.log looks very obvious to me, and I'm
  not lucky enough to get a stack trace or anything.

  Attached are the `ubuntu-bug linux` things that are uploaded
  automatically, but I'm happy to do whatever science experiments are
  necessary to get further info.

  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
  Date: Fri Apr 27 10:45:49 2018
  InstallationDate: Installed on 2017-11-13 (164 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (48 days ago)

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

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

[Kernel-packages] [Bug 1777258] Re: Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install has flakey wifi and no BT Bluetooth

I guess you warm booted instead of cold booted your system?

Please power off the system, and boot with v4.18-rc1 again.

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

Title:
  Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install
  has flakey wifi and no BT Bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On fresh install on Yoga920 of Bionic Beaver 18, wifi and bluetooth
  work.  Then they degrade with BT not working withing a day or five,
  and wifi is consistently inconsistent.  On the bluetooth gui, user is
  unable to turn bt on or off and the CLI shows no blocking on bt but it
  doesn't work.

  I think this has to do with the Qualcomm QCA6174 [168c:003e] (rev 32)
  on Ubuntu Bionic and the ath10k_pci driver but Qualcomm nor Lenovo
  have answers.

  https://paste.ubuntu.com/p/XC5PWRFywp/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.19
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 16 08:57:46 2018
  InstallationDate: Installed on 2018-06-09 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  phelix 1834 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=0690300c-b74d-4b47-925d-49298e311243
  InstallationDate: Installed on 2018-06-16 (7 days ago)
  InstallationMedia: Ubuntu 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 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Y7
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-16 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.18.0-041800rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)

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

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

Title:
  wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware
  (-22)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Fix Committed
Status in plymouth source package in Artful:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in plymouth source package in Bionic:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  Message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from
  hardware (-22)" showed when the system shutdown.

  [Test]
  Users confirmed the patch fixes their issue.

  [Regression Potential]
  Low. It's in mainline Linux, limited to iwlwifi, trivial change.

  Sara Sharon (1):
iwlwifi: mvm: fix "failed to remove key" message

  ==Original Bug Report===
  When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I get a 
hung shutdown with the message "wlp3s0: failed to remove key (1, 
ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to load 
firmware versions that do not exist on the system i.e. versions 33 then 32 of 
the firmware. It then seems to load version 31 of the firmware. Wireless 
features seem to work normally. The issues are just at shutdown time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1621 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Oct  3 06:12:13 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 13d3:5755 IMC Networks
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1773905] Re: Support UVC1.5 Camera for Xenial

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

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

Title:
  Support UVC1.5 Camera for Xenial

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

Bug description:
  ===SRU Justification===
  [Impact]
  UVC1.5 USB class is not in UVC driver's device ID, so the driver doesn't get 
loaded.

  [Test]
  See if the uvcvideo module is loaded for UVC1.5 camera.
  I can confirm with this commit, uvcvideo.ko is loaded. In addition, cheese 
can use the webcam without issue.

  [Fix]
  Add UVC1.5 device id to uvcvideo. 

  [Regression Potential]
  Low. The short control message is already fixed by another commit.

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

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

[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

2018-06-26 Thread Tyler Hicks

@Breno since the missing commits are only for improved reporting of
vulnerability status, does IBM consider them to be needed for Ubuntu
14.04's 3.13 kernel? (Ubuntu 17.10's 4.13 kernel will go EoL soon so it
probably won't receive the changes)

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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

[Kernel-packages] [Bug 1777258] Re: Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install has flakey wifi and no BT Bluetooth

[0.00] Linux version 4.18.0-041800rc1-generic (kernel@tangerine) (gcc 
version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17 00:34:22 
UTC 2018
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 
bytes, using 'compacted' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x00057fff] usable
[0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved
[0.00] BIOS-e820: [mem 0x00059000-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x27498fff] usable
[0.00] BIOS-e820: [mem 0x27499000-0x27499fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x2749a000-0x2749afff] reserved
[0.00] BIOS-e820: [mem 0x2749b000-0x28827fff] usable
[0.00] BIOS-e820: [mem 0x28828000-0x29127fff] reserved
[0.00] BIOS-e820: [mem 0x29128000-0x2ed3dfff] usable
[0.00] BIOS-e820: [mem 0x2ed3e000-0x2ef3dfff] type 20
[0.00] BIOS-e820: [mem 0x2ef3e000-0x2f72dfff] reserved
[0.00] BIOS-e820: [mem 0x2f72e000-0x2ff7dfff] ACPI NVS
[0.00] BIOS-e820: [mem 0x2ff7e000-0x2fffdfff] ACPI data
[0.00] BIOS-e820: [mem 0x2fffe000-0x2fffefff] usable
[0.00] BIOS-e820: [mem 0x2000-0x3cff] reserved
[0.00] BIOS-e820: [mem 0xe000-0xefff] reserved
[0.00] BIOS-e820: [mem 0xfd00-0xfe7f] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved
[0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xffa0-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x0004c1ff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.50 by INSYDE Corp.
[0.00] efi:  ACPI 2.0=0x2fffd014  SMBIOS=0x2efb2000  SMBIOS 
3.0=0x2efb  ESRT=0x2efaedd8  MEMATTR=0x2ce55018 
[0.00] SMBIOS 3.0.0 present.
[0.00] DMI: LENOVO 80Y7/LNVNB161216, BIOS 5NCN38WW 02/22/2018
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] last_pfn = 0x4c2000 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 008000 mask 7F8000 uncachable
[0.00]   1 base 004000 mask 7FC000 uncachable
[0.00]   2 base 003C00 mask 7FFC00 uncachable
[0.00]   3 base 003A00 mask 7FFE00 uncachable
[0.00]   4 base 003900 mask 7FFF00 uncachable
[0.00]   5 base 003880 mask 7FFF80 uncachable
[0.00]   6 base 20 mask 70 uncachable
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.00] last_pfn = 0x2 max_arch_pfn = 0x4
[0.00] esrt: Reserving ESRT space from 0x2efaedd8 to 
0x2efaee60.
[0.00] Scanning 1 areas for low memory corruption
[0.00] Base memory trampoline at [(ptrval)] 98000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x34c55a000, 0x34c55afff] PGTABLE
[0.00] BRK [0x34c55b000, 0x34c55bfff] PGTABLE
[0.00] BRK

[Kernel-packages] [Bug 1777258] Re: Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install has flakey wifi and no BT Bluetooth

Anything specific I should be looking for?  When I dmesg its a pretty
long list.

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

Title:
  Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install
  has flakey wifi and no BT Bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On fresh install on Yoga920 of Bionic Beaver 18, wifi and bluetooth
  work.  Then they degrade with BT not working withing a day or five,
  and wifi is consistently inconsistent.  On the bluetooth gui, user is
  unable to turn bt on or off and the CLI shows no blocking on bt but it
  doesn't work.

  I think this has to do with the Qualcomm QCA6174 [168c:003e] (rev 32)
  on Ubuntu Bionic and the ath10k_pci driver but Qualcomm nor Lenovo
  have answers.

  https://paste.ubuntu.com/p/XC5PWRFywp/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.19
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 16 08:57:46 2018
  InstallationDate: Installed on 2018-06-09 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  phelix 1834 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=0690300c-b74d-4b47-925d-49298e311243
  InstallationDate: Installed on 2018-06-16 (7 days ago)
  InstallationMedia: Ubuntu 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 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Y7
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-16 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.18.0-041800rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1778511] Re: PCI network card (r8169) UNCLAIMED at boot

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

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

Title:
  PCI network card (r8169) UNCLAIMED at boot

Status in linux package in Ubuntu:
  Invalid

Bug description:
  2 network interfaces installed - Intel and Realtek. Intel (onboard) no 
problem. Realtek (PCI Express) not loaded at boot.
  lshw -C network (after boot) shows
   *-network UNCLAIMED
 description: Ethernet controller
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:05:00.0
 version: 06
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd cap_list
 configuration: latency=0
 resources: ioport:d000(size=256) memory:f7c0-f7c00fff 
memory:f000-f0003fff

  sudo modprobe -r r8169 & sudo  modprobe r8169 loads driver

  lshw -C network then gives
   *-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:05:00.0
 logical name: enp5s0
 version: 06
 serial: 98:de:d0:06:2e:68
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl_nic/rtl8168e-2.fw 
ip=192.168.2.6 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
 resources: irq:32 ioport:d000(size=256) memory:f7c0-f7c00fff 
memory:f000-f0003fff

  INTEL
  *-network 
 description: Ethernet interface
 product: Ethernet Connection I217-V
 vendor: Intel Corporation
 physical id: 19
 bus info: pci@:00:19.0
 logical name: eno1
 version: 04
 serial: 74:d0:2b:9e:f5:fb
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 32 bits
 clock: 33MHz
 capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=3.2.6-k duplex=full firmware=0.13-4 ip=192.168.1.64 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:27 memory:f7f0-f7f1 memory:f7f3d000-f7f3dfff 
ioport:f080(size=32)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard4495 F pulseaudio
   /dev/snd/controlC1:  richard4495 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 13:15:42 2018
  HibernationDevice: RESUME=UUID=03521e66-171a-4e66-bc2e-650c385fbefc
  InstallationDate: Installed on 2013-10-18 (1710 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=496abb27-03bd-48e8-81b3-bdb5f4aea244 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-15 (41 days ago)
  dmi.bios.date: 05/17/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1007
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1007:bd05/17/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1772154] Re: Unstable WiFi adapter Gigabyte GC-WB867D-I

Follow #22 and file a bug to let Intel iwlwifi developers know.

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

Title:
  Unstable WiFi adapter Gigabyte GC-WB867D-I

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The WiFi adapter Gigabyte GC-WB867D-I is quite unstable on Ubuntu
  18.04. I do not have data relative to previous versions of Ubuntu
  since this PCIe card is part of a new build that has had 18.04 as the
  first installed version.

  The reason why I can point the finger at the Linux kernel is that the
  card seems to work reliably well on Windows 10 (no packet loss when
  pinging the local router). On Ubuntu 18.04, the card's behaviour seems
  very correlated to the signal strength and exhibits a threshold
  phenomenon. With the antenna placed in an obstacle-free area, some
  ping packets are occasionally lost. But when some objects are placed
  near the antenna (e.g. a phone), the packet loss can get up to 90%.
  Under the very same conditions, the packet loss on Windows is exactly
  0 (and the RTT never gets above 500ms).

  I have disabled the WiFi power saving (changed from 2 to 3) but that
  didn't fix the problem. It seems that restarting the NetworkManager
  service helps for a bit, but after a while the problem resurfaces.

  The card in question has onboard USB Bluetooth and is pretty much an
  M.2 to PCIe x1 adapter for an Intel Wifi adapter. The relevant output
  of lspci is

  03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275
  (rev 78)

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 10:32:00 2018
  InstallationDate: Installed on 2018-04-29 (19 days ago)
  InstallationMedia: Ubuntu 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/pcmC1D7p:   gabriele   1893 F...m pulseaudio
   /dev/snd/controlC1:  gabriele   1893 F pulseaudio
   /dev/snd/controlC0:  gabriele   1893 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=d2390d6b-2bc3-41bb-b385-3dd8921a36e2
  InstallationDate: Installed on 2018-04-29 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=2e79827f-410a-4aba-ab8f-e278ca6e7aa3 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
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B360M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd03/07/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB360MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1777258] Re: Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install has flakey wifi and no BT Bluetooth

Can you attach dmesg when BT failed to work?

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

Title:
  Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install
  has flakey wifi and no BT Bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On fresh install on Yoga920 of Bionic Beaver 18, wifi and bluetooth
  work.  Then they degrade with BT not working withing a day or five,
  and wifi is consistently inconsistent.  On the bluetooth gui, user is
  unable to turn bt on or off and the CLI shows no blocking on bt but it
  doesn't work.

  I think this has to do with the Qualcomm QCA6174 [168c:003e] (rev 32)
  on Ubuntu Bionic and the ath10k_pci driver but Qualcomm nor Lenovo
  have answers.

  https://paste.ubuntu.com/p/XC5PWRFywp/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.19
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 16 08:57:46 2018
  InstallationDate: Installed on 2018-06-09 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  phelix 1834 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=0690300c-b74d-4b47-925d-49298e311243
  InstallationDate: Installed on 2018-06-16 (7 days ago)
  InstallationMedia: Ubuntu 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 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Y7
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-16 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.18.0-041800rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1776443] Re: iwlwifi-29 kernel timeout queue active on fifo 2 and stuck

Please give #3 a try...

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

Title:
  iwlwifi-29 kernel timeout queue active on fifo 2 and stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dell inspiron 15 3565 and intel 3165. Difficult to report when wifi is
  down!

  Happens sometimes after a few minutes, never more than 30 minutes.
  Easy to capture journalctl when the network connection hangs. Intel
  fails on 2.4 GHz or 5 GHz, using several different AP's.

  The same system runs stable and perfect with a USB dongle Realtek
  RTL8188CUS, but I have to blacklist iwlwifi in
  /etc/modprobe.d/modprobe.conf to prevent iwlwifi hanging all network
  activity while simply scanning and not connected to an AP.

  I've had similar problems with this system under 17.10, but it has
  become more reproducible under 18.04. I've back-levelled the driver as
  far as possible, but they all hang the network. Because version 29
  firmware is the latest in the bionic repository, and also on the intel
  support web site, I won't confuse matters by reporting earlier ubuntu
  kernels or iwlwifi versions

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

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

[Kernel-packages] [Bug 1776080] Re: After initial install of Bionic, bluetooth stops working QCA6714

2018-06-26 Thread Daniel van Vugt

Sorry, I found the lsusb output you have already provided in:
  http://paste.ubuntu.com/p/XC5PWRFywp/

Please just send us the output from 'journalctl' after the problem
occurs.

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

Title:
  After initial install of Bionic, bluetooth stops working QCA6714

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed fresh Bionic, everything works.  After a few hours,
  bluetooth stops working on Qualcomm QCA6714, Lenovo Yoga 920.
  Duplicated it twice.

  From CLI, it indicates that everything is unblocked and operational.
  From GUI, can't get BT switch to turn on BT.  Nothing I found online
  could fix BT.  Requested driver from Qualcomm. No help.

  http://paste.ubuntu.com/p/XC5PWRFywp/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.19
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 10 10:34:49 2018
  InstallationDate: Installed on 2018-06-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1776080] Re: After initial install of Bionic, bluetooth stops working QCA6714

2018-06-26 Thread Daniel van Vugt

Thanks.

It looks like some unusual things are happening in the kernel a couple
of times:

[   81.158861] ath10k_pci :6b:00.0: Unknown eventid: 118809
[   81.161868] ath10k_pci :6b:00.0: Unknown eventid: 90118

and

[ 9845.821302] ath10k_pci :6b:00.0: Unknown eventid: 118809
[ 9845.824344] ath10k_pci :6b:00.0: Unknown eventid: 90118

So this may be a problem with the kernel module.

Can you please also send us output from 'lsusb' and 'journalctl'?
Ideally just after the problem has occurred.


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

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

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

Title:
  After initial install of Bionic, bluetooth stops working QCA6714

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed fresh Bionic, everything works.  After a few hours,
  bluetooth stops working on Qualcomm QCA6714, Lenovo Yoga 920.
  Duplicated it twice.

  From CLI, it indicates that everything is unblocked and operational.
  From GUI, can't get BT switch to turn on BT.  Nothing I found online
  could fix BT.  Requested driver from Qualcomm. No help.

  http://paste.ubuntu.com/p/XC5PWRFywp/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.19
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 10 10:34:49 2018
  InstallationDate: Installed on 2018-06-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

2018-06-26 Thread Tyler Hicks

The Artful 4.13 kernel has already received some of these fixes in
4.13.0-43.48 and the same is true for the Trusty 3.13 kernel in
3.13.0-151.201.

They contain these patches:

- powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags
- powerpc: Add security feature flags for Spectre/Meltdown
- powerpc/pseries: Set or clear security feature flags
- powerpc/powernv: Set or clear security feature flags
- powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()
- powerpc/pseries: Use the security flags in pseries_setup_rfi_flush()

The missing commits in both kernels are:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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

[Kernel-packages] [Bug 1771783] Re: iproute2: frr route protocols are not converted to string on xenial

2018-06-26 Thread Ubuntu Foundations Team Bug Bot

The attachment "proposed-patch-1.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  iproute2: frr route protocols are not converted to string on xenial

Status in iproute2 package in Ubuntu:
  New

Bug description:
  FRR puts its own proto numbers when inserting a route, example:
  $ ip route
  [snip]
  2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

  iproute2 defines some protocols, but not all:
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

  A patch has been pushed upstream so that external applications can define 
their protocols numbers:
  719e331ff619 ("Add support for rt_protos.d")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

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

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

[Kernel-packages] [Bug 1778772] Re: linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.15.0-1010.10~16.04.1 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: 1776333
  phase: Uploaded

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

Title:
  linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 4.15.0-1010.10~16.04.1 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: 1776333
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1760099] Re: Additional spectre and meltdown patches

2018-06-26 Thread Tyler Hicks

The Xenial 4.4 kernel was fixed in 4.4.0-127.153:

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

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

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

Title:
  Additional spectre and meltdown patches

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Breno Leitao  - 2018-03-29 08:53:56 ==
  Hi Canonical,

  There are some additional patches for Spectre and Meltdown that is
  required on ppc64el. We would need to have them included on all Ubuntu
  kernels.

  This is the patch series:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown 
   
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   [v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() [v2,01/10] powerpc: Add security feature 
flags for Spectre/Meltdown
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()   
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()[v2,01/10] powerpc: 
Add security feature flags for Spectre/Meltdown
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 
[v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown 

  http://patchwork.ozlabs.org/project/linuxppc-
  dev/list/?series=36012=*

  == Comment: #1 - Breno Leitao  - 2018-03-29 08:55:48 ==
  This is a better formatted patch series list:

  [v2,10/10] powerpc/64s: Wire up cpu_show_spectre_v2() 

 
  [v2,09/10] powerpc/64s: Wire up cpu_show_spectre_v1()   
  [v2,08/10] powerpc/pseries: Use the security flags in 
pseries_setup_rfi_flush() 
  [v2,07/10] powerpc/powernv: Use the security flags in pnv_setup_rfi_flus()
  
  [v2,06/10] powerpc/64s: Enhance the information in cpu_show_meltdown()  
  [v2,05/10] powerpc/64s: Move cpu_show_meltdown()
  [v2,04/10] powerpc/powernv: Set or clear security feature flags 
  [v2,03/10] powerpc/pseries: Set or clear security feature flags 
  [v2,02/10] powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags 
  [v2,01/10] powerpc: Add security feature flags for Spectre/Meltdown

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

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

[Kernel-packages] [Bug 1778772] Re: linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

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

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

** Description changed:

  This bug is for tracking the 4.15.0-1010.10~16.04.1 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: 1776333
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Tuesday, 26. June 2018 23:00 UTC

** Description changed:

  This bug is for tracking the 4.15.0-1010.10~16.04.1 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: 1776333
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Tuesday, 26. June 2018 23:00 UTC
+ phase: Uploaded

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

Title:
  linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 4.15.0-1010.10~16.04.1 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: 1776333
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1778555] Re: My Webcam does not work with Cheese

2018-06-26 Thread Victor Porton

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

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

Title:
  My Webcam does not work with Cheese

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cheese says that there is no video cam. The same webcam (connected
  through USB 3) does work in Skype.

  From dmesg:

  [1.329876] usb 3-2: New USB device found, idVendor=17a1, idProduct=0128
  [1.329877] usb 3-2: New USB device strings: Mfr=32, Product=38, 
SerialNumber=0
  [1.329878] usb 3-2: Product: USB2.0 JPEG WebCam
  [1.329879] usb 3-2: Manufacturer: TASCORP

  From dmidecode (about my motherboard):

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: Gigabyte Technology Co., Ltd.
  Product Name: H67A-UD3H
  Version:  
  Serial Number:  
  UUID: ----1C6F65886700
  Wake-up Type: Power Switch
  SKU Number:  
  Family:  

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

  $ dpkg -s cheese
  Package: cheese
  Status: install ok installed
  Priority: optional
  Section: gnome
  Installed-Size: 437
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 3.28.0-1ubuntu1
  Depends: libc6 (>= 2.4), libcanberra-gtk3-0 (>= 0.25), libcheese-gtk25 (>= 
3.18.0), libcheese8 (>= 3.18.0), libclutter-1.0-0 (>= 1.16), 
libclutter-gtk-1.0-0 (>= 0.91.8), libgdk-pixbuf2.0-0 (>= 2.25.2), libglib2.0-0 
(>= 2.39.90), libgnome-desktop-3-17 (>= 3.17.92), libgstreamer1.0-0 (>= 1.0.0), 
libgtk-3-0 (>= 3.13.7), cheese-common (>= 3.28.0-1ubuntu1), gnome-video-effects
  Recommends: gvfs, yelp
  Suggests: gnome-video-effects-frei0r
  Description: tool to take pictures and videos from your webcam
   A webcam application that supports image and video capture. Makes
   it easy to take photos and videos of you, your friends, pets or whatever
   you want. Allows you to apply fancy visual effects, fine-control image
   settings and has features such as Multi-Burst mode, Countdown timer
   for photos.
  Homepage: https://wiki.gnome.org/Apps/Cheese
  Original-Maintainer: Debian GNOME Maintainers 


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 19:11:59 2018
  InstallationDate: Installed on 2018-06-23 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: H67A-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd11/02/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67A-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67A-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67A-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  porton 1424 F pulseaudio
   /dev/snd/controlC0:  porton 1424 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-23 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

[Kernel-packages] [Bug 1778798] Re: zedit doesn't open file in vm mode

2018-06-26 Thread Paul White

** Tags added: xenial

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

Title:
  zedit doesn't open file in vm mode

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  fis-gtm installed in Ubuntu environment.  zfs-zed package installed to
  create and edit M routines.  Using zed command doesn't open file.

  --
  Description:Ubuntu 16.04.4 LTS
  Release:16.04
  --
  Package: zfs-zed
  --
  Expected action was the file opened in vm editor.
  --
  Actual action was the file wasn't opened.

  cemberger@cemberger-PC:/$ sudo zed "usr/staff/TESTING"
  cemberger@cemberger-PC:/$ ls usr/staff
  TESTING
  cemberger@cemberger-PC:/$ sudo zed "cprac"
  cemberger@cemberger-PC:/$ sudo zed "ccc"
  cemberger@cemberger-PC:/$

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

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

Re: [Kernel-packages] [Bug 1778511] Re: PCI network card (r8169) UNCLAIMED at boot

2018-06-26 Thread Richard Wall

Indeed there was - in /etc/modprobe.d for r8168-dkms. I ran sudo apt-get 
purge --auto-remove r8168-dkms
and all is working as it should.

Many thanks for your help.

On 26/06/18 16:02, Kai-Heng Feng wrote:
> Is there any entry in /etc/modprobe.conf or /etc/modprobe.d that is
> r8168/r8169?
>

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

Title:
  PCI network card (r8169) UNCLAIMED at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  2 network interfaces installed - Intel and Realtek. Intel (onboard) no 
problem. Realtek (PCI Express) not loaded at boot.
  lshw -C network (after boot) shows
   *-network UNCLAIMED
 description: Ethernet controller
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:05:00.0
 version: 06
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd cap_list
 configuration: latency=0
 resources: ioport:d000(size=256) memory:f7c0-f7c00fff 
memory:f000-f0003fff

  sudo modprobe -r r8169 & sudo  modprobe r8169 loads driver

  lshw -C network then gives
   *-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:05:00.0
 logical name: enp5s0
 version: 06
 serial: 98:de:d0:06:2e:68
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl_nic/rtl8168e-2.fw 
ip=192.168.2.6 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
 resources: irq:32 ioport:d000(size=256) memory:f7c0-f7c00fff 
memory:f000-f0003fff

  INTEL
  *-network 
 description: Ethernet interface
 product: Ethernet Connection I217-V
 vendor: Intel Corporation
 physical id: 19
 bus info: pci@:00:19.0
 logical name: eno1
 version: 04
 serial: 74:d0:2b:9e:f5:fb
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 32 bits
 clock: 33MHz
 capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=3.2.6-k duplex=full firmware=0.13-4 ip=192.168.1.64 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:27 memory:f7f0-f7f1 memory:f7f3d000-f7f3dfff 
ioport:f080(size=32)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard4495 F pulseaudio
   /dev/snd/controlC1:  richard4495 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 13:15:42 2018
  HibernationDevice: RESUME=UUID=03521e66-171a-4e66-bc2e-650c385fbefc
  InstallationDate: Installed on 2013-10-18 (1710 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=496abb27-03bd-48e8-81b3-bdb5f4aea244 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-15 (41 days ago)
  dmi.bios.date: 05/17/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1007
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1007:bd05/17/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1778555] Re: My Webcam does not work with Cheese

2018-06-26 Thread Victor Porton

It does not work with the upstream kernel.

(By the way, I realize that this is not a place to get support, but you
should help the bug reported to test: Is it good to run my production PC
with the upstream kernel from now on? or it it better to uninstall it
after finishing testing?)

Also: I told that it does work with Skype by mistake. Video cam does not
work in Skype, too.

$ uname -a
Linux victor-pc 4.18.0-041800rc2-generic #201806241430 SMP Sun Jun 24 14:33:07 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
~,0$ cheese 

(cheese:2433): Gtk-WARNING **: 01:11:18.402: Theme parsing error: 
cheese.css:7:35: The style property GtkScrollbar:min-slider-length is 
deprecated and shouldn't be used anymore. It will be removed in a future version
** Message: 01:11:18.486: cheese-application.vala:211: Error during camera 
setup: No device found


(cheese:2433): cheese-CRITICAL **: 01:11:18.497: cheese_camera_device_get_name: 
assertion 'CHEESE_IS_CAMERA_DEVICE (device)' failed

(cheese:2433): GLib-CRITICAL **: 01:11:18.497: g_variant_new_string:
assertion 'string != NULL' failed

(cheese:2433): GLib-CRITICAL **: 01:11:18.497: g_variant_ref_sink:
assertion 'value != NULL' failed

(cheese:2433): GLib-GIO-CRITICAL **: 01:11:18.497:
g_settings_schema_key_type_check: assertion 'value != NULL' failed

(cheese:2433): GLib-CRITICAL **: 01:11:18.497:
g_variant_get_type_string: assertion 'value != NULL' failed

(cheese:2433): GLib-GIO-CRITICAL **: 01:11:18.497: g_settings_set_value:
key 'camera' in 'org.gnome.Cheese' expects type 's', but a GVariant of
type '(null)' was given

(cheese:2433): GLib-CRITICAL **: 01:11:18.497: g_variant_unref:
assertion 'value != NULL' failed

** (cheese:2433): CRITICAL **: 01:11:18.497:
cheese_preferences_dialog_setup_resolutions_for_device: assertion
'device != NULL' failed

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

Title:
  My Webcam does not work with Cheese

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cheese says that there is no video cam. The same webcam (connected
  through USB 3) does work in Skype.

  From dmesg:

  [1.329876] usb 3-2: New USB device found, idVendor=17a1, idProduct=0128
  [1.329877] usb 3-2: New USB device strings: Mfr=32, Product=38, 
SerialNumber=0
  [1.329878] usb 3-2: Product: USB2.0 JPEG WebCam
  [1.329879] usb 3-2: Manufacturer: TASCORP

  From dmidecode (about my motherboard):

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: Gigabyte Technology Co., Ltd.
  Product Name: H67A-UD3H
  Version:  
  Serial Number:  
  UUID: ----1C6F65886700
  Wake-up Type: Power Switch
  SKU Number:  
  Family:  

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

  $ dpkg -s cheese
  Package: cheese
  Status: install ok installed
  Priority: optional
  Section: gnome
  Installed-Size: 437
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 3.28.0-1ubuntu1
  Depends: libc6 (>= 2.4), libcanberra-gtk3-0 (>= 0.25), libcheese-gtk25 (>= 
3.18.0), libcheese8 (>= 3.18.0), libclutter-1.0-0 (>= 1.16), 
libclutter-gtk-1.0-0 (>= 0.91.8), libgdk-pixbuf2.0-0 (>= 2.25.2), libglib2.0-0 
(>= 2.39.90), libgnome-desktop-3-17 (>= 3.17.92), libgstreamer1.0-0 (>= 1.0.0), 
libgtk-3-0 (>= 3.13.7), cheese-common (>= 3.28.0-1ubuntu1), gnome-video-effects
  Recommends: gvfs, yelp
  Suggests: gnome-video-effects-frei0r
  Description: tool to take pictures and videos from your webcam
   A webcam application that supports image and video capture. Makes
   it easy to take photos and videos of you, your friends, pets or whatever
   you want. Allows you to apply fancy visual effects, fine-control image
   settings and has features such as Multi-Burst mode, Countdown timer
   for photos.
  Homepage: https://wiki.gnome.org/Apps/Cheese
  Original-Maintainer: Debian GNOME Maintainers 


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 19:11:59 2018
  InstallationDate: Installed on 2018-06-23 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: H67A-UD3H
  dmi.board.vendor:

[Kernel-packages] [Bug 1778765] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk

2018-06-26 Thread Jun Kong

precisely, its size is 0 and hence lsblk ignores it without option -a.

# lsblk -a
NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0 7:00 0 loop
loop1 7:10 0 loop
loop2 7:20 0 loop
loop3 7:30 0 loop
loop4 7:40 0 loop
loop5 7:50 0 loop
loop6 7:60 0 loop
loop7 7:70 0 loop
sda   8:00 465.8G  0 disk
├─sda18:10   476M  0 part /boot
├─sda28:20  30.8G  0 part [SWAP]
└─sda38:30 434.6G  0 part /
sdb   8:16   0 931.5G  0 disk
sr0  11:01  1024M  0 rom
nvme0n1 259:00 0 disk

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

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following the suggestion #12 on bug 1758205 to raise a new one

  
  I have updated kernel to 4.15.0-23-generic and still see the problem reported 
in 1758205:

  root@localhost:/sys/block# nvme list
  Node SN Model Namespace Usage Format FW Rev
    
 - -- 
 
  /dev/nvme0n1 CJH0020005EB HUSMR7616BDP301 1 1.92 TB / 1.92 TB 512 B + 8 B 
KNECD105

  root@localhost:/sys/block# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  sda 8:0 0 465.8G 0 disk
  ├─sda1 8:1 0 476M 0 part /boot
  ├─sda2 8:2 0 30.8G 0 part [SWAP]
  └─sda3 8:3 0 434.6G 0 part /
  sdb 8:16 0 931.5G 0 disk
  sr0 11:0 1 1024M 0 rom
  root@localhost:/sys/block# ls -l /sys/block/
  total 0
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop0 -> ../devices/virtual/block/loop0
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop1 -> ../devices/virtual/block/loop1
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop2 -> ../devices/virtual/block/loop2
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop3 -> ../devices/virtual/block/loop3
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop4 -> ../devices/virtual/block/loop4
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop5 -> ../devices/virtual/block/loop5
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop6 -> ../devices/virtual/block/loop6
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop7 -> ../devices/virtual/block/loop7
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 nvme0n1 -> 
../devices/pci:00/:00:01.1/:02:00.0/nvme/nvme0/nvme0n1
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sda -> 
../devices/pci:00/:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sdb -> 
../devices/pci:00/:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdb
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sr0 -> 
../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sr0
  root@localhost:/sys/block# lspci -nn | grep -i Non
  02:00.0 Non-Volatile memory controller [0108]: HGST, Inc. Ultrastar SN200 
Series NVMe SSD [1c58:0023] (rev 02)
  root@localhost:/sys/block# blockdev --getsize64 /dev/nvme0n1
  0
  root@localhost:/sys/block#

  # cat /proc/version_signature
  Ubuntu 4.15.0-23.25-generic 4.15.18

  
  # dmidecode -t 2
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.6 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
  Manufacturer: ASUSTeK Computer INC.
  Product Name: P8Z68-V PRO
  Version: Rev 1.xx
  Serial Number: 11010417300
  Asset Tag: To be filled by O.E.M.
  Features:
  Board is a hosting board
  Board is replaceable
  Location In Chassis: To be filled by O.E.M.
  Chassis Handle: 0x0003
  Type: Motherboard
  Contained Object Handles: 0

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

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

[Kernel-packages] [Bug 1777364] Re: coping files to cifs mounted directory causes general protection fault

2018-06-26 Thread Martin Barlow

Nice catch. Thank you.

This indeed does seem to be a workaround. Forcing version 1.0 avoids the
issue. Its not a proper fix however. Seems to be bug in higher versions.

>From the man doc:

The default since v4.13.5 is for the client and server to negotiate the
highest possible version greater than or equal to 2.1. In kernels prior
to v4.13, the default was 1.0. For kernels between v4.13 and v4.13.5 the
default is 3.0.

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

Title:
  coping files to cifs mounted directory causes general protection fault

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  Copy some large files from local filesystem to CIFS mounted
  filesystem. After some gigabytes, it syslog will show "general
  protection fault" and mounted file system will become unresponsive.

  How often does it occur:

  Every time, after a few minutes or so.

  Affected kernels:

  Bionic 4.15.0-23-generic and forward. I also tried 4.15.18-041518-generic and 
4.16.13-041613-generic from ubuntu archives an got similar GPF.
  4.13.0-43-generic from ubuntu 17.10 not affected.

  More information:

  I have kerberos authenticated, autofs mounted, cifs
  Mounted with:
  type cifs 
(rw,relatime,vers=default,sec=krb5,cache=strict,username=root,uid=1100,forceuid,gid=0,noforcegid,addr=192.168.50.2,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mbarlow2249 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jun 17 23:14:02 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=25088f17-7123-46c8-bda4-362bcd9f986e
  InstallationDate: Installed on 2017-11-26 (203 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=69170b9c-88cc-4e5b-83a8-c6a01d7b738b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (51 days ago)
  WifiSyslog:

  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.2
  dmi.board.name: 06CC14
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn06CC14:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Kernel-packages] [Bug 1778555] Re: My Webcam does not work with Cheese

2018-06-26 Thread Victor Porton

On Tue, 2018-06-26 at 20:40 +, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular
> problem?

The problem first appeared after an upgrade of Debian Linux (mixed
"frankendebian" distro). I do not remember the exact versions of the
software.

In Ubuntu 18.04 the problem appeared immediately after installation. I
haven't tested with other versions of Ubuntu.

> 
> Would it be possible for you to test the latest upstream kernel?
> Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
> latest
> v4.18 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'.

OK, I am going to do this later.

> Once testing of the upstream kernel is complete, please mark this bug
> as
> "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/1778555

Title:
  My Webcam does not work with Cheese

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cheese says that there is no video cam. The same webcam (connected
  through USB 3) does work in Skype.

  From dmesg:

  [1.329876] usb 3-2: New USB device found, idVendor=17a1, idProduct=0128
  [1.329877] usb 3-2: New USB device strings: Mfr=32, Product=38, 
SerialNumber=0
  [1.329878] usb 3-2: Product: USB2.0 JPEG WebCam
  [1.329879] usb 3-2: Manufacturer: TASCORP

  From dmidecode (about my motherboard):

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: Gigabyte Technology Co., Ltd.
  Product Name: H67A-UD3H
  Version:  
  Serial Number:  
  UUID: ----1C6F65886700
  Wake-up Type: Power Switch
  SKU Number:  
  Family:  

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

  $ dpkg -s cheese
  Package: cheese
  Status: install ok installed
  Priority: optional
  Section: gnome
  Installed-Size: 437
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 3.28.0-1ubuntu1
  Depends: libc6 (>= 2.4), libcanberra-gtk3-0 (>= 0.25), libcheese-gtk25 (>= 
3.18.0), libcheese8 (>= 3.18.0), libclutter-1.0-0 (>= 1.16), 
libclutter-gtk-1.0-0 (>= 0.91.8), libgdk-pixbuf2.0-0 (>= 2.25.2), libglib2.0-0 
(>= 2.39.90), libgnome-desktop-3-17 (>= 3.17.92), libgstreamer1.0-0 (>= 1.0.0), 
libgtk-3-0 (>= 3.13.7), cheese-common (>= 3.28.0-1ubuntu1), gnome-video-effects
  Recommends: gvfs, yelp
  Suggests: gnome-video-effects-frei0r
  Description: tool to take pictures and videos from your webcam
   A webcam application that supports image and video capture. Makes
   it easy to take photos and videos of you, your friends, pets or whatever
   you want. Allows you to apply fancy visual effects, fine-control image
   settings and has features such as Multi-Burst mode, Countdown timer
   for photos.
  Homepage: https://wiki.gnome.org/Apps/Cheese
  Original-Maintainer: Debian GNOME Maintainers 

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 19:11:59 2018
  InstallationDate: Installed on 2018-06-23 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: H67A-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd11/02/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67A-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67A-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67A-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  porton 1424 F pulseaudio
   /dev/snd/controlC0:  porton 1424 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-23 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic

Re: [Kernel-packages] [Bug 1776080] Re: After initial install of Bionic, bluetooth stops working QCA6714

[0.00] Linux version 4.18.0-041800rc1-generic (kernel@tangerine)
(gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17
00:34:22 UTC 2018
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960
bytes, using 'compacted' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x00057fff] usable
[0.00] BIOS-e820: [mem 0x00058000-0x00058fff]
reserved
[0.00] BIOS-e820: [mem 0x00059000-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x000f]
reserved
[0.00] BIOS-e820: [mem 0x0010-0x27498fff] usable
[0.00] BIOS-e820: [mem 0x27499000-0x27499fff] ACPI
NVS
[0.00] BIOS-e820: [mem 0x2749a000-0x2749afff]
reserved
[0.00] BIOS-e820: [mem 0x2749b000-0x28827fff] usable
[0.00] BIOS-e820: [mem 0x28828000-0x29127fff]
reserved
[0.00] BIOS-e820: [mem 0x29128000-0x2ed3dfff] usable
[0.00] BIOS-e820: [mem 0x2ed3e000-0x2ef3dfff] type
20
[0.00] BIOS-e820: [mem 0x2ef3e000-0x2f72dfff]
reserved
[0.00] BIOS-e820: [mem 0x2f72e000-0x2ff7dfff] ACPI
NVS
[0.00] BIOS-e820: [mem 0x2ff7e000-0x2fffdfff] ACPI
data
[0.00] BIOS-e820: [mem 0x2fffe000-0x2fffefff] usable
[0.00] BIOS-e820: [mem 0x2000-0x3cff]
reserved
[0.00] BIOS-e820: [mem 0xe000-0xefff]
reserved
[0.00] BIOS-e820: [mem 0xfd00-0xfe7f]
reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff]
reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed00fff]
reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed19fff]
reserved
[0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff]
reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff]
reserved
[0.00] BIOS-e820: [mem 0xffa0-0x]
reserved
[0.00] BIOS-e820: [mem 0x0001-0x0004c1ff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.50 by INSYDE Corp.
[0.00] efi:  ACPI 2.0=0x2fffd014  SMBIOS=0x2efb2000  SMBIOS
3.0=0x2efb  ESRT=0x2efaedd8  MEMATTR=0x2ce55018
[0.00] SMBIOS 3.0.0 present.
[0.00] DMI: LENOVO 80Y7/LNVNB161216, BIOS 5NCN38WW 02/22/2018
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] last_pfn = 0x4c2000 max_arch_pfn = 0x4
[0.00] MTRR default type: write-back
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 008000 mask 7F8000 uncachable
[0.00]   1 base 004000 mask 7FC000 uncachable
[0.00]   2 base 003C00 mask 7FFC00 uncachable
[0.00]   3 base 003A00 mask 7FFE00 uncachable
[0.00]   4 base 003900 mask 7FFF00 uncachable
[0.00]   5 base 003880 mask 7FFF80 uncachable
[0.00]   6 base 20 mask 70 uncachable
[0.00]   7 disabled
[0.00]   8 disabled
[0.00]   9 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC-
WT
[0.00] last_pfn = 0x2 max_arch_pfn = 0x4
[0.00] esrt: Reserving ESRT space from 0x2efaedd8 to
0x2efaee60.
[0.00] Scanning 1 areas for low memory corruption
[0.00] Base memory trampoline at [(ptrval)] 98000 size 24576
[0.00] Using GB pages for direct mapping
[0.00] BRK [0x34c55a000, 0x34c55afff] PGTABLE
[0.00] BRK [0x34c55b000, 0x34c55bfff] PGTABLE
[0.00] BRK

[Kernel-packages] [Bug 1778798] [NEW] zedit doesn't open file in vm mode

2018-06-26 Thread Carl Emberger

Public bug reported:

fis-gtm installed in Ubuntu environment.  zfs-zed package installed to
create and edit M routines.  Using zed command doesn't open file.

--
Description:Ubuntu 16.04.4 LTS
Release:16.04
--
Package: zfs-zed
--
Expected action was the file opened in vm editor.
--
Actual action was the file wasn't opened.

cemberger@cemberger-PC:/$ sudo zed "usr/staff/TESTING"
cemberger@cemberger-PC:/$ ls usr/staff
TESTING
cemberger@cemberger-PC:/$ sudo zed "cprac"
cemberger@cemberger-PC:/$ sudo zed "ccc"
cemberger@cemberger-PC:/$

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

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

Title:
  zedit doesn't open file in vm mode

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  fis-gtm installed in Ubuntu environment.  zfs-zed package installed to
  create and edit M routines.  Using zed command doesn't open file.

  --
  Description:Ubuntu 16.04.4 LTS
  Release:16.04
  --
  Package: zfs-zed
  --
  Expected action was the file opened in vm editor.
  --
  Actual action was the file wasn't opened.

  cemberger@cemberger-PC:/$ sudo zed "usr/staff/TESTING"
  cemberger@cemberger-PC:/$ ls usr/staff
  TESTING
  cemberger@cemberger-PC:/$ sudo zed "cprac"
  cemberger@cemberger-PC:/$ sudo zed "ccc"
  cemberger@cemberger-PC:/$

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

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

[Kernel-packages] [Bug 1771783] Re: iproute2: frr route protocols are not converted to string on xenial

2018-06-26 Thread Khaled El Mously

** Patch added: "proposed-patch-1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+attachment/5156893/+files/proposed-patch-1.debdiff

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

Title:
  iproute2: frr route protocols are not converted to string on xenial

Status in iproute2 package in Ubuntu:
  New

Bug description:
  FRR puts its own proto numbers when inserting a route, example:
  $ ip route
  [snip]
  2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

  iproute2 defines some protocols, but not all:
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

  A patch has been pushed upstream so that external applications can define 
their protocols numbers:
  719e331ff619 ("Add support for rt_protos.d")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

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

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

[Kernel-packages] [Bug 1778772] Re: linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

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

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

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

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

Title:
  linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 4.15.0-1010.10~16.04.1 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: 1776333
  phase: Packaging

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

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

[Kernel-packages] [Bug 1778476] Re: [bionic] high cpu load HP probook iio-sensor-proxy

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 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.18-rc2


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

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

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

Title:
  [bionic] high cpu load HP probook  iio-sensor-proxy

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a many HP ProBook 450 G1 and HP ProBook 650 G3 with fresh
  install of Ubuntu Desktop.

  They all have a load average of 1.0 when idle (no graphical session
  opened).

  vmstat shows idle=0% and waiting=~ 100%

  The process which uses most CPU time is iio-sensor-proxy (about 1%)
  and it's constantly in D state (uninterruptible sleep).

  Manually starting this command shows that the sensor (lis3lv02d on
  both products) is constantly sending garbage informations (see
  attachment).

  With iio-sensor-proxy service stopped, the CPU load is ~ 0%

  As the service is 'static' and can not be disabled, the only workaround is to 
remove the 'iios-sensor-proxy' package.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1371 F pulseaudio
ljanvier   2104 F pulseaudio
   /dev/snd/controlC0:  gdm1371 F pulseaudio
ljanvier   2104 F pulseaudio
  DistroRelease: Ubuntu 18.04
  MachineType: Hewlett-Packard HP ProBook 650 G1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=e375b9cb-3776-455a-bb2e-24f826528047 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  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-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 12/24/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L77 Ver. 01.31
  dmi.board.name: 1993
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3A
  dmi.chassis.asset.tag: 5CG5124FWZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL77Ver.01.31:bd12/24/2014:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.3A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP ProBook 650 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1778222] Re: Ubuntu LIVECD kernel panic

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 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.18-rc2


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

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

Title:
  Ubuntu LIVECD kernel panic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I’ve encounter a problem, not sure if it’s a bug or an intentional
  change to the Linux kernel. I normally don’t mess with the kernel as
  suggested by many on the Internet. But with new releases of Linux Mint
  19.0 or Ubuntu 18.04 out, I decided to try them with the new LiveCD’s.
  With Ubuntu now using Gnome, I decided to give the LiveCD for 18.04 a
  try since I haven’t used Ubuntu since Unity, but then ‘Bamm’ the boot
  of the LiveCD locks up with a kernel panic.

  So I tried the Linux Mint 19.0 LiveCD and had the same failure.
  Looking further at the problem I started installing different kernels
  in my Linux Mint 18.3  system. I found that my system will operate
  with different kernels up to an including 4.11. When I tried kernels
  4.13 or 4.15 both failed to boot with the same kernel panic.
  Everything locks up and I have to do a power off, power on operation
  to recover. So kernel 4.11 is the last one I can use. I found that the
  LiveCD’s both use kernel 4.15 which does not work on my system.

  I have included a picture of the screen when the boot fails. Would
  like to use the latest versions but the kernel problem prevents me
  from doing so.

  This is my uname data: uname -a
  Linux   4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  I have the dmidecode data and the lspci data if needed for kernel
  4.11.(From a good boot)

  With further testing I have found that, Linux Mint 19.0 LiveCD (in
  compatibility mode) or Ubuntu 18.04 LiveCD with the ‘noacpi’ option,
  will both boot into a usable live operating system. I’m afraid though
  that if I installed either to my hard drive that neither would boot. I
  would like to have help resolving this problem so I can continue to
  use Linux. Thanks!

  Ps.there are no newer bios updates for my computer.

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

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

[Kernel-packages] [Bug 1778555] Re: My Webcam does not work with Cheese

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.18 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.18-rc2


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

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

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

Title:
  My Webcam does not work with Cheese

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cheese says that there is no video cam. The same webcam (connected
  through USB 3) does work in Skype.

  From dmesg:

  [1.329876] usb 3-2: New USB device found, idVendor=17a1, idProduct=0128
  [1.329877] usb 3-2: New USB device strings: Mfr=32, Product=38, 
SerialNumber=0
  [1.329878] usb 3-2: Product: USB2.0 JPEG WebCam
  [1.329879] usb 3-2: Manufacturer: TASCORP

  From dmidecode (about my motherboard):

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: Gigabyte Technology Co., Ltd.
  Product Name: H67A-UD3H
  Version:  
  Serial Number:  
  UUID: ----1C6F65886700
  Wake-up Type: Power Switch
  SKU Number:  
  Family:  

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

  $ dpkg -s cheese
  Package: cheese
  Status: install ok installed
  Priority: optional
  Section: gnome
  Installed-Size: 437
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 3.28.0-1ubuntu1
  Depends: libc6 (>= 2.4), libcanberra-gtk3-0 (>= 0.25), libcheese-gtk25 (>= 
3.18.0), libcheese8 (>= 3.18.0), libclutter-1.0-0 (>= 1.16), 
libclutter-gtk-1.0-0 (>= 0.91.8), libgdk-pixbuf2.0-0 (>= 2.25.2), libglib2.0-0 
(>= 2.39.90), libgnome-desktop-3-17 (>= 3.17.92), libgstreamer1.0-0 (>= 1.0.0), 
libgtk-3-0 (>= 3.13.7), cheese-common (>= 3.28.0-1ubuntu1), gnome-video-effects
  Recommends: gvfs, yelp
  Suggests: gnome-video-effects-frei0r
  Description: tool to take pictures and videos from your webcam
   A webcam application that supports image and video capture. Makes
   it easy to take photos and videos of you, your friends, pets or whatever
   you want. Allows you to apply fancy visual effects, fine-control image
   settings and has features such as Multi-Burst mode, Countdown timer
   for photos.
  Homepage: https://wiki.gnome.org/Apps/Cheese
  Original-Maintainer: Debian GNOME Maintainers 


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 19:11:59 2018
  InstallationDate: Installed on 2018-06-23 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: H67A-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd11/02/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67A-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67A-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67A-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  porton 1424 F pulseaudio
   /dev/snd/controlC0:  porton 1424 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-23 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. H67A-UD3H
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color

[Kernel-packages] [Bug 1778475] Re: i40e: restore workaround for removing default MAC filter

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

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

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

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

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

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

Title:
  i40e: restore workaround for removing default MAC filter

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

Bug description:
  Ubuntu Bionic kernel (4.15.0-23) lacks upstream patch for i40e which
  results in forced promiscous mode when adding a vlan.

  
  [   10.847381] i40e :3d:00.0: Error I40E_AQ_RC_EINVAL adding RX filters 
on PF, promiscuous mode forced on

  Steps to reproduce and patch here:

  https://patchwork.ozlabs.org/patch/692499/

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

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

[Kernel-packages] [Bug 1770565] Re: [i915_bpo] Fix flickering issue after panel change

2018-06-26 Thread Timo Aaltonen

file a new bug, test mainline kernels starting from 4.8 and up

http://kernel.ubuntu.com/~kernel-ppa/mainline/

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

Title:
  [i915_bpo] Fix flickering issue after panel change

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  A certain OEM laptop changed the panel type/vendor, and the change regressed 
the driver causing a flickering image. The ODM has tools to measure various 
values of the driver/panel combination, and determined that some voltage levels 
were way too low to pass the spec. The process to bisect the commits took 
weeks, so while it's technically possible that this issue was fixed by a single 
commit (drm/i915: Ignore OpRegion panel type except on select machines), we've 
also kept another 10 commits which upstream thought should help (and did, they 
improved the measured values but not enough).

  So, this backport carries all 11 commits from 4.8/4.9 that the ODM
  verified to pass the tests.

  [Test case]
  Needs to be tested with the ODM tools to be sure.

  [Regression potential]
  There is some, but apart from the necessary refactoring the rest are bugfixes 
to match the HW specs, so this should in fact fix a lot more than just this 
certain machine.

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

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

[Kernel-packages] [Bug 1778274] Re: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 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.18-rc2


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

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

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

Title:
  snd_hda_codec_realtek hdaudioC0D0: Unable to sync register

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi.

  I'm running Ubuntu MATE 16.04 running kernel `4.4.0-128-generic`.

  Since applying updates this morning I'm now unable to shut my machine
  down cleanly. If I shut down or restart, the error
  `snd_hda_codec_realtek hdaudioC0D0: unable to sync register` is output
  3 times and the machine doesn't power down. I have to finish the
  shutdown manually by holding the power button.

  Wasn't sure which debug steps to follow for this error, but this is
  the corresponding extract from `/var/log/kern.log`:

  ```
  Jun 22 21:14:04 leonard kernel: [   37.378508] snd_hda_codec_hdmi 
hdaudioC0D2: Unable to sync register 0x2f0d00. -5
  Jun 22 21:14:04 leonard kernel: [   37.378876] snd_hda_codec_hdmi 
hdaudioC0D2: HDMI: invalid ELD buf size -1
  Jun 22 21:14:04 leonard kernel: [   37.379239] snd_hda_codec_hdmi 
hdaudioC0D2: HDMI: invalid ELD buf size -1
  Jun 22 21:14:04 leonard kernel: [   37.379602] snd_hda_codec_hdmi 
hdaudioC0D2: HDMI: invalid ELD buf size -1
  Jun 22 21:14:04 leonard kernel: [   37.405753] snd_hda_codec_realtek 
hdaudioC0D0: Unable to sync register 0x2b8000. -5
  Jun 22 21:14:04 leonard kernel: [   37.405873] snd_hda_codec_realtek 
hdaudioC0D0: Unable to sync register 0x2b8000. -5
  Jun 22 21:14:04 leonard NetworkManager[904]:   [1529698444.9269] 
ModemManager disappeared from bus
  ```

  I made the report using `ubuntu-bug linux` so hopefully this will
  provide the necessary debug info. If I need to post more info, let me
  know what you need.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-128-generic 4.4.0-128.154
  ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
  Uname: Linux 4.4.0-128-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1660 F pulseaudio
  CurrentDesktop: MATE
  Date: Fri Jun 22 21:19:43 2018
  HibernationDevice: RESUME=UUID=6bc8046c-253e-4b27-bb37-27d8e02c255d
  InstallationDate: Installed on 2017-01-25 (513 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:1112 Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N24_25BU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic.efi.signed 
root=UUID=f03f5e5c-4a97-462b-8e17-63e66a434dc9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-128-generic N/A
   linux-backports-modules-4.4.0-128-generic  N/A
   linux-firmware 1.157.19
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N24_25BU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd12/01/2016:svnNotebook:pnN24_25BU:pvrNotApplicable:rvnNotebook:rnN24_25BU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: N24_25BU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1770565] Re: [i915_bpo] Fix flickering issue after panel change

2018-06-26 Thread Timo Aaltonen

although, your issue can't be the result of this backport, because T440s
has a haswell (gen7.5) gpu, i915_bpo is used only on gen9 gpus

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

Title:
  [i915_bpo] Fix flickering issue after panel change

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  A certain OEM laptop changed the panel type/vendor, and the change regressed 
the driver causing a flickering image. The ODM has tools to measure various 
values of the driver/panel combination, and determined that some voltage levels 
were way too low to pass the spec. The process to bisect the commits took 
weeks, so while it's technically possible that this issue was fixed by a single 
commit (drm/i915: Ignore OpRegion panel type except on select machines), we've 
also kept another 10 commits which upstream thought should help (and did, they 
improved the measured values but not enough).

  So, this backport carries all 11 commits from 4.8/4.9 that the ODM
  verified to pass the tests.

  [Test case]
  Needs to be tested with the ODM tools to be sure.

  [Regression potential]
  There is some, but apart from the necessary refactoring the rest are bugfixes 
to match the HW specs, so this should in fact fix a lot more than just this 
certain machine.

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

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

[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu

I'm investigating this for Bionic.  I'll post an update shortly.

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

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

Title:
  [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common
  deb on Ubuntu

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress

Bug description:
  ---Problem Description---
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods
   
  ---uname output---
  inux-image-4.13.0-36-generic
   
  Machine Type = not relevant 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   File libperf-jvmti.so is missing in linux-tools-common deb provided for 
Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also 
checked if the file is available on launchpad 
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) 
at it's also absent there:

  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm
  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm

  I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
  apparently it's no being packaged in any .deb file?

  Thanks. 
   

   
  Userspace tool common name: perf 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace tool obtained from project website:  na

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

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

[Kernel-packages] [Bug 1776335] Re: linux-gcp: 4.13.0-1020.24 -proposed tracker

2018-06-26 Thread Marcelo Cerri

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

** This bug has been marked a duplicate of bug 1778772
   linux-gcp: 4.15.0-1010.10~16.04.1 -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/1776335

Title:
  linux-gcp: 4.13.0-1020.24 -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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  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: 1776333
  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/1776335/+subscriptions

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

[Kernel-packages] [Bug 1772991] Re: [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable Nvidia driver on bare metal

2018-06-26 Thread Douglas Lehr

I can verify from IBM's standpoint, that we were able to use Volta gpu's
with POWER9.  The Nvidia driver enabled correctly.

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

Title:
  [Ubuntu 18.04.1] POWER9 - Nvidia Volta - Kernel changes to enable
  Nvidia driver on bare metal

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

Bug description:
  == SRU Justification ==
  12 kernel patches have been identified as needed to support Nvidia Volta 
  on bare metal. All are accepted upstream in 4.17. Three of those are 
  already in bionic, leaving a total of 9 remaining commits needed in bionic.
  This pull request is for those other 9 commits.

  == Regression Potential ==
  All of the commits are specific to powerpc.

  == Test Case ==
  A test kernel was built with these patches and tested by IBM.


  == Comment: #0 - Barry B. Arndt  - 2018-05-23 13:40:33 ==
  12 kernel patches have been identified as needed to support Nvidia Volta on 
bare metal.  All are accepted upstream in 4.17.  Three of those are already in 
bionic, leaving a total of 9 remaining commits needed in bionic.  Those 9 
commits are:

  720c84046c26  powerpc/npu-dma.c: Fix crash after __mmu_notifier_register 
failure
  2b74e2a9b39d  powerpc/powernv/npu: Fix deadlock in mmio_invalidate()
  5ee573e8ef03  powerpc/powernv/mce: Don't silently restart the machine
  fb5924fddf9e  powerpc/mm: Flush cache on memory hot(un)plug
  7fd6641de28f  powerpc/powernv/memtrace: Let the arch hotunplug code flush 
cache
  28a5933e8d36  powerpc/powernv/npu: Add lock to prevent race in concurrent 
context init/destroy
  a1409adac748  powerpc/powernv/npu: Prevent overwriting of 
pnv_npu2_init_contex() callback parameters
  d0cf9b561ca9  powerpc/powernv/npu: Do a PID GPU TLB flush when invalidating a 
large address range
  75ecfb49516c  powerpc/mce: Fix a bug where mce loops on memory UE.

  We cherry-picked the commits, and all applied cleanly.  The resultant
  kernel built successfully and loaded.

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

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

[Kernel-packages] [Bug 1778772] Re: linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

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

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

** Description changed:

  This bug is for tracking the 4.15.0-1010.10~16.04.1 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: 1776333
+ kernel-stable-phase-changed:Tuesday, 26. June 2018 19:00 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 4.15.0-1010.10~16.04.1 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: 1776333
- kernel-stable-phase-changed:Tuesday, 26. June 2018 19:00 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta 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:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 4.15.0-1010.10~16.04.1 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: 1776333
  phase: Packaging

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

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

[Kernel-packages] [Bug 1778772] [NEW] linux-gcp: 4.15.0-1010.10~16.04.1 -proposed tracker

2018-06-26 Thread Marcelo Cerri

Public bug reported:

This bug is for tracking the 4.15.0-1010.10~16.04.1 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: 1776333

** 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-gcp (Ubuntu)
 Importance: Undecided
 Status: Invalid

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.06.11-1 xenial

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

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

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

** Tags added: xenial

** Changed in: linux-gcp (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: Undecided =>

[Kernel-packages] [Bug 1778765] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk

2018-06-26 Thread Jun Kong

Unable to run this command

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

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following the suggestion #12 on bug 1758205 to raise a new one

  
  I have updated kernel to 4.15.0-23-generic and still see the problem reported 
in 1758205:

  root@localhost:/sys/block# nvme list
  Node SN Model Namespace Usage Format FW Rev
    
 - -- 
 
  /dev/nvme0n1 CJH0020005EB HUSMR7616BDP301 1 1.92 TB / 1.92 TB 512 B + 8 B 
KNECD105

  root@localhost:/sys/block# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  sda 8:0 0 465.8G 0 disk
  ├─sda1 8:1 0 476M 0 part /boot
  ├─sda2 8:2 0 30.8G 0 part [SWAP]
  └─sda3 8:3 0 434.6G 0 part /
  sdb 8:16 0 931.5G 0 disk
  sr0 11:0 1 1024M 0 rom
  root@localhost:/sys/block# ls -l /sys/block/
  total 0
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop0 -> ../devices/virtual/block/loop0
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop1 -> ../devices/virtual/block/loop1
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop2 -> ../devices/virtual/block/loop2
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop3 -> ../devices/virtual/block/loop3
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop4 -> ../devices/virtual/block/loop4
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop5 -> ../devices/virtual/block/loop5
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop6 -> ../devices/virtual/block/loop6
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop7 -> ../devices/virtual/block/loop7
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 nvme0n1 -> 
../devices/pci:00/:00:01.1/:02:00.0/nvme/nvme0/nvme0n1
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sda -> 
../devices/pci:00/:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sdb -> 
../devices/pci:00/:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdb
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sr0 -> 
../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sr0
  root@localhost:/sys/block# lspci -nn | grep -i Non
  02:00.0 Non-Volatile memory controller [0108]: HGST, Inc. Ultrastar SN200 
Series NVMe SSD [1c58:0023] (rev 02)
  root@localhost:/sys/block# blockdev --getsize64 /dev/nvme0n1
  0
  root@localhost:/sys/block#

  # cat /proc/version_signature
  Ubuntu 4.15.0-23.25-generic 4.15.18

  
  # dmidecode -t 2
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.6 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
  Manufacturer: ASUSTeK Computer INC.
  Product Name: P8Z68-V PRO
  Version: Rev 1.xx
  Serial Number: 11010417300
  Asset Tag: To be filled by O.E.M.
  Features:
  Board is a hosting board
  Board is replaceable
  Location In Chassis: To be filled by O.E.M.
  Chassis Handle: 0x0003
  Type: Motherboard
  Contained Object Handles: 0

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

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

[Kernel-packages] [Bug 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

2018-06-26 Thread Thadeu Lima de Souza Cascardo

There is a package on ppa:cascardo/ppa that should fix the problem. Can
you test it and report back?

Cascardo.

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

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Won't Fix
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  In Progress
Status in crash source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Some analysis won't be possible on new kernels (hwe-edge on xenial, for 
example; or the standard bionic kernel).

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.

  [Regression Potential]
  Analysis of crashed kernels will require that the crash file be moved to a 
system where crash doesn't have the regression. The patch, however, should 
touch only the broken command, and has been tested.

  -

  
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c600  [THREAD_INFO: c03e56cb]
   CPU: 41
     STATE: TASK_RUNNING (SYSRQ)

  crash> ?

  *  files  mach   repeat timer
  alias  foreachmodrunq   tree
  ascii  fuser  mount  search union
  bt gdbnetsetvm
  btop

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

2018-06-26 Thread Thadeu Lima de Souza Cascardo

There is a package on ppa:cascardo/ppa that should fix the problem. Can
you test it and report back?

Cascardo.

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  New
Status in crash source package in Artful:
  In Progress
Status in crash source package in Bionic:
  Fix Released

Bug description:
  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)
   
  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8001-22C 

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows 

  Once you generate the kdump 
  use crash to analyze the vmcore and we get this error 

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)   
  WARNING: cannot access vmalloc'd module memory

  
  crash: invalid structure member offset: thread_info_task
 FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

100833e0: (undetermined)
1017d220: OFFSET_verify+80
1011552c: task_init+5084
1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

commit c8178eca9c74f81a7f803a58d339635cc152e8d9
Author: Dave Anderson 
Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

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

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

[Kernel-packages] [Bug 1777364] Re: coping files to cifs mounted directory causes general protection fault

2018-06-26 Thread Frits Jalvingh

Could be related to something in here:

https://bugs.archlinux.org/task/57474

Adding vers=1.0 in the mount line seems to fix the issue.

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

Title:
  coping files to cifs mounted directory causes general protection fault

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  Copy some large files from local filesystem to CIFS mounted
  filesystem. After some gigabytes, it syslog will show "general
  protection fault" and mounted file system will become unresponsive.

  How often does it occur:

  Every time, after a few minutes or so.

  Affected kernels:

  Bionic 4.15.0-23-generic and forward. I also tried 4.15.18-041518-generic and 
4.16.13-041613-generic from ubuntu archives an got similar GPF.
  4.13.0-43-generic from ubuntu 17.10 not affected.

  More information:

  I have kerberos authenticated, autofs mounted, cifs
  Mounted with:
  type cifs 
(rw,relatime,vers=default,sec=krb5,cache=strict,username=root,uid=1100,forceuid,gid=0,noforcegid,addr=192.168.50.2,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mbarlow2249 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jun 17 23:14:02 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=25088f17-7123-46c8-bda4-362bcd9f986e
  InstallationDate: Installed on 2017-11-26 (203 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=69170b9c-88cc-4e5b-83a8-c6a01d7b738b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (51 days ago)
  WifiSyslog:

  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.2
  dmi.board.name: 06CC14
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn06CC14:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

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

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

apport-collect 1778765

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

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

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

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

** Tags added: bionic

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

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Following the suggestion #12 on bug 1758205 to raise a new one

  
  I have updated kernel to 4.15.0-23-generic and still see the problem reported 
in 1758205:

  root@localhost:/sys/block# nvme list
  Node SN Model Namespace Usage Format FW Rev
    
 - -- 
 
  /dev/nvme0n1 CJH0020005EB HUSMR7616BDP301 1 1.92 TB / 1.92 TB 512 B + 8 B 
KNECD105

  root@localhost:/sys/block# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  sda 8:0 0 465.8G 0 disk
  ├─sda1 8:1 0 476M 0 part /boot
  ├─sda2 8:2 0 30.8G 0 part [SWAP]
  └─sda3 8:3 0 434.6G 0 part /
  sdb 8:16 0 931.5G 0 disk
  sr0 11:0 1 1024M 0 rom
  root@localhost:/sys/block# ls -l /sys/block/
  total 0
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop0 -> ../devices/virtual/block/loop0
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop1 -> ../devices/virtual/block/loop1
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop2 -> ../devices/virtual/block/loop2
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop3 -> ../devices/virtual/block/loop3
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop4 -> ../devices/virtual/block/loop4
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop5 -> ../devices/virtual/block/loop5
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop6 -> ../devices/virtual/block/loop6
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop7 -> ../devices/virtual/block/loop7
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 nvme0n1 -> 
../devices/pci:00/:00:01.1/:02:00.0/nvme/nvme0/nvme0n1
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sda -> 
../devices/pci:00/:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sdb -> 
../devices/pci:00/:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdb
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sr0 -> 
../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sr0
  root@localhost:/sys/block# lspci -nn | grep -i Non
  02:00.0 Non-Volatile memory controller [0108]: HGST, Inc. Ultrastar SN200 
Series NVMe SSD [1c58:0023] (rev 02)
  root@localhost:/sys/block# blockdev --getsize64 /dev/nvme0n1
  0
  root@localhost:/sys/block#

  # cat /proc/version_signature
  Ubuntu 4.15.0-23.25-generic 4.15.18

  
  # dmidecode -t 2
  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 2.6 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
  Manufacturer: ASUSTeK Computer INC.
  Product Name: P8Z68-V PRO
  Version: Rev 1.xx
  Serial Number: 11010417300
  Asset Tag: To be filled by O.E.M.
  Features:
  Board is a hosting board
  Board is replaceable
  Location In Chassis: To be filled by O.E.M.
  Chassis Handle: 0x0003
  Type: Motherboard
  Contained Object Handles: 0

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

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

[Kernel-packages] [Bug 1778765] [NEW] Ubuntu 18.04 NVMe disks are not displayed on lsblk

2018-06-26 Thread Jun Kong

Public bug reported:

Following the suggestion #12 on bug 1758205 to raise a new one


I have updated kernel to 4.15.0-23-generic and still see the problem reported 
in 1758205:

root@localhost:/sys/block# nvme list
Node SN Model Namespace Usage Format FW Rev
   
- --  
/dev/nvme0n1 CJH0020005EB HUSMR7616BDP301 1 1.92 TB / 1.92 TB 512 B + 8 B 
KNECD105

root@localhost:/sys/block# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 476M 0 part /boot
├─sda2 8:2 0 30.8G 0 part [SWAP]
└─sda3 8:3 0 434.6G 0 part /
sdb 8:16 0 931.5G 0 disk
sr0 11:0 1 1024M 0 rom
root@localhost:/sys/block# ls -l /sys/block/
total 0
lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop4 -> ../devices/virtual/block/loop4
lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop5 -> ../devices/virtual/block/loop5
lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop6 -> ../devices/virtual/block/loop6
lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop7 -> ../devices/virtual/block/loop7
lrwxrwxrwx 1 root root 0 Jun 25 15:05 nvme0n1 -> 
../devices/pci:00/:00:01.1/:02:00.0/nvme/nvme0/nvme0n1
lrwxrwxrwx 1 root root 0 Jun 25 15:05 sda -> 
../devices/pci:00/:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda
lrwxrwxrwx 1 root root 0 Jun 25 15:05 sdb -> 
../devices/pci:00/:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdb
lrwxrwxrwx 1 root root 0 Jun 25 15:05 sr0 -> 
../devices/pci:00/:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sr0
root@localhost:/sys/block# lspci -nn | grep -i Non
02:00.0 Non-Volatile memory controller [0108]: HGST, Inc. Ultrastar SN200 
Series NVMe SSD [1c58:0023] (rev 02)
root@localhost:/sys/block# blockdev --getsize64 /dev/nvme0n1
0
root@localhost:/sys/block#

# cat /proc/version_signature
Ubuntu 4.15.0-23.25-generic 4.15.18


# dmidecode -t 2
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.6 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: P8Z68-V PRO
Version: Rev 1.xx
Serial Number: 11010417300
Asset Tag: To be filled by O.E.M.
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: To be filled by O.E.M.
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

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

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

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk

Status in linux package in Ubuntu:
  New

Bug description:
  Following the suggestion #12 on bug 1758205 to raise a new one

  
  I have updated kernel to 4.15.0-23-generic and still see the problem reported 
in 1758205:

  root@localhost:/sys/block# nvme list
  Node SN Model Namespace Usage Format FW Rev
    
 - -- 
 
  /dev/nvme0n1 CJH0020005EB HUSMR7616BDP301 1 1.92 TB / 1.92 TB 512 B + 8 B 
KNECD105

  root@localhost:/sys/block# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  sda 8:0 0 465.8G 0 disk
  ├─sda1 8:1 0 476M 0 part /boot
  ├─sda2 8:2 0 30.8G 0 part [SWAP]
  └─sda3 8:3 0 434.6G 0 part /
  sdb 8:16 0 931.5G 0 disk
  sr0 11:0 1 1024M 0 rom
  root@localhost:/sys/block# ls -l /sys/block/
  total 0
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop0 -> ../devices/virtual/block/loop0
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop1 -> ../devices/virtual/block/loop1
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop2 -> ../devices/virtual/block/loop2
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop3 -> ../devices/virtual/block/loop3
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop4 -> ../devices/virtual/block/loop4
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop5 -> ../devices/virtual/block/loop5
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop6 -> ../devices/virtual/block/loop6
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 loop7 -> ../devices/virtual/block/loop7
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 nvme0n1 -> 
../devices/pci:00/:00:01.1/:02:00.0/nvme/nvme0/nvme0n1
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sda -> 
../devices/pci:00/:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sdb -> 
../devices/pci:00/:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdb
  lrwxrwxrwx 1 root root 0 Jun 25 15:05 sr0 ->

[Kernel-packages] [Bug 1152484] Re: [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu

2018-06-26 Thread Sandi Vujaković

I've used UKUU to get kernel version 4.17.3, but this issue remains on
my HP Pavilion 15-aw003nm
(http://www8.hp.com/h20195/v2/GetPDF.aspx/c05342156.pdf ) on kernel
version 4.15.0-23 from the repository as well as on the latest stable
kernel.

The exact error message copied from dmesg is as follows:

[  +0,07] [Firmware Bug]: cpu 0, invalid threshold interrupt offset
1 for bank 4, block 0 (MSR0413=0xd100)

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

Title:
  [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector
  0x400, but the register is already in use for vector 0xf9 on another
  cpu

Status in HWE Next:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  suspend_30_cycles.log is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
  ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: Generic [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1577 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1577 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'HDMI'/'HDA ATI HDMI at 0xf0344000 irq 46'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100300'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xf034 irq 16'
 Mixer name : 'IDT 92HD99BXX'
 Components : 'HDA:111d76e5,103c1937,00100303'
 Controls  : 18
 Simple ctrls  : 10
  Date: Fri Mar  8 02:43:22 2013
  HibernationDevice: RESUME=UUID=b745d689-656e-45a5-b635-c37b6ac2888f
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MachineType: Hewlett-Packard HP Pavilion Sleekbook 14 PC
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic 
root=UUID=7b5bc75d-d89d-454f-84f6-18291d5a1735 ro quiet splash initcall_debug 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-25-generic N/A
   linux-backports-modules-3.5.0-25-generic  N/A
   linux-firmware1.79.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/01/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1937
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 87.0B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd11/01/2012:svnHewlett-Packard:pnHPPavilionSleekbook14PC:pvr08921100590320100:rvnHewlett-Packard:rn1937:rvr87.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Sleekbook 14 PC
  dmi.product.version: 08921100590320100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1778759] [NEW] Bionic update: upstream stable patchset 2018-06-26

2018-06-26 Thread Kamal Mostafa

Public bug reported:

SRU Justification

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

   upstream stable patchset 2018-06-26 (ported from v4.14.40 and v4.16.8)
   from git://git.kernel.org/

clocksource: Consistent de-rate when marking unstable
clocksource: Initialize cs->wd_list
clocksource: Allow clocksource_mark_unstable() on unregistered clocksources
KVM: x86: remove APIC Timer periodic/oneshot spikes
platform/x86: Kconfig: Fix dell-laptop dependency chain.
xhci: Fix use-after-free in xhci_free_virt_device
drm/vc4: Make sure vc4_bo_{inc,dec}_usecnt() calls are balanced
btrfs: Take trans lock before access running trans in check_delayed_ref
infiniband: mlx5: fix build errors when INFINIBAND_USER_ACCESS=m
Input: atmel_mxt_ts - add touchpad button mapping for Samsung Chromebook Pro
arm64: Add work around for Arm Cortex-A55 Erratum 1024718
UBUNTU: [Config] CONFIG_ARM64_ERRATUM_1024718=y
tracing: Fix bad use of igrab in trace_uprobe.c
irqchip/qcom: Fix check for spurious interrupts
platform/x86: asus-wireless: Fix NULL pointer dereference
usb: musb: trace: fix NULL pointer dereference in musb_g_tx()
usb: musb: host: fix potential NULL pointer dereference
USB: serial: option: adding support for ublox R410M
USB: serial: option: reimplement interface masking
USB: Accept bulk endpoints with 1024-byte maxpacket
usb: dwc3: gadget: Fix list_del corruption in dwc3_ep_dequeue
USB: serial: visor: handle potential invalid device configuration
errseq: Always report a writeback error once
test_firmware: fix setting old custom fw path back on exit, second try
drm/bridge: vga-dac: Fix edid memory leak
drm/vmwgfx: Fix a buffer object leak
iw_cxgb4: Atomically flush per QP HW CQEs
IB/hfi1: Fix NULL pointer dereference when invalid num_vls is used
IB/hfi1: Fix loss of BECN with AHG
IB/hfi1: Fix handling of FECN marked multicast packet
IB/mlx5: Use unlimited rate when static rate is not supported
NET: usb: qmi_wwan: add support for ublox R410M PID 0x90b2
RDMA/mlx5: Protect from shift operand overflow
RDMA/mlx5: Fix multiple NULL-ptr deref errors in rereg_mr flow
RDMA/ucma: Allow resolving address w/o specifying source address
RDMA/cxgb4: release hw resources on device removal
xfs: prevent creating negative-sized file via INSERT_RANGE
rtlwifi: cleanup 8723be ant_sel definition
rtlwifi: btcoex: Add power_on_setting routine
Input: atmel_mxt_ts - add touchpad button mapping for Samsung Chromebook Pro
Input: leds - fix out of bound access
scsi: target: Fix fortify_panic kernel exception
tracepoint: Do not warn on ENOMEM
ALSA: aloop: Add missing cable lock to ctl API callbacks
ALSA: aloop: Mark paused device as inactive
ALSA: dice: fix kernel NULL pointer dereference due to invalid calculation for 
array index
ALSA: seq: Fix races at MIDI encoding in snd_virmidi_output_trigger()
ALSA: pcm: Check PCM state at xfern compat ioctl
ALSA: hda - Fix incorrect usage of IS_REACHABLE()
USB: serial: option: Add support for Quectel EP06
ACPI / button: make module loadable when booted in non-ACPI mode
percpu: include linux/sched.h for cond_resched()

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2018-06-26 (ported from v4.14.40 and v4.16.8)
+    from git://git.kernel.org/
  
-upstream stable patchset 2018-06-26
-from git://git.kernel.org/
+

[Kernel-packages] [Bug 1766055] Re: Vcs-Git header on bionic linux source package points to zesty git tree

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093554.html

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

Title:
  Vcs-Git header on bionic linux source package points to zesty git tree

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

Bug description:
  mark@studiopc:~$ cat /etc/*-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  <...>
  mark@studiopc:~$ sudo apt source linux
  Reading package lists... Done
  NOTICE: 'linux' packaging is maintained in the 'Git' version control system 
at:
  git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/zesty
  Please use:
  git clone 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/zesty
  to retrieve the latest (possibly unreleased) updates to the package.

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

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

[Kernel-packages] [Bug 1778511] Re: PCI network card (r8169) UNCLAIMED at boot

Is there any entry in /etc/modprobe.conf or /etc/modprobe.d that is
r8168/r8169?

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

Title:
  PCI network card (r8169) UNCLAIMED at boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  2 network interfaces installed - Intel and Realtek. Intel (onboard) no 
problem. Realtek (PCI Express) not loaded at boot.
  lshw -C network (after boot) shows
   *-network UNCLAIMED
 description: Ethernet controller
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:05:00.0
 version: 06
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd cap_list
 configuration: latency=0
 resources: ioport:d000(size=256) memory:f7c0-f7c00fff 
memory:f000-f0003fff

  sudo modprobe -r r8169 & sudo  modprobe r8169 loads driver

  lshw -C network then gives
   *-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:05:00.0
 logical name: enp5s0
 version: 06
 serial: 98:de:d0:06:2e:68
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl_nic/rtl8168e-2.fw 
ip=192.168.2.6 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
 resources: irq:32 ioport:d000(size=256) memory:f7c0-f7c00fff 
memory:f000-f0003fff

  INTEL
  *-network 
 description: Ethernet interface
 product: Ethernet Connection I217-V
 vendor: Intel Corporation
 physical id: 19
 bus info: pci@:00:19.0
 logical name: eno1
 version: 04
 serial: 74:d0:2b:9e:f5:fb
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 32 bits
 clock: 33MHz
 capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 
10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=3.2.6-k duplex=full firmware=0.13-4 ip=192.168.1.64 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:27 memory:f7f0-f7f1 memory:f7f3d000-f7f3dfff 
ioport:f080(size=32)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard4495 F pulseaudio
   /dev/snd/controlC1:  richard4495 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 13:15:42 2018
  HibernationDevice: RESUME=UUID=03521e66-171a-4e66-bc2e-650c385fbefc
  InstallationDate: Installed on 2013-10-18 (1710 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=496abb27-03bd-48e8-81b3-bdb5f4aea244 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-15 (41 days ago)
  dmi.bios.date: 05/17/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1007
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1007:bd05/17/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1770565] Re: [i915_bpo] Fix flickering issue after panel change

2018-06-26 Thread Killercow

Since installing this kernel, I see instant screen garbage or blanking
(everything but the cursor), when attaching / removing a second / third
screen on My Lenovo Thinkpad T440s.

Older kernels do not suffer these problems. A restart of lightdm makes
the problems go away and makes a second screen be detected as expected.

What logs would be usefull? Xorg.0.log doesn't realy have anything out
of the ordinary, nor does Dmesg.

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

Title:
  [i915_bpo] Fix flickering issue after panel change

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  A certain OEM laptop changed the panel type/vendor, and the change regressed 
the driver causing a flickering image. The ODM has tools to measure various 
values of the driver/panel combination, and determined that some voltage levels 
were way too low to pass the spec. The process to bisect the commits took 
weeks, so while it's technically possible that this issue was fixed by a single 
commit (drm/i915: Ignore OpRegion panel type except on select machines), we've 
also kept another 10 commits which upstream thought should help (and did, they 
improved the measured values but not enough).

  So, this backport carries all 11 commits from 4.8/4.9 that the ODM
  verified to pass the tests.

  [Test case]
  Needs to be tested with the ODM tools to be sure.

  [Regression potential]
  There is some, but apart from the necessary refactoring the rest are bugfixes 
to match the HW specs, so this should in fact fix a lot more than just this 
certain machine.

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

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

[Kernel-packages] [Bug 1766055] Re: Vcs-Git header on bionic linux source package points to zesty git tree

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

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

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

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

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

Title:
  Vcs-Git header on bionic linux source package points to zesty git tree

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

Bug description:
  mark@studiopc:~$ cat /etc/*-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  <...>
  mark@studiopc:~$ sudo apt source linux
  Reading package lists... Done
  NOTICE: 'linux' packaging is maintained in the 'Git' version control system 
at:
  git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/zesty
  Please use:
  git clone 
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/zesty
  to retrieve the latest (possibly unreleased) updates to the package.

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

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

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

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

apport-collect 1742488

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

Title:
  KVMGT gvt-g live migration

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

Bug description:
  KVMGT gvt-g Live Migration is a valuable feature for a variety of use
  cases like load balancing, hardware failover, energy saving and
  geographic migration. To enable VGPU live migration, one new region is
  designed for vfio_mdev device status save and restore during the
  migration. And one new ioctl is added to help do the mdev device dirty
  page synchronization. Correspondingly, GVT implements a function to
  save/retore the device context in the new region.

  Applied platform: BDW/SKL/KBL

  Business value: Improve efficiency and reduce cost in VM maintenance
  by enabling live migration for Intel GPU accelerated VM.

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

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

[Kernel-packages] [Bug 1742488] Re: KVMGT gvt-g live migration

2018-06-26 Thread  Christian Ehrhardt 

Hi,
the own website [1] still calls it "should be considered a work in progress. As 
such it is not a complete product nor should it be considered one. Extra care 
should be taken when testing and configuring a system to use the KVMGT project".

That said I'm not sure what is expected here. I assume you will continue
to work on upstreaming this into the Kernel / Qemu and we will pick it
up by that - right?

[1]: https://01.org/igvt-g/blogs/wangbo85/2018/2018-q1-release-kvmgt-
intel-gvt-g-kvm

** Package changed: kvm (Ubuntu) => qemu (Ubuntu)

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

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

Title:
  KVMGT gvt-g live migration

Status in linux package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New

Bug description:
  KVMGT gvt-g Live Migration is a valuable feature for a variety of use
  cases like load balancing, hardware failover, energy saving and
  geographic migration. To enable VGPU live migration, one new region is
  designed for vfio_mdev device status save and restore during the
  migration. And one new ioctl is added to help do the mdev device dirty
  page synchronization. Correspondingly, GVT implements a function to
  save/retore the device context in the new region.

  Applied platform: BDW/SKL/KBL

  Business value: Improve efficiency and reduce cost in VM maintenance
  by enabling live migration for Intel GPU accelerated VM.

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

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

[Kernel-packages] [Bug 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress

Moving back to Confirmed state - since all the available logs are
already uploaded.

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

Title:
  Ubuntu 18.04 guest hangs during diskio stress

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

Bug description:
  Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
  Ubuntu 18.04 (latest updates) guest.

  Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
  Run diskio stress on all the 3 data disks for overnight.
  Guest goes unresponsive (even ping fails) in between.
  Only way to recover is to reset the guest.

  Logs do not indicate much on this error.
  Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of 
different hits.

  We have tried mainline kernel v4.18-rc-2 and have hit the issue there
  as well.

  Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
  have not seen any crash/hang here.

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

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

[Kernel-packages] [Bug 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress

* Also hit with 16.04.4 HWE kernel 4.13.0-45-generic.

* Not seen with LTS kernel 4.4 of Ubuntu 16.04

** Also affects: dellserver
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu 18.04 guest hangs during diskio stress

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

Bug description:
  Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
  Ubuntu 18.04 (latest updates) guest.

  Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
  Run diskio stress on all the 3 data disks for overnight.
  Guest goes unresponsive (even ping fails) in between.
  Only way to recover is to reset the guest.

  Logs do not indicate much on this error.
  Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of 
different hits.

  We have tried mainline kernel v4.18-rc-2 and have hit the issue there
  as well.

  Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
  have not seen any crash/hang here.

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

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

[Kernel-packages] [Bug 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress

** Attachment added: "screenshot-2"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778717/+attachment/5156771/+files/image-2018-06-22-14-48-57-801.png

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

Title:
Ubuntu 18.04 guest hangs during diskio stress

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

Bug description:
Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
Ubuntu 18.04 (latest updates) guest.

Guest has 3 data disks apart from the boot disk. All these disks are exposed
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
Run diskio stress on all the 3 data disks for overnight.
Guest goes unresponsive (even ping fails) in between.
Only way to recover is to reset the guest.

Logs do not indicate much on this error.
Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of
different hits.

We have tried mainline kernel v4.18-rc-2 and have hit the issue there
as well.

Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
have not seen any crash/hang here.

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

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

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

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

apport-collect 1778717

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

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

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

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

** Tags added: bionic

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

Title:
  Ubuntu 18.04 guest hangs during diskio stress

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

Bug description:
  Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
  Ubuntu 18.04 (latest updates) guest.

  Guest has 3 data disks apart from the boot disk. All these disks are exposed 
through "ParaVirtual SCSI controller" from the host ESXi 6.7.
  Run diskio stress on all the 3 data disks for overnight.
  Guest goes unresponsive (even ping fails) in between.
  Only way to recover is to reset the guest.

  Logs do not indicate much on this error.
  Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of 
different hits.

  We have tried mainline kernel v4.18-rc-2 and have hit the issue there
  as well.

  Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
  have not seen any crash/hang here.

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

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

[Kernel-packages] [Bug 1778717] Re: Ubuntu 18.04 guest hangs during diskio stress

** Attachment added: "screenshot-1"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778717/+attachment/5156770/+files/image-2018-06-25-10-13-05-871.png

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

Title:
Ubuntu 18.04 guest hangs during diskio stress

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

Bug description:
Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
Ubuntu 18.04 (latest updates) guest.

Logs do not indicate much on this error.
Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of
different hits.

We have tried mainline kernel v4.18-rc-2 and have hit the issue there
as well.

Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
have not seen any crash/hang here.

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

[Kernel-packages] [Bug 1778717] [NEW] Ubuntu 18.04 guest hangs during diskio stress

Public bug reported:

Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu
18.04 (latest updates) guest.

Logs do not indicate much on this error.
Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of different
hits.

We have tried mainline kernel v4.18-rc-2 and have hit the issue there as
well.

Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
have not seen any crash/hang here.

** Affects: dellserver
Importance: Undecided
Status: New

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

** Tags: bionic

** Attachment added: "log files inside /var/log/"

https://bugs.launchpad.net/bugs/1778717/+attachment/5156769/+files/var-log-ubuntu1804-vm.zip

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

Title:
Ubuntu 18.04 guest hangs during diskio stress

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

Bug description:
Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and
Ubuntu 18.04 (latest updates) guest.

Logs do not indicate much on this error.
Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of
different hits.

We have tried mainline kernel v4.18-rc-2 and have hit the issue there
as well.

Changing the SCSI controller to "LSI Logic SAS adapter" helps and we
have not seen any crash/hang here.

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

[Kernel-packages] [Bug 1776284] Re: @buy hydrocodone online +209-813-2040

2018-06-26 Thread William Grant

** Package changed: linux-azure (Ubuntu) => null-and-void

** Information type changed from Public to Private

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

Title:
  @buy hydrocodone online +209-813-2040

Status in NULL Project:
  Invalid

Bug description:
  
https://comunidad.tuenti.es/welcome-comunidad-14/hydrocodone-buy-online+(209)(813)(2040)buy-hydrocodone-online-5843
  
https://www.chegg.com/homework-help/questions-and-answers/buy-hydrocodone-online+1-209~813~2040-hydrocodone-prescription-buy-hydrocodone-online-+1-209~813~2040-
  
https://foundation.zurb.com/forum/posts/57309-hydrocodone-online-1888-562-8956-buy-hydrocodone-online
  https://snazzymaps.com/style/157850/call+2098132040-buy-hydrocodone-online
  https://snazzymaps.com/style/160588/hy/+2098132040-buy-hydrocodone-online
  
https://comunidad.tuenti.es/welcome-comunidad-14/q-buy-hydrocodone-online-+2098132040-buy-oxycodone-online-6479
  
https://www.themuse.com/jobs/l-San-Francisco%2C-CA+q-Hy_+1(209-803~2040)-buy-hydrocodone-online+level-Entry-Level-jobs
  
https://www.chegg.com/homework-help/questions-and-answers/buy-hydrocodone-online-1~888~562~8956-hydrocodone-sale-cheap-buy-hydrocodone-online-
  
https://www.chegg.com/homework-help/questions-and-answers/buy-oxycodone-1-209-803-2040-buy-oxycodone-online-visit-buy-hydrocodone-http-hydrocodoneor-q27879302

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1776284/+subscriptions

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

[Kernel-packages] [Bug 1776305] Re: Buy hydrocodone online +209-813-2040 (No Rx)

2018-06-26 Thread William Grant

** Package changed: linux-azure (Ubuntu) => null-and-void

** Information type changed from Public to Private

** Changed in: null-and-void
   Status: New => Invalid

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

Title:
  Buy hydrocodone online +209-813-2040 (No Rx)

Status in NULL Project:
  Invalid

Bug description:
  
https://www.paincaresolution.com/hydrocodone-buy-online+(209)(813)(2040)-buy-hydrocodone-online-5843
  
https://www.chegg.com/homework-help/questions-and-answers/buy-hydrocodone-online+1-209~813~2040-hydrocodone-prescription-buy-hydrocodone-online-+1-209~813~2040-
  
https://foundation.zurb.com/forum/posts/57309-hydrocodone-online-1888-562-8956-buy-hydrocodone-online
  https://snazzymaps.com/style/157850/call+2098132040-buy-hydrocodone-online
  https://snazzymaps.com/style/160588/hy/+2098132040-buy-hydrocodone-online
  
https://comunidad.tuenti.es/welcome-comunidad-14/q-buy-hydrocodone-online-+2098132040-buy-oxycodone-online-6479
  
https://www.themuse.com/jobs/l-San-Francisco%2C-CA+q-Hy_+1(209-803~2040)-buy-hydrocodone-online+level-Entry-Level-jobs
  
https://www.chegg.com/homework-help/questions-and-answers/buy-hydrocodone-online-1~888~562~8956-hydrocodone-sale-cheap-buy-hydrocodone-online-
  
https://www.chegg.com/homework-help/questions-and-answers/buy-oxycodone-1-209-803-2040-buy-oxycodone-online-visit-buy-hydrocodone-http-hydrocodoneor-q27879302

To manage notifications about this bug go to:
https://bugs.launchpad.net/null-and-void/+bug/1776305/+subscriptions

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

[Kernel-packages] [Bug 1778705] Re: skey in ubuntu-kvm-unit-test failed on Xenial zVM

2018-06-26 Thread Dimitri John Ledkov 

kvm on z/vm is out of scope for Ubuntu on s390x.

one may still want to investigate none-the-less in case something
generic is uncovered.

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

Title:
  skey in ubuntu-kvm-unit-test failed on Xenial zVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1
  FAIL skey (2 tests)

  This is the only failure in this test suite on Xenial zVM, need to run
  it manually to see what's going on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-130-generic 4.4.0-130.156
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [ 3288.479241] audit_printk_skb: 153 callbacks suppressed
   [ 3288.479246] audit: type=1400 audit(1530011067.825:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine" pid=6480 comm="apparmor_parser"
   [ 3288.510095] audit: type=1400 audit(1530011067.865:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=6480 
comm="apparmor_parser"
  Date: Tue Jun 26 07:05:34 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-130-generic N/A
   linux-backports-modules-4.4.0-130-generic  N/A
   linux-firmware 1.157.19
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

apport-collect 1778705

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

Title:
  skey in ubuntu-kvm-unit-test failed on Xenial zVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1
  FAIL skey (2 tests)

  This is the only failure in this test suite on Xenial zVM, need to run
  it manually to see what's going on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-130-generic 4.4.0-130.156
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [ 3288.479241] audit_printk_skb: 153 callbacks suppressed
   [ 3288.479246] audit: type=1400 audit(1530011067.825:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine" pid=6480 comm="apparmor_parser"
   [ 3288.510095] audit: type=1400 audit(1530011067.865:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=6480 
comm="apparmor_parser"
  Date: Tue Jun 26 07:05:34 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-130-generic N/A
   linux-backports-modules-4.4.0-130-generic  N/A
   linux-firmware 1.157.19
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04

2018-06-26 Thread tuttobenethx

Using a Logitech M310 from a KM520 bundle kit like Steven Karas (steven-
karas) and having exactly the same issue. His comment (comment #91)
makes my middle button magically start working as well.

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

Title:
  Middle mouse (wheel-click) button stopped working after upgrade to
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 16.04 clicking the middle mouse button (scroll
  wheel) on my Logitech M185 stopped working.

  xev does not even show the event for clicking the wheel, while it
  shows other button clicks and scroll wheel up/down events.

  xinput list shows the USB receiver 2 times:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=9[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ HID 046a:0023   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=16   [slave  pointer 
 (2)]
  ⎜   ↳ TPPS/2 IBM TrackPoint   id=17   [slave  pointer 
 (2)]

  Listing the capabilities looks like this:

  $ xinput list 9
  Logitech USB Receiver id=9[slave  pointer  (2)]
   Reporting 7 classes:
    Class originated from: 9. Type: XIButtonClass
    Buttons supported: 24
    Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" 
"Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" 
"Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button 
Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" 
"Button Unknown" "Button Unknown" "Button Unknown"
    Button state:
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 3:
  Label: Rel Vert Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 3
  type: 1 (vertical)
  increment: -1.00
  flags: 0x2 ( preferred )

  $ xinput list 10
  Logitech USB Receiver id=10   [slave  pointer  (2)]
   Reporting 6 classes:
    Class originated from: 10. Type: XIButtonClass
    Buttons supported: 7
    Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"
    Button state:
    Class originated from: 10. Type: XIKeyClass
    Keycodes supported: 248
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0

  Does anyone have an idea how I can attempt to further debug that issue? Or 
maybe even a solution? Should I consider this issue a bug? Can I provide more 
info?
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  toby  11625 F pulseaudio
   /dev/snd/controlC0:  toby  11625 F pulseaudio
   /dev/snd/pcmC1D0p:   toby  11625 F...m pulseaudio
   /dev/snd/controlC1:  toby  11625 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5e3a6d2e-05f8-4d01-b80c-a9f200e6
  InstallationDate: Installed on

[Kernel-packages] [Bug 1690085]

2018-06-26 Thread kernelorg

I'm praying intensely that the new AMD Epyc 3000 Embedded series (low
power e3000) don't have the same issues.   Hoping to buy one in the next
few months when they finally put the damn things on some ITX boards.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload:

[Kernel-packages] [Bug 1777863] Re: [drm:intel_wait_ddi_buf_idle [i915]] ERROR Timeout waiting for DDI BUF C idle bit

2018-06-26 Thread Haug Bürger

That doesn't seem to happen with  4.15.0-22-generic.

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

Title:
  [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI
  BUF C idle bit

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System reboot. This could be related to putting the NB back into the docking 
station.
  Search for [ cut here ] to find the final error 
message before reboot.

  Linux mymachine4 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16
  UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Using vrefresh ranges from config file
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 
+hsync +vsync (67.5 kHz eP)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync 
(31.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync 
(31.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 
+hsync +vsync (80.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync 
+vsync (60.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync 
-vsync (48.4 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync 
(46.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync 
+vsync (67.5 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 
+hsync +vsync (64.0 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1600x900"x60.0  119.00  1600 1696 1864 2128  900 901 904 932 -hsync 
+vsync (55.9 kHz e)
  Jun 20 12:05:00 mymachine /usr/lib/gdm3/gdm-x-session[4443]: (II) modeset(0): 
Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080 1081 1084 1118 
-hsync +vsync (67.1 kHz e)
  Jun 20 12:05:18 mymachine kernel: [drm:intel_wait_ddi_buf_idle [i915]] 
*ERROR* Timeout waiting for DDI BUF C idle bit
  Jun 20 12:05:18 mymachine kernel: [ cut here ]
  Jun 20 12:05:18 mymachine kernel: vblank wait timed out on crtc 2
  Jun 20 12:05:18 mymachine kernel: WARNING: CPU: 2 PID: 4445 at 
/build/linux-uT8zSN/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073 
drm_wait_one_vblank+0x181/0x190 [drm]
  Jun 20 12:05:18 mymachine kernel: Modules linked in: msr rfcomm ccm veth 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge stp llc 
overlay thunderbolt cmac bnep btusb btrtl btbcm uvcvideo 
  Jun 20 12:05:18 mymachine kernel:  intel_cstate mac80211 intel_rapl_perf 
snd_compress ac97_bus snd_pcm_dmaengine snd_seq_midi snd_seq_midi_event 
snd_hda_intel snd_rawmidi snd_hda_codec snd_hda_core snd_hwdep i
  Jun 20 12:05:18 mymachine kernel:  pps_core drm nvme_core wmi video
  Jun 20 12:05:18 mymachine kernel: CPU: 2 PID: 4445 Comm: Xorg Tainted: G  
  W4.15.0-23-generic #25-Ubuntu
  Jun 20 12:05:18 mymachine kernel: Hardware name: LENOVO 
20HGS30X00/20HGS30X00, BIOS N1WET34W (1.13 ) 06/26/2017
  Jun 20 12:05:18 mymachine kernel: RIP: 0010:drm_wait_one_vblank+0x181/0x190 
[drm]
  Jun 20 12:05:18 mymachine kernel: RSP: 0018:a32ac3b83a68 EFLAGS: 00010282
  Jun 20 12:05:18 mymachine kernel: RAX:  RBX: 8c5175a38000 
RCX: 0006
  Jun 20 12:05:18 mymachine kernel: RDX: 0007 RSI: 0096 
RDI: 8c519e516490
  Jun 20 12:05:18 mymachine kernel: RBP: a32ac3b83ac0 R08: 0001 
R09: 06aa
  Jun 20 12:05:18 mymachine kernel: R10:  R11:  
R12: 0002
  Jun

[Kernel-packages] [Bug 1690085]

2018-06-26 Thread robert

(In reply to OptionalRealName from comment #375)
> Thread still ongoing with no response from AMD.
> 
> Really shouldn't need to fiddle with custom bios options.
> 
> What is big business / big iron or whatever it's called doing with Epyc and
> linux servers? Are those totally fine?

I am running an Epyc-based server, and as posted in this thread here:
https://forums.fedoraforum.org/showthread.php?317537-first-server-error-reboot-what-is-this-UUID
(worth a full read)
everything in there was solved by setting the correct Virtualization flags in 
BIOS, as specified by a Supermicro Tech as follows:

It looks like you want to enable the virtualization feature.
Please go into BIOS,
Advanced -> NB Configuration -> IOMMU (change to Enabled).
Advanced -> PCIe/PCI/PnP Configuration -> SR-IOV Support (change to Enabled).


After this, the server worked without a hitch, and I have now upgraded
it from Centos7, to Fedora 28, and it runs like a charm.

Of course the server is not IDLE at all, and maybe that saves the server
from the low power issue discussed in this thread. However, I have had
it at least 7 days just sitting there not doing anything, and it never
had any problem.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the

[Kernel-packages] [Bug 1773113] Re: nvidia-390 does not show GUI

2018-06-26 Thread claudio@ubuntu

I just tried again to test if nvidia updates would fix this ugly bug. In
summary: no.

I also tried the graphics-drivers ppa mentioned (specifically tried the
340 and 390 drivers) with the same negative results.

The only working solution for my nvidia-prime laptop (nvidia+intel) is
using nouveau+Wayland. Nvidia does not work at all. This is suboptimal
as Wayland is less stable and there is a performance penalty when using
nouveau.

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

Title:
nvidia-390 does not show GUI

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

Bug description:
I know this bug is a duplicate, I am opening it because it seems that for #
#1752053 it is marked as "Fix Released" although many people are still affected
and complaining about it and nobody can or will change that status. So it is an
attempt to raise more attention, as HDMI currently isn't usable for me on
Ubuntu 18.04 (it affected me on 16.04 as well).
Put in short, after Nvidia drivers are installed and I switch from Nvidia
card to the intel one, the GUI can't be opened anymore

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

[Kernel-packages] [Bug 1778705] [NEW] skey in ubuntu-kvm-unit-test failed on Xenial zVM

Public bug reported:

TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1
FAIL skey (2 tests)

This is the only failure in this test suite on Xenial zVM, need to run
it manually to see what's going on.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-130-generic 4.4.0-130.156
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
CurrentDmesg:
 [ 3288.479241] audit_printk_skb: 153 callbacks suppressed
 [ 3288.479246] audit: type=1400 audit(1530011067.825:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine" pid=6480 comm="apparmor_parser"
 [ 3288.510095] audit: type=1400 audit(1530011067.865:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=6480 
comm="apparmor_parser"
Date: Tue Jun 26 07:05:34 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
 
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C
 SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-130-generic N/A
 linux-backports-modules-4.4.0-130-generic  N/A
 linux-firmware 1.157.19
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: apport-bug package-from-proposed s390x xenial

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  skey in ubuntu-kvm-unit-test failed on Xenial zVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  TESTNAME=skey TIMEOUT=90s ACCEL= ./s390x/run s390x/skey.elf -smp 1
  FAIL skey (2 tests)

  This is the only failure in this test suite on Xenial zVM, need to run
  it manually to see what's going on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-130-generic 4.4.0-130.156
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [ 3288.479241] audit_printk_skb: 153 callbacks suppressed
   [ 3288.479246] audit: type=1400 audit(1530011067.825:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine" pid=6480 comm="apparmor_parser"
   [ 3288.510095] audit: type=1400 audit(1530011067.865:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=6480 
comm="apparmor_parser"
  Date: Tue Jun 26 07:05:34 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-130-generic N/A
   linux-backports-modules-4.4.0-130-generic  N/A
   linux-firmware 1.157.19
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about

[Kernel-packages] [Bug 1772081] Re: HP x360 - Ryzen 2500U Locks up

2018-06-26 Thread Freihut

I can't answer your question about battery life according to the
parameters, I did not test that.

If you're running RavenRidge on Ubuntu, you will have to fight the CPU
(Ryzen's CPU lock ups:
https://bugzilla.kernel.org/show_bug.cgi?id=196683 ) and also amdgpu,
because they're still working on it.

1st: Get your CPU working:
AFAIK:
disable SMT (seems to have some weird clocking side effects – I didn't figure 
that out)
OR
set CPU govenor to "powersafe" (will make the Ryzen's clock get kind of fixed 
to max 1,6 or 2ghz)
OR
idle=nomwait (my favorite solution so far)

While you're testing the CPU, try to disable amdgpu by kernel-parameter
"nomodeset" to exclude any amdgpu-issues while testing.

My testcase-setup was: Let Palemoon (Firefox-Fork) autoplay random
videos on Youtube, because it causes some partial load and needs no user
actions. Freezes occurred between 4 minutes and 3 hours.

2nd: Get amdgpu working:
Well. You'll have a lot of fun finding a solution, that works for you!
*Start reading vega-based articles on phoronix.
*Then cry a lot.
*Then try out different versions of mesa/LLVM ( 
https://launchpad.net/~paulo-miguel-dias ).
*Then cry a lot.

I'm was testing Padoka stable ppa with Kernel 4.15 and 4.17.2 (mainline, 
installed via ukuu) and still had freezes (GUI was frozen, but sound was going 
on and REISUB was possible) until I copied new firmware from 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu?id=66e1b33efe227432956136dd46bdb2a9b7f38a27
Just download all raven_*.bin files and put them to /lib/firmware/amdgpu/ and 
reboot. My freezes went away, no matter what Kernel (4.15 or 4.17) I'm using.
But if I'm running:
"update-initramfs -u"
booting will freeze at:
"switching to amdgpudrmfb from EFI VGA"

Solution is to boot with "nomodeset" and run:
"apt remove linux-firmware"
"apt install linux-firmware"
"update-initramfs -u"
and then copy the new firmware again and reboot. But I just ran into that 
issue, so that "solution" is brand new and not much tested. Better have 
backups, as you always should have.

Running RavenRidge on Ubuntu is a bit of a kerfuffle.

** Bug watch added: Linux Kernel Bug Tracker #196683
   https://bugzilla.kernel.org/show_bug.cgi?id=196683

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

Title:
  HP x360 - Ryzen 2500U Locks up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
I have an HP x360 Ryzen 2500u.   It locks up a couple of times a day.   
Before I disabled C6, using this python script 
https://github.com/r4m0n/ZenStates-Linux it would lock up minutes after boot.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stu3022 F pulseaudio
   /dev/snd/controlC0:  stu3022 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-19 (32 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5fbe26ec-88dd-4b0f-8e57-c577efacffc7 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
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  StagingDrivers: r8822be
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP

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

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

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

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

apport-collect 1778534

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

Title:
  Touchpad not working (Elantech ELAN0618)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For a fresh installed Ubuntu 16 (and 18), touchpad doesn't work for
  Elantech ELAN0618.

  We have modified the struct elan_acpi_id, by adding ELAN0618 to the
  list of the supported models (in the file
  drivers/input/mouse/elan_i2c_core.c from the kernel source)

  static const struct acpi_device_id elan_acpi_id[] = {
{ "ELAN", 0 },
{ "ELAN0100", 0 },
{ "ELAN0600", 0 },
{ "ELAN0602", 0 },
{ "ELAN0605", 0 },
{ "ELAN0608", 0 },
{ "ELAN0605", 0 },
{ "ELAN0609", 0 },
{ "ELAN060B", 0 },
{ "ELAN060C", 0 },
{ "ELAN0611", 0 },
{ "ELAN0618", 0 },
{ "ELAN1000", 0 },
{ }
  };

  and then built the kernel, and our problem solved.

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

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

[Kernel-packages] [Bug 1778534] Re: Touchpad not working (Elantech ELAN0618)

2018-06-26 Thread Paul White

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

Title:
  Touchpad not working (Elantech ELAN0618)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For a fresh installed Ubuntu 16 (and 18), touchpad doesn't work for
  Elantech ELAN0618.

  We have modified the struct elan_acpi_id, by adding ELAN0618 to the
  list of the supported models (in the file
  drivers/input/mouse/elan_i2c_core.c from the kernel source)

  static const struct acpi_device_id elan_acpi_id[] = {
{ "ELAN", 0 },
{ "ELAN0100", 0 },
{ "ELAN0600", 0 },
{ "ELAN0602", 0 },
{ "ELAN0605", 0 },
{ "ELAN0608", 0 },
{ "ELAN0605", 0 },
{ "ELAN0609", 0 },
{ "ELAN060B", 0 },
{ "ELAN060C", 0 },
{ "ELAN0611", 0 },
{ "ELAN0618", 0 },
{ "ELAN1000", 0 },
{ }
  };

  and then built the kernel, and our problem solved.

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

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

[Kernel-packages] [Bug 1778534] [NEW] Touchpad not working (Elantech ELAN0618)

You have been subscribed to a public bug:

For a fresh installed Ubuntu 16 (and 18), touchpad doesn't work for
Elantech ELAN0618.

We have modified the struct elan_acpi_id, by adding ELAN0618 to the list
of the supported models (in the file drivers/input/mouse/elan_i2c_core.c
from the kernel source)

static const struct acpi_device_id elan_acpi_id[] = {
{ "ELAN", 0 },
{ "ELAN0100", 0 },
{ "ELAN0600", 0 },
{ "ELAN0602", 0 },
{ "ELAN0605", 0 },
{ "ELAN0608", 0 },
{ "ELAN0605", 0 },
{ "ELAN0609", 0 },
{ "ELAN060B", 0 },
{ "ELAN060C", 0 },
{ "ELAN0611", 0 },
{ "ELAN0618", 0 },
{ "ELAN1000", 0 },
{ }
};

and then built the kernel, and our problem solved.

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


** Tags: bot-comment
-- 
Touchpad not working (Elantech ELAN0618)
https://bugs.launchpad.net/bugs/1778534
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1778658] Re: Nvidia fails after switching its mode

2018-06-26 Thread AceLan Kao

** Tags added: originate-from-1777105 somerville

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

Title:
  Nvidia fails after switching its mode

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Switch Nvidia mode requires rebooting the system. It's because of losing some 
of its status while switching mode if runtime PM is enabled. It's a generic 
issue that would happen on some other devices, too. This patch restores 
devices' config space on runtime resume.

  [Test]
  Test and verify it on machines with Nvidia discrete graphics.

  [Fix]
  Fix by saving and restoring config space over a runtime suspend cycle even if 
the device is not bound.

  [Regression Potential]
  Low. It saves and restores states during suspending and resuming.

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

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

[Kernel-packages] [Bug 1778658] [NEW] Nvidia fails after switching its mode

2018-06-26 Thread AceLan Kao

Public bug reported:

[Impact]
Switch Nvidia mode requires rebooting the system. It's because of losing some 
of its status while switching mode if runtime PM is enabled. It's a generic 
issue that would happen on some other devices, too. This patch restores 
devices' config space on runtime resume.

[Test]
Test and verify it on machines with Nvidia discrete graphics.

[Fix]
Fix by saving and restoring config space over a runtime suspend cycle even if 
the device is not bound.

[Regression Potential]
Low. It saves and restores states during suspending and resuming.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress


** Tags: originate-from-1777105 somerville

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

Title:
  Nvidia fails after switching its mode

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Switch Nvidia mode requires rebooting the system. It's because of losing some 
of its status while switching mode if runtime PM is enabled. It's a generic 
issue that would happen on some other devices, too. This patch restores 
devices' config space on runtime resume.

  [Test]
  Test and verify it on machines with Nvidia discrete graphics.

  [Fix]
  Fix by saving and restoring config space over a runtime suspend cycle even if 
the device is not bound.

  [Regression Potential]
  Low. It saves and restores states during suspending and resuming.

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

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

[Kernel-packages] [Bug 1774150] Re: 3.13.0-149-generic: suspend/resume issue on 14.04

2018-06-26 Thread Kevin Donnelly

The latest 13.0.151 kernel has the same issue, at least on this laptop.
This also means that whatever security updates are rolled into the
mainline kernels are in effect inaccessible to laptop users affected by
this issue. :-(

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

Title:
  3.13.0-149-generic: suspend/resume issue on 14.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 14.04.5 LTS, the most recent kernel update to
  3.13.0-149-generic means that my laptop (Acer Aspire V5) does not
  resume once suspended - all I get is a blank screen, unresponsive to
  keypresses, and I need to reboot.

  The 144 kernel is OK, and this question:
  
https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04
  suggests that 147 is OK too.

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

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

[Kernel-packages] [Bug 1758205] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-path (NVMe / Bolt ) (systemd?)

2018-06-26 Thread Andrew Cloke

As this bug has been closed, could you raise a new bug (possibly
referencing this one) for this issue? Thanks.

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

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk and /dev/disk/by-
  path (NVMe / Bolt ) (systemd?)

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

Bug description:
  ---Problem Description---

  Bolt based NVMe disks (namespaces) are not displayed on lsblk and 
/dev/disk/by-path
  # nvme list 
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 1  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n10S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 10 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n11S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 11 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n12S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 12 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n13S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 13 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n14S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 14 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n15S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 15 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n16S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 16 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n17S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 17 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n18S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 18 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n19S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 19 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n2 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 2  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n20S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 20 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n21S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 21 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n22S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 22 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n23S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 23 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n24S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 24 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n25S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 25 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n26S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 26 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n27S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 27 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n28S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 28 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n29S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 29 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n3 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 3  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n30S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 30 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n31S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 31 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n32S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 32 28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n4 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 4  28.67  GB /  28.67  GB  4 KiB +  0 B   MN12MN12
  /dev/nvme0n5 S3RVNA0J600206   PCIe3 1.6TB NVMe Flash Adapter II x8
 5

Re: [Kernel-packages] [Bug 1778506] Re: Have to restart the bluetooth after sleeping to connect to headphones

2018-06-26 Thread marvin

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

Ah sorry. I did not catch that one. Yes the workaround is easy. Its one of
these two

sudo service bluetooth restart

or

 sudo service network-manager restart


On Tue, Jun 26, 2018 at 4:10 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> *** This bug is a duplicate of bug 1759628 ***
> https://bugs.launchpad.net/bugs/1759628
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. This particular bug has already been reported and is a
> duplicate of bug 1759628, so it is being marked as such. Please look at
> the other bug report to see if there is any missing information that you
> can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report. Feel free to continue to report any other bugs you may
> find.
>
>
> ** This bug has been marked a duplicate of bug 1759628
> bluez regression: Bluetooth audio fails to reconnect after resume
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1778506
>
> Title:
>   Have to restart the bluetooth after sleeping to connect to headphones
>
> Status in bluez package in Ubuntu:
>   New
>
> Bug description:
>   Linux Ubuntu 18-04 X1-18 4.15.0-23-generic
>
>   After suspend my bose bluetooth headphones keep connecting /
>   disconnecting / connecting ... until failure.
>
>   After
>   marvin@X1-18:~$ sudo service bluetooth restart
>
>   everything works fine again.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: bluez 5.48-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
>   Uname: Linux 4.15.0-23-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jun 25 14:06:50 2018
>   InterestingModules: rfcomm bnep btusb bluetooth
>   MachineType: LENOVO 20FRS2M600
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
> root=UUID=fb013004-2044-405c-946d-4da9f7e757e5 ro quiet splash
>   SourcePackage: bluez
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 06/23/2016
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: N1FET41W (1.15 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20FRS2M600
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: None
>   dmi.modalias:
> dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
>   dmi.product.family: ThinkPad X1 Yoga 1st
>   dmi.product.name: 20FRS2M600
>   dmi.product.version: ThinkPad X1 Yoga 1st
>   dmi.sys.vendor: LENOVO
>   hciconfig:
>hci0:Type: Primary  Bus: USB
> BD Address: E4:A7:A0:36:99:9D  ACL MTU: 1021:4  SCO MTU: 96:6
> UP RUNNING PSCAN ISCAN
> RX bytes:358790 acl:11101 sco:0 events:25202 errors:0
> TX bytes:14298744 acl:22439 sco:0 commands:2586 errors:0
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1778506/+subscriptions
>

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

Title:
  Have to restart the bluetooth after sleeping to connect to headphones

Status in bluez package in Ubuntu:
  New

Bug description:
  Linux Ubuntu 18-04 X1-18 4.15.0-23-generic

  After suspend my bose bluetooth headphones keep connecting /
  disconnecting / connecting ... until failure.

  After 
  marvin@X1-18:~$ sudo service bluetooth restart

  everything works fine again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 25 14:06:50 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FRS2M600
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=fb013004-2044-405c-946d-4da9f7e757e5 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET41W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FRS2M600
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias:

[Kernel-packages] [Bug 1770784] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest crashes in apparmor_file_alloc_security()

2018-06-26 Thread Andrew Cloke

Ack. Thanks for the update. Closing.

** Changed in: ubuntu-power-systems
   Status: Incomplete => Invalid

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

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest
  crashes in apparmor_file_alloc_security()

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

Bug description:
  Test was running an Ubuntu 16.04 guest with a Ubuntu 18.04 host when
  the guest dumped a vmcore.

  According to the dump, the crash is actually a BUG_ON() raised from
  apparmor_file_alloc_security() having called aa_begin_current_label()
  which calls aa_current_raw_label() that in turn calls
  aa_cred_raw_label() where the BUG_ON() resides:

static inline struct aa_label *aa_cred_raw_label(const struct cred *cred)
{
struct aa_task_ctx *ctx = cred_ctx(cred);
BUG_ON(!ctx || !ctx->label);
return ctx->label;
}

  Now, the warnings we previously had seen raised from aa_file_perm()
  may have been related since rcu_dereference() as fctx->label is NULL.

fctx = file_ctx(file);
   
rcu_read_lock();
flabel  = rcu_dereference(fctx->label);
   AA_BUG(!flabel);

KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-124-generic
  DUMPFILE: dump.201805110830  [PARTIAL DUMP]
  CPUS: 32
  DATE: Fri May 11 06:30:35 2018
UPTIME: 03:40:43
  LOAD AVERAGE: 102.77, 103.38, 100.54
 TASKS: 862
  NODENAME: boslcp4g4
   RELEASE: 4.4.0-124-generic
   VERSION: #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018
   MACHINE: ppc64le  (2134 Mhz)
MEMORY: 16 GB
 PANIC: "kernel BUG at 
/build/linux-VRGJAN/linux-4.4.0/security/apparmor/include/context.h:69!"
   PID: 18397
   COMMAND: "chgrp"
  TASK: c0035be322c0  [THREAD_INFO: c0035b5c]
   CPU: 10
 STATE: TASK_RUNNING (PANIC)

  
  crash> bt
  PID: 18397  TASK: c0035be322c0  CPU: 10  COMMAND: "chgrp"
   #0 [c0035b5c3430] crash_kexec at c0176274
   #1 [c0035b5c35d0] die at c0020ef8
   #2 [c0035b5c3660] _exception at c0021244
   #3 [c0035b5c37f0] program_check_common at c0006208
   Program Check [700] exception frame:
   R0:  c04923e4R1:  c0035b5c3ae0R2:  c15fa700
   R3:  c000fcd01a00R4:  0001R5:  ffc0
   R6:  c000fcd01b00R7:  0003fe8dR8:  c163a700
   R9:  0001R10: R11: 
   R12: c04fd880R13: c7b06400R14: 
   R15: R16: 0013R17: 
   R18: 3fffb7501468R19: R20: 3fffb74ff7e0
   R21: R22: R23: 3fffdf3cbd40
   R24: 9001R25: 0041R26: f000
   R27: c0035b5c3dd0R28: c16342f8R29: c000fcd01a00
   R30: c000fcd01a00R31: 
   NIP: c04fd8c8MSR: 80029033OR3: c04923e0
   CTR: c04fd880LR:  c04923e4XER: 
   CCR: 24004248MQ:  0001DAR: c00328004288
   DSISR: c0035b5c39e0 Syscall Result: 
   #4 [c0035b5c3ae0] apparmor_file_alloc_security at c04fd8c8
   [Link Register] [c0035b5c3ae0] security_file_alloc at c04923e4
   #5 [c0035b5c3b50] security_file_alloc at c04923e4  (unreliable)
   #6 [c0035b5c3b90] get_empty_filp at c02e7010
   #7 [c0035b5c3c10] path_openat at c02faa2c
   #8 [c0035b5c3c90] do_filp_open at c02fc9bc
   #9 [c0035b5c3db0] do_sys_open at c02e3150
  #10 [c0035b5c3e30] system_call at c0009484
   System Call [c01] exception frame:
   R0:  0005R1:  3fffdf3cb8c0R2:  3fffb7507e00
   R3:  0100270514b0R4:  0008R5:  3fffb7501ef8
   R6:  0008R7:  9001R8:  3fffdf3cbd40
   R9:  R10: R11: 
   R12: R13: 3fffb750a190
   NIP: 3fffb74dbdacMSR: 8280f033OR3: 0100270514b0
   CTR: LR:  3fffb74b7034XER: 
   CCR: 44004442MQ:  0001DAR: 3fffb748
   DSISR: 4000 Syscall Result: fffe

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

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

[Kernel-packages] [Bug 1765668] Re: Unable to boot Xenial cloud image on Bionic ARM64 ThunderX / Azure

It looks like the test has passed with Bionic Azure kernel + Xenial
(guest), I will remove the azure project.

** No longer affects: linux-azure (Ubuntu)

** Summary changed:

- Unable to boot Xenial cloud image on Bionic ARM64 ThunderX / Azure
+ Unable to boot Xenial cloud image on Bionic ARM64 ThunderX

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

Title:
  Unable to boot Xenial cloud image on Bionic ARM64 ThunderX

Status in ubuntu-kernel-tests:
  New
Status in uvtool package in Ubuntu:
  Incomplete
Status in linux-azure source package in Bionic:
  New
Status in uvtool source package in Bionic:
  Incomplete

Bug description:
  Similar to bug 1744754, I can create an Artful KVM on this ThunderX
  ARM64 node with Bionic installed. But not with Xenial.

  Steps:
 # uvt-simplestreams-libvirt sync release=xenial arch=arm64
 # uvt-kvm create test release=xenial arch=arm64
 # uvt-kvm wait test --insecure
 uvt-kvm: error: timed out waiting for dnsmasq lease for 52:54:00:72:91:3a.
 # uvt-kvm ip test
 uvt-kvm: error: no IP address found for libvirt machine 'test'.

  With Artful, although it will return error due to the "Permission Denied" 
error, but you can still ssh into that KVM:
  # uvt-simplestreams-libvirt sync release=artful arch=arm64
  # uvt-kvm create a-test release=artful arch=arm64
  # uvt-kvm wait a-test --insecure
  ubuntu@192.168.122.119: Permission denied (publickey).
  Traceback (most recent call last):
File "/usr/bin/uvt-kvm", line 35, in 
  uvtool.libvirt.kvm.main_cli_wrapper(sys.argv[1:])
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 861, in 
main_cli_wrapper
  main(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 856, in 
main
  args.func(parser, args)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 782, in 
main_wait
  main_wait_remote(parser, args)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 745, in 
main_wait_remote
  insecure=args.insecure,
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 614, in 
ssh
  ssh_call, preexec_fn=subprocess_setup, close_fds=True, stdin=stdin
File "/usr/lib/python2.7/subprocess.py", line 190, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '[u'ssh', u'-o', 
u'UserKnownHostsFile=/tmp/uvt-kvm.known_hoststmpnK_mba', u'-l', u'ubuntu', 
u'192.168.122.119', u'env', u'UVTOOL_WAIT_INTERVAL=8.0', 
u'UVTOOL_WAIT_TIMEOUT=120.0', u'sh', u'-']' returned non-zero exit status 255
  # uvt-kvm ip a-test
  192.168.122.119
  # ssh ubuntu@192.168.122.119 "lsb_release -a"
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: User Name 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 20 09:15 seq
   crw-rw 1 root audio 116, 33 Apr 20 09:15 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Apr 20 10:33:57 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro acpi=force iommu.passthrough=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
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias:

[Kernel-packages] [Bug 1778584] Re: linux-image-3.13.0-151-generic fails to boot

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

Title:
  linux-image-3.13.0-151-generic fails to boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Our machine rebooted over the weekend and fails to boot the new
  3.13.0-151-generic kernel.

  I have fallen back to 3.13.0-149-generic kernel in the meantime.

  Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  --- 
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carmen 1815 F pulseaudio
   /dev/snd/controlC0:  carmen 1815 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0d9024d4-384e-4eea-b1ee-f7a36ce05e7f
  InstallationDate: Installed on 2013-07-08 (1812 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-A75-D3H
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=056dd0ad-a7cd-4b07-a922-9de9da3e17df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-149-generic N/A
   linux-backports-modules-3.13.0-149-generic  N/A
   linux-firmware  1.127.24
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-149-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-09-23 (1006 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True
  dmi.bios.date: 06/13/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-A75-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd06/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75-D3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-A75-D3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1778642] [NEW] ubuntu_lttng_smoke_test failed on Azure 4.15