date:20180628

4.4.0-130.156 - lowlatency
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_kvm_unit_tests - 28 failed on amaura, 18 failed on chico, 21 failed on 
michael
  ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) 
inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) 
fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153)
  xfstests - xfs generic/475 failed

Issue to note in i386:
  ubuntu_ltp_syscalls - fcntl36 failed with X/X-LTS/X-HWE i386 kernel (bug 
1774396) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153)
  xfstests - ext4 generic/113 timed out

4.4.0-130.156 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_kvm_unit_tests - 28 failed on amaura, 21 failed on michael
  ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) 
inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) 
fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153)
  xfstests - xfs generic/475 failed

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - pmu on ms10-34-mcdivittB0-kernel (bug 1751000) 
gicv2-ipi and gicv2-active on starmie
  ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) 
inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) 
fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153)

Issue to note in i386:
  ubuntu_ltp_syscalls - fcntl36 failed with X/X-LTS/X-HWE i386 kernel (bug 
1774396) inotify07 failed with X/X-LTS/A kernel (bug 1774387) inotify08 failed 
with X/X-LTS/X-HWE/A kernel (bug 1775784) fanotify07/fanotify08 test timeouted 
(bug 1775165) fanotify09 timeouted (bug 1775153)
  xfstests - ext4 generic/113 timed out

Issue to note in ppc64le (P8):
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool, bug 1755118
  ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) 
inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) 
fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153)
  ubuntu_lxc - lxc-test-apparmor-mount failed, network issue

Issue to note in s390x (Ubuntu on LPAR):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) 
inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) 
fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153)

Issue to note in s390x (zKVM):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - 12 failed (nested kvm is not supported)
  ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) 
inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) 
fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153)
  ubuntu_lxc - lxc-test-ubuntu(Failed to start networking in ubuntu-cloud 
container)

Issue to note in s390x (zVM):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705)
  ubuntu_ltp_syscalls - inotify07 failed with X/X-LTS/A kernel (bug 1774387) 
inotify08 failed with X/X-LTS/X-HWE/A kernel (bug 1775784) 
fanotify07/fanotify08 test timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153)


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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Title:
  linux: 4.4.0-130.156 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
S

[Kernel-packages] [Bug 1750480] [NEW] package ndiswrapper-dkms 1.60-3~ubuntu16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6

You have been subscribed to a public bug:

why everytime I start the pc it does not start normal and have problems
with apps like Amarok, and play videos and music. please if you send me
information about this for your attention thanks

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ndiswrapper-dkms 1.60-3~ubuntu16.04.2
ProcVersionSignature: Ubuntu 3.16.0-53.72~14.04.1-generic 3.16.7-ckt18
Uname: Linux 3.16.0-53-generic i686
NonfreeKernelModules: xts gf128mul algif_skcipher af_alg dm_crypt hid_generic 
pata_acpi usbhid hid nouveau mxm_wmi i2c_algo_bit ttm drm_kms_helper psmouse 
drm sdhci_pci sdhci ssb ahci firewire_ohci forcedeth firewire_core libahci 
crc_itu_t wmi video
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Mon Feb 19 19:47:43 2018
DpkgHistoryLog:
 Start-Date: 2018-02-19  19:39:27
 Commandline: aptdaemon role='role-remove-packages' sender=':1.76'
 Remove: libqtscript4-uitools:i386 (0.2.0-1), libqtscript4-gui:i386 (0.2.0-1), 
libqjson0:i386 (0.8.1-3), liblastfm1:i386 (1.0.9-1), 
kdemultimedia-kio-plugins:i386 (4:15.12.3-0ubuntu1), libloudmouth1-0:i386 
(1.5.2-1build1), libkcddb4:i386 (4:15.12.3-0ubuntu1), libqtscript4-sql:i386 
(0.2.0-1), libkcompactdisc4:i386 (4:15.12.3-0ubuntu1), amarok-common:i386 
(2:2.8.0-0ubuntu9), libaio1:i386 (0.3.110-2), libqtscript4-xml:i386 (0.2.0-1), 
libtag-extras1:i386 (1.0.1-3build1), amarok:i386 (2:2.8.0-0ubuntu9), 
libqtscript4-core:i386 (0.2.0-1), amarok-utils:i386 (2:2.8.0-0ubuntu9), 
libmygpo-qt1:i386 (1.0.7-0ubuntu2), libqtscript4-network:i386 (0.2.0-1), 
kio-audiocd:i386 (4:15.12.3-0ubuntu1)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 6
InstallationDate: Installed on 2015-10-24 (849 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: ndiswrapper
Title: package ndiswrapper-dkms 1.60-3~ubuntu16.04.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 6
UpgradeStatus: Upgraded to xenial on 2016-08-04 (564 days ago)

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


** Tags: apport-package i386 xenial
-- 
package ndiswrapper-dkms 1.60-3~ubuntu16.04.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 6
https://bugs.launchpad.net/bugs/1750480
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 1750480] Re: package ndiswrapper-dkms 1.60-3~ubuntu16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6

2018-06-28 Thread Julian Andres Klode

depmod failed here when configuring linux image, reassigning

** Package changed: ndiswrapper (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/1750480

Title:
  package ndiswrapper-dkms 1.60-3~ubuntu16.04.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 6

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  why everytime I start the pc it does not start normal and have
  problems with apps like Amarok, and play videos and music. please if
  you send me information about this for your attention thanks

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ndiswrapper-dkms 1.60-3~ubuntu16.04.2
  ProcVersionSignature: Ubuntu 3.16.0-53.72~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-53-generic i686
  NonfreeKernelModules: xts gf128mul algif_skcipher af_alg dm_crypt hid_generic 
pata_acpi usbhid hid nouveau mxm_wmi i2c_algo_bit ttm drm_kms_helper psmouse 
drm sdhci_pci sdhci ssb ahci firewire_ohci forcedeth firewire_core libahci 
crc_itu_t wmi video
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Mon Feb 19 19:47:43 2018
  DpkgHistoryLog:
   Start-Date: 2018-02-19  19:39:27
   Commandline: aptdaemon role='role-remove-packages' sender=':1.76'
   Remove: libqtscript4-uitools:i386 (0.2.0-1), libqtscript4-gui:i386 
(0.2.0-1), libqjson0:i386 (0.8.1-3), liblastfm1:i386 (1.0.9-1), 
kdemultimedia-kio-plugins:i386 (4:15.12.3-0ubuntu1), libloudmouth1-0:i386 
(1.5.2-1build1), libkcddb4:i386 (4:15.12.3-0ubuntu1), libqtscript4-sql:i386 
(0.2.0-1), libkcompactdisc4:i386 (4:15.12.3-0ubuntu1), amarok-common:i386 
(2:2.8.0-0ubuntu9), libaio1:i386 (0.3.110-2), libqtscript4-xml:i386 (0.2.0-1), 
libtag-extras1:i386 (1.0.1-3build1), amarok:i386 (2:2.8.0-0ubuntu9), 
libqtscript4-core:i386 (0.2.0-1), amarok-utils:i386 (2:2.8.0-0ubuntu9), 
libmygpo-qt1:i386 (1.0.7-0ubuntu2), libqtscript4-network:i386 (0.2.0-1), 
kio-audiocd:i386 (4:15.12.3-0ubuntu1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 6
  InstallationDate: Installed on 2015-10-24 (849 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: ndiswrapper
  Title: package ndiswrapper-dkms 1.60-3~ubuntu16.04.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 6
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (564 days ago)

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

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

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

This change was made by a bot.

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

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

Title:
  package ndiswrapper-dkms 1.60-3~ubuntu16.04.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 6

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  why everytime I start the pc it does not start normal and have
  problems with apps like Amarok, and play videos and music. please if
  you send me information about this for your attention thanks

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ndiswrapper-dkms 1.60-3~ubuntu16.04.2
  ProcVersionSignature: Ubuntu 3.16.0-53.72~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-53-generic i686
  NonfreeKernelModules: xts gf128mul algif_skcipher af_alg dm_crypt hid_generic 
pata_acpi usbhid hid nouveau mxm_wmi i2c_algo_bit ttm drm_kms_helper psmouse 
drm sdhci_pci sdhci ssb ahci firewire_ohci forcedeth firewire_core libahci 
crc_itu_t wmi video
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Mon Feb 19 19:47:43 2018
  DpkgHistoryLog:
   Start-Date: 2018-02-19  19:39:27
   Commandline: aptdaemon role='role-remove-packages' sender=':1.76'
   Remove: libqtscript4-uitools:i386 (0.2.0-1), libqtscript4-gui:i386 
(0.2.0-1), libqjson0:i386 (0.8.1-3), liblastfm1:i386 (1.0.9-1), 
kdemultimedia-kio-plugins:i386 (4:15.12.3-0ubuntu1), libloudmouth1-0:i386 
(1.5.2-1build1), libkcddb4:i386 (4:15.12.3-0ubuntu1), libqtscript4-sql:i386 
(0.2.0-1), libkcompactdisc4:i386 (4:15.12.3-0ubuntu1), amarok-common:i386 
(2:2.8.0-0ubuntu9), libaio1:i386 (0.3.110-2), libqtscript4-xml:i386 (0.2.0-1), 
libtag-extras1:i386 (1.0.1-3build1), amarok:i386 (2:2.8.0-0ubuntu9), 
libqtscript4-core:i386 (0.2.0-1), amarok-utils:i386 (2:2.8.0-0ubuntu9), 
libmygpo-qt1:i386 (1.0.7-0ubuntu2), libqtscript4-network:i386 (0.2.0-1), 
kio-audiocd:i386 (4:15.12.3-0ubuntu1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 6
  InstallationDate: Installed on 2015-10-24 (849 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: ndiswrapper
  Title: package ndiswrapper-dkms 1.60-3~ubuntu16.04.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 6
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (564 days ago)

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

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

[Kernel-packages] [Bug 1770423] Re: Please cherry-pick upstream patch for HDMI on Dell XPS 9360

2018-06-28 Thread Michael Stapelberg

As far as I remember, I did not have to do any backporting.

Thanks for looking into this.

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

Title:
  Please cherry-pick upstream patch for HDMI on Dell XPS 9360

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

Bug description:
  Connecting the Dell USB-C HDMI/LAN/VGA/USB adapter to my XPS 9360
  doesn’t quite work: I could not get my monitor to display a picture at
  all, regardless of which resolution I tried.

  A quick search on the internet revealed this patch:
  https://lists.freedesktop.org/archives/intel-
  gfx/2017-March/124077.html. Applying it to the 4.4.0-122 kernel does
  indeed make the HDMI work

  Could you please cherry-pick this patch into the Ubuntu kernel?
  Thanks!

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

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

[Kernel-packages] [Bug 1777242] Re: 4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic)

2018-06-28 Thread Aurélien COUDERC

It kind of works but takes forever to start due to crng initialization.
(Forever like I didn’t wait and ended up pressing some random keys to get 
things moving after more than a minute.)

[6.163871] 8139cp :00:03.0 ens3: link up, 100Mbps, full-duplex, lpa 
0x05E1
[   97.338260] random: crng init done

This problem was not present in former kernel versions.

dmesg attached.

** Attachment added: "dmesg-4.15.0-25-generic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777242/+attachment/5157350/+files/dmesg-4.15.0-25-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/1777242

Title:
  4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic)

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

Bug description:
  Trying to boot bionic with 4.15.0-23-generic fails with a kernel panic in 
qemu on an Debian amd64 host.
  The version of qemu is the current in Debian Testing: 2.12+dfsg-3.

  Booting with 4.15.0-22-generic works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zouzou 1274 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-12 (338 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170710)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux-signed (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=26da642a-bbc4-440b-bed3-a911bbbfe582 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.11.1-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.8
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.11.1-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.8:cvnQEMU:ct1:cvrpc-i440fx-2.8:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.8
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1776340] Re: linux-oem: 4.15.0-1009.12 -proposed tracker

2018-06-28 Thread Brad Figg

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

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

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

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

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

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

[Kernel-packages] [Bug 1779063] [NEW] Occasional kernel panic on shutdown in ext4 code (dquot_drop)

You have been subscribed to a public bug:

Occasionally (about once every three weeks) my machine experiences a
kernel panic somewhere in the ext4 code on shutdown (and only on
shutdown).

Ubuntu Version: 18.04, x86-64

Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

I attached two photos of the panic messages, one occurring on May 16th,
the other on June 26th. The call trace is identical in both.

Given how similar the messages are, I don't think this is an
intermittent machine-related glitch. As of yet, however, I could not
identify a pattern on when the issue occurs.

Kernel versions:
 - May 16th: 4.15.0-20-generic
 - June 26th: 4.15.0-23-generic

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


** Tags: bot-comment kernel-bug
-- 
Occasional kernel panic on shutdown in ext4 code (dquot_drop)
https://bugs.launchpad.net/bugs/1779063
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 1777858] Re: Redpine: Observed kernel panic while running wireless regressions tests

2018-06-28 Thread Kleber Sacilotto de Souza

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

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

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

Title:
  Redpine: Observed kernel panic while running wireless regressions
  tests

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

Bug description:
  SRU Justification:
  --

  Impact:
  Kernel freezes/panic when running wireless tests

  Test case:
  1. Create a wireless soft-ap/station upon reboot.

  2. Install Checkbox plano and :
 $ sudo snap install --devmode checkbox-plano

  3. Run below wifi-ap test case
 $ checkbox-plano.checkbox-cli run .*device 
.*wireless/caracalla-wifi_ap_.*wlan0_auto

  4. Upon 3-4 iteraions, observed kernel crash as below,
 BUG: unable to handle kernel NULL pointer dereference at   
(null)
 IP: [] exit_creds+0x1f/0x50
 PGD 0
 Oops: 0002 [#1] SMP
 CPU: 0 PID: 6502 Comm: rmmod Tainted: G   OE   
4.4.0-128-generic #154-Ubuntu
 Hardware name: Dell Inc. Edge Gateway 3003/  , BIOS 01.00.00 
04/17/2017
 Stack:
 88007392e600 880075847dc0 8108160a 
 88007392e600 880075847de8 810a484b 880076127000
 88003cd3a800 880074f12a00 880075847e28 c09bed15
 Call Trace:
 [] __put_task_struct+0x5a/0x140
 [] kthread_stop+0x10b/0x110
 [] rsi_disconnect+0x2f5/0x300 [ven_rsi_sdio]
 [] ? __pm_runtime_resume+0x5b/0x80
 [] sdio_bus_remove+0x38/0x100
 [] __device_release_driver+0xa4/0x150
 [] driver_detach+0xb5/0xc0
 [] bus_remove_driver+0x55/0xd0
 [] driver_unregister+0x2c/0x50
 [] sdio_unregister_driver+0x1a/0x20
 [] rsi_module_exit+0x15/0x30 [ven_rsi_sdio]
 [] SyS_delete_module+0x1b8/0x210
 [] entry_SYSCALL_64_fastpath+0x1c/0xbb

  Fix:
  kthread_stop() is taking care of wait_for_completion() by default.
  No need of taking care separately.
  Issue is resolved by removing wait_for_completion() from rsi_disconnect().

  Regression Petential:
  Ran Step 3 in 30-times. Didn't see any kernel panic.

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

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

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

[Kernel-packages] [Bug 1779063] Re: Occasional kernel panic on shutdown in ext4 code (dquot_drop)

add "linux" as affected package.

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic

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

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

[Kernel-packages] [Bug 1779063] 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 1779063

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic

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

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

To pin intel-microcode version:

echo "intel-microcode hold" | sudo dpkg --set-selections

-- 
You 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 1774150] Re: 3.13.0-149-generic: suspend/resume issue on 14.04

2018-06-28 Thread kovserg

Thank you. Now resume works fine. This helps:

sudo apt-get install intel-microcode=2.20140122.1

But now ubuntu wants to upgarade it back to 3.20180425.1 on every
update.

-- 
You 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 1765653] Re: directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and Bionic ThunderX ARM64

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

Title:
  directory-concurrent.sh.ext4 in ubuntu_ecryptfs failed on Atrful and
  Bionic ThunderX ARM64

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  This directory-concurrent.sh.ext4 test will fail with 4.13 and 4.15
  kernel on a ThunderX ARM64 node (passed on the other Moonshot node):

  Steps:
    1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests 
-b master-next
    2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
    3. rm -fr autotest/client/tests
    4. ln -sf ~/autotest-client-tests autotest/client/tests
    5. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E 
autotest/client/autotest-local --verbose 
autotest/client/tests/ubuntu_ecryptfs/control

  Output:
   Running 'tests/run_one.sh -K -t directory-concurrent.sh -b 100 -D 
/mnt/image -l /mnt/lower -u /mnt/upper -f ext4'
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing mkdir() - possible eCryptfs hang
   Timed out after 30 seconds doing rmdir() - possible eCryptfs hang
   Timed out after 30 seconds doing

[Kernel-packages] [Bug 1776338] Re: linux: 4.15.0-24.26 -proposed tracker

2018-06-28 Thread Taihsiang Ho

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/bionic/4.15.0-24.26
/bionic-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1776338

Title:
  linux: 4.15.0-24.26 -proposed tracker

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

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

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

  backports: bug 1776346 (linux-azure), bug 1776347 (linux-azure-edge), bug 
1776348 (linux-hwe-edge)
  derivatives: bug 1776339 (linux-raspi2), bug 1776340 (linux-oem), bug 1776341 
(linux-aws), bug 1776342 (linux-azure), bug 1776344 (linux-gcp), bug 1776345 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1773172] Re: quota kernel modules not available in linux-aws

2018-06-28 Thread Glenn

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

** This bug has been marked a duplicate of bug 1678213
   linux-aws does not provide linux-image-extra-$(uname -r)

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

Title:
  quota kernel modules not available in linux-aws

Status in linux-aws package in Ubuntu:
  New

Bug description:
  The quota kernel modules (quota_v1 and quota_v2) are not available in
  the linux-aws kernel, because the modules are contained in the generic
  kernel's linux-image-extra package.

  There is no -extra package for linux-aws, so the quota modules should
  be promoted to the main linux-image package for linux-aws.

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

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

[Kernel-packages] [Bug 1776333] Re: linux: 4.13.0-46.51 -proposed tracker

2018-06-28 Thread Taihsiang Ho

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/artful/4.13.0-46.51
/artful-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1776333

Title:
  linux: 4.13.0-46.51 -proposed tracker

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

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

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

  backports: bug 1776335 (linux-gcp), bug 1776336 (linux-hwe), bug 1776337 
(linux-oem)
  derivatives: bug 1776334 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1680507] Re: breakpoint test from ubuntu_kernel_selftest failed to build on aarch64

Test disabled. 
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=bd5f0644889aa654532f8bac7b531c6bd3a362a2

** Changed in: ubuntu-kernel-tests
   Status: New => Fix Released

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  breakpoint test from ubuntu_kernel_selftest failed to build on aarch64

Status in ubuntu-kernel-tests:
  Fix Released
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in glibc source package in Zesty:
  New
Status in linux source package in Zesty:
  Won't Fix
Status in glibc source package in Artful:
  New
Status in linux source package in Artful:
  New
Status in glibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Confirmed

Bug description:
  stderr:
breakpoint_test_arm64.c: In function ‘set_watchpoint’:
breakpoint_test_arm64.c:91:28: error: storage size of ‘dreg_state’ 
isn’t known
struct user_hwdebug_state dreg_state;
^~
In file included from /usr/include/alloca.h:24:0,
from /usr/include/stdlib.h:453,
from ../kselftest.h:13,
from breakpoint_test_arm64.c:37:
breakpoint_test_arm64.c:98:32: error: invalid use of undefined type 
‘struct user_hwdebug_state’
iov.iov_len = offsetof(struct user_hwdebug_state, dbg_regs) +
^
breakpoint_test_arm64.c: In function ‘run_test’:
breakpoint_test_arm64.c:171:25: error: ‘TRAP_HWBKPT’ undeclared (first 
use in this function)
if (siginfo.si_code != TRAP_HWBKPT) {
^~~
breakpoint_test_arm64.c:171:25: note: each undeclared identifier is 
reported only once for each function it appears in
make: *** [breakpoint_test_arm64] Error 1

  Full log can be found here: http://pastebin.ubuntu.com/24328194/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-18-generic 4.10.0-18.20
  ProcVersionSignature: User Name 4.10.0-18.20-generic 4.10.8
  Uname: Linux 4.10.0-18-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  6 14:48 seq
   crw-rw 1 root audio 116, 33 Apr  6 14:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Apr  6 14:50:50 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-18-generic N/A
   linux-backports-modules-4.10.0-18-generic  N/A
   linux-firmware 1.164
  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/1680507/+subscriptions

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

[Kernel-packages] [Bug 1778932] [NEW] rsync can trigger system crash

You have been subscribed to a public bug:

I'm not sure how much of this is rsync or something else in my system. I
can reliably trigger this using rsync to transfer files from one drive
to another drive on my computer.   the source is ssd and destination is
mdadm raid 1 partition.  will attach syslog messages. after it is
triggered, the the system becomes unresponsive and requires a hard
reboot. running rysnc as user, no special privileges.

 
root@music:~# lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04


 apt-cache policy rsync 
rsync:
  Installed: 3.1.2-2.1ubuntu1
  Candidate: 3.1.2-2.1ubuntu1
  Version table:
 *** 3.1.2-2.1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


uname -a
Linux music 4.15.0-23-lowlatency #25-Ubuntu SMP PREEMPT Wed May 23 20:39:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: rsync 3.1.2-2.1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18
Uname: Linux 4.15.0-23-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 27 10:08:36 2018
InstallationDate: Installed on 2018-03-31 (87 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 LANGUAGE=en_US
 PATH=(custom, no user)
SourcePackage: rsync
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic
-- 
rsync can trigger system crash
https://bugs.launchpad.net/bugs/1778932
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 1776349] Re: linux: -proposed tracker

2018-06-28 Thread Kleber Sacilotto de Souza

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

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

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

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

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

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

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

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-lbm series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid

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

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

  backports: 
  derivatives:

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

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

[Kernel-packages] [Bug 1775847] Re: fanatic docker test in ubuntu_fan_smoke_test failed on Bionic s390x

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

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1772505
   [18.04] [regression testing] ubuntu_fan_smoke_tests failing on s390x

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

Title:
  fanatic docker test in ubuntu_fan_smoke_test failed on Bionic s390x

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

Bug description:
  This is not a regression, this can be found on 4.15.0-21.22 as well.

  * Command:
    ./ubuntu_fan_smoke_test.sh 10.245.0.0/16
    Exit status: 1
    Duration: 58.4590229988

    stdout:
    Running in the Canonical CI environment
    Testing Fan Networking (pre-0.13.0 API)
    docker pull s390x/ubuntu: PASSED
    enable disable fan test: PASSED
    fanctl show test: PASSED
    fanctl check bridge config test: PASSED
    fanatic docker test(--dns=10.245.80.1): FAILED (fanatic enable-docker 
returned 1)
    stderr:
    debconf: delaying package configuration, since apt-utils is not installed
    Job for docker.service failed.
    See "systemctl status docker.service" and "journalctl -xe" for details.

  This is the log from "journalctl -xe":
  Jun 08 14:28:49 kernel02 systemd[1]: docker.service: Start request repeated 
too quickly.
  Jun 08 14:28:49 kernel02 systemd[1]: docker.service: Failed with result 
'start-limit-hit'.
  Jun 08 14:28:49 kernel02 systemd[1]: Failed to start Docker Application 
Container Engine.

  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 s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Fri Jun  8 14:26:44 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M 
BOOT_IMAGE=0
  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: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1778932] Re: rsync can trigger system crash

2018-06-28 Thread Robie Basak

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Reassigning to the kernel since rsync should never be able to crash the
system and if it crashes it's usually the kernel or bad hardware that's
responsible.

** Package changed: rsync (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/1778932

Title:
  rsync can trigger system crash

Status in linux package in Ubuntu:
  New

Bug description:
  I'm not sure how much of this is rsync or something else in my system.
  I can reliably trigger this using rsync to transfer files from one
  drive to another drive on my computer.   the source is ssd and
  destination is mdadm raid 1 partition.  will attach syslog messages.
  after it is triggered, the the system becomes unresponsive and
  requires a hard reboot. running rysnc as user, no special privileges.

   
  root@music:~# lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
   apt-cache policy rsync 
  rsync:
Installed: 3.1.2-2.1ubuntu1
Candidate: 3.1.2-2.1ubuntu1
Version table:
   *** 3.1.2-2.1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  uname -a
  Linux music 4.15.0-23-lowlatency #25-Ubuntu SMP PREEMPT Wed May 23 20:39:43 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsync 3.1.2-2.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18
  Uname: Linux 4.15.0-23-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Jun 27 10:08:36 2018
  InstallationDate: Installed on 2018-03-31 (87 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   LANGUAGE=en_US
   PATH=(custom, no user)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1778932] 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 1778932

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

Title:
  rsync can trigger system crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm not sure how much of this is rsync or something else in my system.
  I can reliably trigger this using rsync to transfer files from one
  drive to another drive on my computer.   the source is ssd and
  destination is mdadm raid 1 partition.  will attach syslog messages.
  after it is triggered, the the system becomes unresponsive and
  requires a hard reboot. running rysnc as user, no special privileges.

   
  root@music:~# lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
   apt-cache policy rsync 
  rsync:
Installed: 3.1.2-2.1ubuntu1
Candidate: 3.1.2-2.1ubuntu1
Version table:
   *** 3.1.2-2.1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  uname -a
  Linux music 4.15.0-23-lowlatency #25-Ubuntu SMP PREEMPT Wed May 23 20:39:43 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsync 3.1.2-2.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18
  Uname: Linux 4.15.0-23-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Jun 27 10:08:36 2018
  InstallationDate: Installed on 2018-03-31 (87 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   LANGUAGE=en_US
   PATH=(custom, no user)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1776346] Re: linux-azure: 4.15.0-1014.14~16.04.1 -proposed tracker

This kernel is identical to linux-azure-edge

4.15.0-1014.14~16.04.1 - azure
Regression test CMPL, RTB.

Issue to note in x86_64 (azure):
  ebizzy - failed on Standard_A0, passed on the rest
  libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad 
config 3, passed on the rest
  monotonic_time - all two tests (or just tsc test) failed on some instances, 
passed on the rest
  ubuntu_kvm_unit_tests - test skipped due to no KVM support, vmx_control will 
crash E4 nodes (bug 1747892)
  ubuntu_ltp_syscalls - inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 
1775784)
  ubuntu_lttng_smoke_test - module failed to build (bug 1765673)
  ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in 
ubuntu-cloud container, Failed creating ubuntu-cloud container due to too many 
open files), passed on the rest
  ubuntu_quota_smoke_test - need the -extra package (bug 1777114)
  ubuntu_ramfs_stress - failed on StandardA0 only
  ubuntu_stress_smoke_test - sysfs caused kernel oopsed on some instances (bug 
1757057)
  ubuntu_unionmount_overlayfs_suite - File unexpectedly on union layer (bug 
1751243)
  ubuntu_zram_smoke_test - zram module missing (bug 1762756)

Skipped / blacklisted:
  * ubuntu_ltp
  * ubuntu_nbd_smoke_test
  * ubuntu_quota_smoke_test
  * ubuntu_ramfs_stress
  * ubuntu_seccomp
  * ubuntu_sysdig_smoke_test
  * ubuntu_vfat_stress

Note that the unionmount overlayfs test was manually tested, it's
affected by bug 1779107

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

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

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

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

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

[Kernel-packages] [Bug 1753941] Re: ubuntu_bpf_jit test failed on Bionic s390x systems

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

** Changed in: ubuntu-kernel-tests
   Status: New => 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/1753941

Title:
  ubuntu_bpf_jit test failed on Bionic s390x systems

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  In Progress

Bug description:
  Not sure if this is related to bug 1751234 (error on AMD64 system is
  different)

  The ubuntu_bpf_jit test will fail with the following 5 test cases:

  test_bpf: #292 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #293 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create 
err=-524 len=4096
  test_bpf: #298 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096
  test_bpf: #299 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524
  test_bpf: #300 BPF_MAXINSNS: jump around ld_abs FAIL to select_runtime 
err=-524

  test_bpf: Summary: 337 PASSED, 5 FAILED, [329/329 JIT'ed]

  And modprobe error can be found in the report as well:
  modprobe: ERROR: could not insert 'test_bpf': Invalid argument

  Issue can be reproduce on both zVM and Ubuntu on LPAR s390x systems.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-11-generic 4.15.0-11.12
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  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': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Wed Mar  7 08:13:51 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M 
BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-11-generic N/A
   linux-backports-modules-4.15.0-11-generic  N/A
   linux-firmware 1.172
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1776819] Re: linux: 3.13.0-153.203 -proposed tracker

3.13.0-153.203 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_kvm_smoke_test - uvt-kvm wait issue on Trusty(bug 1732883)
  ubuntu_kvm_unit_tests - 40 failed on amaura, 26 failed on zeppo
  ubuntu_ltp_syscalls - fcntl35 / fcntl35_64 in LTP syscall test failed with 
T/X/X-LTS kernel (bug 1774394) fanotify06 failed with T kernel (bug 1775378) 
fanotify07/fanotify08 in LTP syscall test generates kernel trace with T kernel 
(bug 1775165) fanotify09 failed with A/T kernel (bug 1775153) request_key03 in 
LTP syscall test cause kernel oops with T kernel (bug 1775370)

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  libhugetlbfs - noresv-preserve-resv-page failed (bug 1747823) 
chunk-overcommit failed (bug 1747828)
  ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376)
  ubuntu_kvm_smoke_test - getlogin will fail to open /proc/self/loginuid (bug 
1770245)
  ubuntu_qrt_apparmor - test_old_trusty_regression_testsuite failed to build 
(bug 1699987)
  ubuntu_qrt_kernel_security - test 021, 022 (bug 1747847) test 050 (bug 
1684776) test 072 (bug 1747850) test 075 (bug 1712007) test 82 (bug 1747853)
  ubuntu_ltp_syscalls - looks like the test crashed on inotify09

Issue to note in i386:
  ubuntu_docker_smoke_test - test case issue (bug 1779109)
  ubuntu_kvm_smoke_test - uvt-kvm wait issue on Trusty(bug 1732883)
  ubuntu_ltp_syscalls - fcntl35 / fcntl35_64 in LTP syscall test failed with 
T/X/X-LTS kernel (bug 1774394) fanotify06 failed with T kernel (bug 1775378) 
fanotify07/fanotify08 in LTP syscall test generates kernel trace with T kernel 
(bug 1775165) fanotify09 failed with A/T kernel (bug 1775153) request_key03 in 
LTP syscall test cause kernel oops with T kernel (bug 1775370)

Issue to note in ppc64le (P8):
  ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376)
  ubuntu_kvm_smoke_test - no supported architecture for 'hvm' (bug 1752550)
  ubuntu_ltp_syscalls - fanotify07/fanotify08 in LTP syscall test generates 
kernel trace with T kernel (bug 1775165) fanotify09 failed with A/T kernel (bug 
1775153)
  ubuntu_lxc - lxc-test-ubuntu failed (Failed creating ubuntu-cloud container)

Note: ubuntu_ltp_syscalls test on Trusty needs further investigation,
the crash should not be considered as a regression since there is no
baseline yet.

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

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

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

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

  backports: bug 1776820 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1776822] Re: linux: 4.4.0-130.156 -proposed tracker

2018-06-28 Thread Taihsiang Ho

Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-130.156
/xenial-proposed-published.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   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/1776822

Title:
  linux: 4.4.0-130.156 -proposed tracker

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

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

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

  backports: bug 1776823 (linux-lts-xenial), bug 1776824 (linux-aws)
  derivatives: bug 1776357 (linux-euclid), bug 1776826 (linux-kvm), bug 1776359 
(linux-raspi2), bug 1776361 (linux-snapdragon), bug 1776829 (linux-aws)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1776276] Re: linux: 4.17.0-2.3 -proposed tracker

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

** This bug has been marked a duplicate of bug 1779124
   linux: 4.17.0-3.4 -proposed tracker

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

Title:
  linux: 4.17.0-2.3 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.17.0-2.3 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

  kernel-phase-changed:Tuesday, 12. June 2018 23:01 UTC
  kernel-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1779124] [NEW] linux: 4.17.0-3.4 -proposed tracker

Public bug reported:

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

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

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

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

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

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

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


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

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

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

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

** Tags added: cosmic

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

** Changed in: kernel-sru-workflow
   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/1779124

Title:
  linux: 4.17.0-3.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow pro

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

4.15.0-1010.10~16.04.1 - gcp
Regression test CMPL, RTB.

Issue to note in gcp:
  libhugetlbfs - 1 failed , 1 killed by signal, 3 bad config
  ubuntu_kvm_unit_tests - failed due to no KVM support
  ubuntu_ltp_syscalls - inotify08 failed with X/X-LTS/X-HWE/A/B kernel (bug 
1775784)
  ubuntu_lttng_smoke_test - lttng module failed to build (bug 1779114)
  ubuntu_quota_smoke_test - need the -extra package (bug 1777114)
  ubuntu_unionmount_overlayfs_suite - File unexpectedly on union layer (bug 
1751243)

Skipped / blacklisted:
 * ubuntu_ltp
 * ubuntu_nbd_smoke_test
 * ubuntu_seccomp
 * ubuntu_sysdig_smoke_test
 * ubuntu_zram_smoke_test

Note that the lttng module build issue is a new one. Considering it's
just a DKMS issue I will not consider it as a regression.

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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

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

Bug description:
  This bug is for tracking the 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: 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/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 1779124] Re: linux: 4.17.0-3.4 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux: 4.17.0-3.4 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.17.0-3.4 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

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

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

[Kernel-packages] [Bug 1779114] [NEW] lttng module failed to build on 4.15.0-1010.10~16.04.1

Public bug reported:

Error! Bad return status for module build on kernel: 4.15.0-1010-gcp
(x86_64)

BTW this module can be built on 4.15 GCP kernel on Bionic (just not
4.15.0-1010.10~16.04.1 on Xenial)

** Affects: lttng-modules
 Importance: Undecided
 Status: New

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

** Also affects: lttng-modules
   Importance: Undecided
   Status: New

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

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

Title:
  lttng module failed to build on 4.15.0-1010.10~16.04.1

Status in lttng-modules:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-gcp package in Ubuntu:
  New

Bug description:
  Error! Bad return status for module build on kernel: 4.15.0-1010-gcp
  (x86_64)

  BTW this module can be built on 4.15 GCP kernel on Bionic (just not
  4.15.0-1010.10~16.04.1 on Xenial)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lttng-modules/+bug/1779114/+subscriptions

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

[Kernel-packages] [Bug 1779116] [NEW] Cosmic update to v4.17.1 stable release

Public bug reported:


SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

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

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Fix Committed


** Tags: kernel-stable-tracking-bug

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  Cosmic update to v4.17.1 stable release

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

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

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

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

[Kernel-packages] [Bug 1779117] [NEW] Cosmic update to v4.17.2 stable release

Public bug reported:


SRU Justification

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

   git://git.kernel.org/

TEST CASE: TBD

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

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Fix Committed


** Tags: kernel-stable-tracking-bug

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

Title:
  Cosmic update to v4.17.2 stable release

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

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

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

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

[Kernel-packages] [Bug 1777242] Re: 4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic)

2018-06-28 Thread wayne

Tested this v2 test kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777242

No problems from my side.

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

Title:
  4.15.0-23-generic fails to boot in qemu on amd64 host (kernel panic)

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

Bug description:
  Trying to boot bionic with 4.15.0-23-generic fails with a kernel panic in 
qemu on an Debian amd64 host.
  The version of qemu is the current in Debian Testing: 2.12+dfsg-3.

  Booting with 4.15.0-22-generic works fine.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zouzou 1274 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-07-12 (338 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170710)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux-signed (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=26da642a-bbc4-440b-bed3-a911bbbfe582 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (128 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.11.1-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.8
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.11.1-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.8:cvnQEMU:ct1:cvrpc-i440fx-2.8:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.8
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1779063] Re: Occasional kernel panic on shutdown in ext4 code (dquot_drop)

apport information

** Tags added: apport-collected bionic

** Description changed:

  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).
  
  Ubuntu Version: 18.04, x86-64
  
  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.
  
  I attached two photos of the panic messages, one occurring on May 16th,
  the other on June 26th. The call trace is identical in both.
  
  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.
  
  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  maik   1743 F pulseaudio
+  /dev/snd/controlC1:  maik   1743 F pulseaudio
+  /dev/snd/controlC0:  maik   1743 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
+ InstallationDate: Installed on 2017-08-25 (306 days ago)
+ InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 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: Upgraded to bionic on 2018-04-26 (62 days ago)
+ UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/08/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: L4.82
+ dmi.board.name: AB350M 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.:bvrL4.82:bd05/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1779063/+attachment/5157441/+files/AlsaInfo.txt

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maik   1743 F pulseaudio
   /dev/snd/controlC1:  maik   1743 F pulseaudio
   /dev/snd/controlC0:  maik   1743 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
  InstallationDate: Installed on 2017-08-25 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 ro quiet splash vt.handoff=1
  ProcVersionSig

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

apport information

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

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maik   1743 F pulseaudio
   /dev/snd/controlC1:  maik   1743 F pulseaudio
   /dev/snd/controlC0:  maik   1743 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
  InstallationDate: Installed on 2017-08-25 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 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: Upgraded to bionic on 2018-04-26 (62 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L4.82
  dmi.board.name: AB350M 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.:bvrL4.82:bd05/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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/1779063/+subscriptions

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

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

apport information

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

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maik   1743 F pulseaudio
   /dev/snd/controlC1:  maik   1743 F pulseaudio
   /dev/snd/controlC0:  maik   1743 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
  InstallationDate: Installed on 2017-08-25 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 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: Upgraded to bionic on 2018-04-26 (62 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L4.82
  dmi.board.name: AB350M 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.:bvrL4.82:bd05/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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/1779063/+subscriptions

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

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1779063/+attachment/5157445/+files/Lspci.txt

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maik   1743 F pulseaudio
   /dev/snd/controlC1:  maik   1743 F pulseaudio
   /dev/snd/controlC0:  maik   1743 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
  InstallationDate: Installed on 2017-08-25 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 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: Upgraded to bionic on 2018-04-26 (62 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L4.82
  dmi.board.name: AB350M 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.:bvrL4.82:bd05/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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/1779063/+subscriptions

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

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

apport information

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

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maik   1743 F pulseaudio
   /dev/snd/controlC1:  maik   1743 F pulseaudio
   /dev/snd/controlC0:  maik   1743 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
  InstallationDate: Installed on 2017-08-25 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 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: Upgraded to bionic on 2018-04-26 (62 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L4.82
  dmi.board.name: AB350M 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.:bvrL4.82:bd05/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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/1779063/+subscriptions

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

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1779063/+attachment/5157448/+files/ProcCpuinfoMinimal.txt

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maik   1743 F pulseaudio
   /dev/snd/controlC1:  maik   1743 F pulseaudio
   /dev/snd/controlC0:  maik   1743 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
  InstallationDate: Installed on 2017-08-25 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 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: Upgraded to bionic on 2018-04-26 (62 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L4.82
  dmi.board.name: AB350M 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.:bvrL4.82:bd05/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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/1779063/+subscriptions

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

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

apport information

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

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maik   1743 F pulseaudio
   /dev/snd/controlC1:  maik   1743 F pulseaudio
   /dev/snd/controlC0:  maik   1743 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
  InstallationDate: Installed on 2017-08-25 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 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: Upgraded to bionic on 2018-04-26 (62 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L4.82
  dmi.board.name: AB350M 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.:bvrL4.82:bd05/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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/1779063/+subscriptions

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

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

apport information

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

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maik   1743 F pulseaudio
   /dev/snd/controlC1:  maik   1743 F pulseaudio
   /dev/snd/controlC0:  maik   1743 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
  InstallationDate: Installed on 2017-08-25 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 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: Upgraded to bionic on 2018-04-26 (62 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L4.82
  dmi.board.name: AB350M 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.:bvrL4.82:bd05/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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/1779063/+subscriptions

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

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

apport information

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

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maik   1743 F pulseaudio
   /dev/snd/controlC1:  maik   1743 F pulseaudio
   /dev/snd/controlC0:  maik   1743 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
  InstallationDate: Installed on 2017-08-25 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 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: Upgraded to bionic on 2018-04-26 (62 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L4.82
  dmi.board.name: AB350M 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.:bvrL4.82:bd05/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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/1779063/+subscriptions

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

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

apport information

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

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

Title:
  Occasional kernel panic on shutdown in ext4 code (dquot_drop)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Occasionally (about once every three weeks) my machine experiences a
  kernel panic somewhere in the ext4 code on shutdown (and only on
  shutdown).

  Ubuntu Version: 18.04, x86-64

  Platform: AMD Ryzen R7 2700 on an Asrock AB350M-Pro4 mainboard.

  I attached two photos of the panic messages, one occurring on May
  16th, the other on June 26th. The call trace is identical in both.

  Given how similar the messages are, I don't think this is an
  intermittent machine-related glitch. As of yet, however, I could not
  identify a pattern on when the issue occurs.

  Kernel versions:
   - May 16th: 4.15.0-20-generic
   - June 26th: 4.15.0-23-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  maik   1743 F pulseaudio
   /dev/snd/controlC1:  maik   1743 F pulseaudio
   /dev/snd/controlC0:  maik   1743 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=a4be9bd2-a879-438d-be59-41d095ad18fb
  InstallationDate: Installed on 2017-08-25 (306 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=20c38f5a-e4d2-4cee-9daa-84a848f15452 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: Upgraded to bionic on 2018-04-26 (62 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L4.82
  dmi.board.name: AB350M 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.:bvrL4.82:bd05/08/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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/1779063/+subscriptions

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

[Kernel-packages] [Bug 1774181] Re: Update to upstream's implementation of Spectre v1 mitigation

2018-06-28 Thread Juerg Haefliger

For Trusty 3.13, add the following patches:
  * UBUNTU: SAUCE: filter: Use barrier_nospec() instead of osb()
  * UBUNTU: SAUCE: Rename osb() to barrier_nospec()
  * UBUNTU: SAUCE: Replace osb() calls with array_index_nospec()
  * nospec: Kill array_index_nospec_mask_check()
  * nospec: Move array_index_nospec() parameter checking into separate macro
  * nospec: Allow index argument to have const-qualified type
  * x86/kvm: Update spectre-v1 mitigation
  * x86/spectre: Report get_user mitigation for spectre_v1
  * nl80211: Sanitize array index in parse_txq_params
  * vfs, fdtable: Prevent bounds-check bypass via speculative execution
  * x86/syscall: Sanitize syscall table de-references under speculation
  * x86/get_user: Use pointer masking to limit speculation
  * x86: Introduce barrier_nospec
  * x86: Implement array_index_mask_nospec
  * array_index_nospec: Sanitize speculative array de-references
  * Documentation: Document array_index_nospec

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

Title:
  Update to upstream's implementation of Spectre v1 mitigation

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Xenial/Trusty/Precise are currently lacking full support of upstream's
  Spectre v1 mitigation. Add the missing patches and merge them with
  Ubuntu's current implementation.

  == SRU Justification ==
  Ubuntu's Spectre v1 mitigation is based on the original embargoed patchset 
which introduced a barrier macro to prevent speculation beyond array boundaries 
for user controlled indices. What eventually landed in upstream is slightly 
different and uses a barrier macro in combination with a masking solution (plus 
syscall table and user pointer sanitation). During the updates to newer stable 
upstream versions, all those patches were skipped. After reviewing them, we 
want to bring them back and merge them with the current implementation which 
brings us back in sync with upstream stable.

  == Fix ==
  Add all the missing Spectre v1 patches from upstream stable 4.4.118 to 
4.4.131. Where appropriate, replace Ubuntu's additional barriers with the 
masking macro.

  == Regression Potential ==
  Low. The patches have been in upstream for quite a while now and we keep the 
speculation barriers that are currently in Ubuntu but not in upstream.

  == Test Case ==
  TBD.

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

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

[Kernel-packages] [Bug 1779156] [NEW] lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

2018-06-28 Thread Scott Moser

Public bug reported:

I'm not sure exactly what got me into this state, but I have several lxc
containers that cannot be deleted.

$ lxc info

api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate: |
-BEGIN CERTIFICATE-

-END CERTIFICATE-
  certificate_fingerprint: 
3af6f8b8233c5d9e898590a9486ded5c0bec045488384f30ea921afce51f75cb
  driver: lxc
  driver_version: 3.0.1
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.15.0-23-generic
  server: lxd
  server_pid: 15123
  server_version: "3.2"
  storage: zfs
  storage_version: 0.7.5-1ubuntu15
  server_clustered: false
  server_name: milhouse

$ lxc delete --force b1
Error: Failed to destroy ZFS filesystem: cannot destroy 
'default/containers/b1': dataset is busy

Talking in #lxc-dev, stgraber and sforeshee provided diagnosis:

 | short version is that something unshared a mount namespace causing
 | them to get a copy of the mount table at the time that dataset was
 | mounted, which then prevents zfs from being able to destroy it)

The work around provided was

 | you can unstick this particular issue by doing:
 |  grep default/containers/b1 /proc/*/mountinfo
 | then for any of the hits, do:
 |   nsenter -t PID -m -- umount 
/var/snap/lxd/common/lxd/storage-pools/default/containers/b1
 | then try the delete again

ProblemType: Bug
DistroRelease: Ubuntu 18.10
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
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  smoser31412 F pulseaudio
 /dev/snd/controlC2:  smoser31412 F pulseaudio
 /dev/snd/controlC0:  smoser31412 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 28 10:42:45 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (1071 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
MachineType: 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 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.174
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2015
dmi.bios.vendor: Intel Corporation
dmi.bios.version: RYBDWi35.86A.0246.2015.0309.1355
dmi.board.asset.tag: �
dmi.board.name: NUC5i5RYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H40999-503
dmi.chassis.asset.tag: �
dmi.chassis.type: 3
dmi.chassis.vendor: �
dmi.chassis.version: �
dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0246.2015.0309.1355:bd03/09/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr:
dmi.product.family: �
dmi.product.name: �
dmi.product.version: �
dmi.sys.vendor: �

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


** Tags: amd64 apport-bug cosmic

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

Title:
  lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure exactly what got me into this state, but I have several
  lxc containers that cannot be deleted.

  $ lxc info
  
  api_status: stable
  api_version: "1.0"
  auth: trusted
  public: false
  auth_methods:
  - tls
  environment:
addresses: []
architectures:
- x86_64
- i686
certificate: |
  -BEGIN CERTIFICATE-
  
  -END CERTIFICATE-
certificate_fingerprint: 
3af6f8b8233c5d9e898590a9486ded5c0bec045488384f30ea921afce51f75cb
driver: lxc
driver_version: 3.0.1
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.15.0-23-generic
server: lxd
server_pid: 15123
server_version: "3.2"
storage: zfs
storage_version: 0.7.5-1ubuntu15
server_clustered: false
server_name:

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

This change was made by a bot.

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

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

Title:
  lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure exactly what got me into this state, but I have several
  lxc containers that cannot be deleted.

  $ lxc info
  
  api_status: stable
  api_version: "1.0"
  auth: trusted
  public: false
  auth_methods:
  - tls
  environment:
addresses: []
architectures:
- x86_64
- i686
certificate: |
  -BEGIN CERTIFICATE-
  
  -END CERTIFICATE-
certificate_fingerprint: 
3af6f8b8233c5d9e898590a9486ded5c0bec045488384f30ea921afce51f75cb
driver: lxc
driver_version: 3.0.1
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.15.0-23-generic
server: lxd
server_pid: 15123
server_version: "3.2"
storage: zfs
storage_version: 0.7.5-1ubuntu15
server_clustered: false
server_name: milhouse

  $ lxc delete --force b1
  Error: Failed to destroy ZFS filesystem: cannot destroy 
'default/containers/b1': dataset is busy

  Talking in #lxc-dev, stgraber and sforeshee provided diagnosis:

   | short version is that something unshared a mount namespace causing
   | them to get a copy of the mount table at the time that dataset was
   | mounted, which then prevents zfs from being able to destroy it)

  The work around provided was

   | you can unstick this particular issue by doing:
   |  grep default/containers/b1 /proc/*/mountinfo
   | then for any of the hits, do:
   |   nsenter -t PID -m -- umount 
/var/snap/lxd/common/lxd/storage-pools/default/containers/b1
   | then try the delete again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  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
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  smoser31412 F pulseaudio
   /dev/snd/controlC2:  smoser31412 F pulseaudio
   /dev/snd/controlC0:  smoser31412 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 28 10:42:45 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (1071 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  MachineType: 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
 
b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 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.174
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0246.2015.0309.1355
  dmi.board.asset.tag: �
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-503
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 3
  dmi.chassis.vendor: �
  dmi.chassis.version: �
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0246.2015.0309.1355:bd03/09/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr:
  dmi.product.family: �
  dmi.product.name: �
  dmi.product.version: �
  dmi.sys.vendor: �

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

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

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2018-06-28 Thread Svip

I am having a similar problem after upgrading to 18.04 on a Dell
Precision M4600, with the following specs:

- Intel Core i7 2640M
- NVidia Quadro 2000M

I have disabled Bluetooth entirely, because I don't need it.  But the
NVidia loading/unloading (add/remove) in udev keeps persisting.  I can
disable this by removing the nvidia-rules (71-nvidia-rules) from the
rules.d-directory, but that also disables the module entirely, and I
need the nvidia module, I just wish it would not unload.

This issue seems to be about Bluetooth, although plenty of mentions of
NVidia, should I create a separate one for the nvidia driver issue?

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

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Confirmed
Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1779173] [NEW] Dell D6000 dock lacks multicast Ethernet functionality

Public bug reported:

Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However,
multicast Ethernet traffic is not processed making IPv6 not functional.
Other services, like mDNS used for LAN service discovery are also
hindered.

The actual reason is that CDC_NCM driver was not processing requests to
filter (admit) multicast traffic. I provide two patches to the linux
kernel that admit all Ethernet multicast traffic whenever a multicast
group is being joined.

The solution is not optimal, as it makes the system receive more traffic
than that strictly needed, but otherwise this only happens when the
computer is connected to a dock and thus is running on AC power. I
believe it is not worth the hassle to join only the requested groups.
This is the same that is done in the CDN_ETHER driver.

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

** Patch added: "[PATCH 1/2] Hook into usbnet_change_mtu respecting usbnet
driver_info"

https://bugs.launchpad.net/bugs/1779173/+attachment/5157467/+files/0001-Hook-into-usbnet_change_mtu-respecting-usbnet-driver.patch

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

Title:
Dell D6000 dock lacks multicast Ethernet functionality

Status in linux package in Ubuntu:
New

Bug description:
Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However,
multicast Ethernet traffic is not processed making IPv6 not
functional. Other services, like mDNS used for LAN service discovery
are also hindered.

The actual reason is that CDC_NCM driver was not processing requests
to filter (admit) multicast traffic. I provide two patches to the
linux kernel that admit all Ethernet multicast traffic whenever a
multicast group is being joined.

The solution is not optimal, as it makes the system receive more
traffic than that strictly needed, but otherwise this only happens
when the computer is connected to a dock and thus is running on AC
power. I believe it is not worth the hassle to join only the requested
groups. This is the same that is done in the CDN_ETHER driver.

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

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

[Kernel-packages] [Bug 1779173] Re: Dell D6000 dock lacks multicast Ethernet functionality

** Patch added: "[PATCH 2/2] Admit multicast traffic"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779173/+attachment/5157468/+files/0002-Admit-multicast-traffic.patch

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

Title:
Dell D6000 dock lacks multicast Ethernet functionality

Status in linux package in Ubuntu:
New

The actual reason is that CDC_NCM driver was not processing requests
to filter (admit) multicast traffic. I provide two patches to the
linux kernel that admit all Ethernet multicast traffic whenever a
multicast group is being joined.

The solution is not optimal, as it makes the system receive more
traffic than that strictly needed, but otherwise this only happens
when the computer is connected to a dock and thus is running on AC
power. I believe it is not worth the hassle to join only the requested
groups. This is the same that is done in the CDN_ETHER driver.

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

[Kernel-packages] [Bug 1779173] Re: Dell D6000 dock lacks multicast Ethernet functionality

2018-06-28 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Dell D6000 dock lacks multicast Ethernet functionality

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However,
  multicast Ethernet traffic is not processed making IPv6 not
  functional. Other services, like mDNS used for LAN service discovery
  are also hindered.

  The actual reason is that CDC_NCM driver was not processing requests
  to filter (admit) multicast traffic. I provide two patches to the
  linux kernel that admit all Ethernet multicast traffic whenever a
  multicast group is being joined.

  The solution is not optimal, as it makes the system receive more
  traffic than that strictly needed, but otherwise this only happens
  when the computer is connected to a dock and thus is running on AC
  power. I believe it is not worth the hassle to join only the requested
  groups. This is the same that is done in the CDN_ETHER driver.

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

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

[Kernel-packages] [Bug 1779173] 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 1779173

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

Title:
  Dell D6000 dock lacks multicast Ethernet functionality

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However,
  multicast Ethernet traffic is not processed making IPv6 not
  functional. Other services, like mDNS used for LAN service discovery
  are also hindered.

  The actual reason is that CDC_NCM driver was not processing requests
  to filter (admit) multicast traffic. I provide two patches to the
  linux kernel that admit all Ethernet multicast traffic whenever a
  multicast group is being joined.

  The solution is not optimal, as it makes the system receive more
  traffic than that strictly needed, but otherwise this only happens
  when the computer is connected to a dock and thus is running on AC
  power. I believe it is not worth the hassle to join only the requested
  groups. This is the same that is done in the CDN_ETHER driver.

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Re: ubuntu_lttng_smoke_test failed on Azure 4.15

2018-06-28 Thread Kleber Sacilotto de Souza

This is probably being caused by the following commit:

commit 4fbb658dd8ce96384852ceae18b0b09034de7b36
Author: Marcelo Henrique Cerri 
Date:   Mon Jun 11 18:22:54 2018 -0300

UBUNTU: [Config] azure: CONFIG_HOTPLUG_CPU=n

The lttng_hp_prepare and lttng_hp_online variables are declared inside a
#ifdef block and are probably used somewhere else without the proper
checking.

So this is a regression that needs to be fixed on the lttng dkms code.

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

Title:
  ubuntu_lttng_smoke_test failed on Azure 4.15

Status in lttng-modules:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  New

Bug description:
  ***THIS IS A POTENTIAL REGRESSION***

  This test will pass with the older kernel, 4.15.0-1013-azure, but not
  the 4.15.0-1014-azure in -proposed.

  It looks like the kernel module can be installed, but four tests have
  failed:

  == lttng smoke test of session create/destroy ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)

  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)

  == lttng smoke test trace open/close system calls ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-14716-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  Summary: 4 passed, 4 failed

  http://10.246.72.46/4.15.0-1014.14-azure/bionic-linux-azure-
  
azure-4.15.0-Standard_D12-ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test/results/ubuntu_lttng_smoke_test
  .lttng-smoke-test/debug/ubuntu_lttng_smoke_test.lttng-smoke-
  test.DEBUG.html

  Error message from /var/log/syslog:

   kernel: [  639.531889] PKCS#7 signature not signed with a trusted key
   kernel: [  639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.606845] PKCS#7 signature not signed with a trusted key
   kernel: [  639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.677124] PKCS#7 signature not signed with a trusted key
   kernel: [  639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.737914] PKCS#7 signature not signed with a trusted key
   kernel: [  639.753366] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.753394] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available
   kernel: [  639.829710] PKCS#7 signature not signed with a trusted key
   kernel: [  639.843736] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
   kernel: [  639.843765] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
   lttng-sessiond[1097]: Error: Unable to load required module 
lttng-ring-buffer-client-discard
   lttng-sessiond[1097]: Warning: No kernel tracer available

To manage notifications about this bug go to:
https://bugs.launchpad.net/lttng-modules/+bug/1778642/+subscriptions

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

[Kernel-packages] [Bug 1779173] Re: Dell D6000 dock lacks multicast Ethernet functionality

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

Title:
  Dell D6000 dock lacks multicast Ethernet functionality

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However,
  multicast Ethernet traffic is not processed making IPv6 not
  functional. Other services, like mDNS used for LAN service discovery
  are also hindered.

  The actual reason is that CDC_NCM driver was not processing requests
  to filter (admit) multicast traffic. I provide two patches to the
  linux kernel that admit all Ethernet multicast traffic whenever a
  multicast group is being joined.

  The solution is not optimal, as it makes the system receive more
  traffic than that strictly needed, but otherwise this only happens
  when the computer is connected to a dock and thus is running on AC
  power. I believe it is not worth the hassle to join only the requested
  groups. This is the same that is done in the CDN_ETHER driver.

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

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

[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

2018-06-28 Thread Paulo Marcel Coelho Aragão

I'd like to test the patched kernel but I've stumbled across this error
when I try to install the linux-image-unsigned package and I haven't
found out how to solve it:

paulo:~/Downloads$ sudo dpkg -i 
linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26_lp1776887_amd64.deb
dpkg: regarding 
linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26_lp1776887_amd64.deb 
containing linux-image-unsigned-4.15.0-23-generic:
 linux-image-unsigned-4.15.0-23-generic conflicts with 
linux-image-4.15.0-23-generic
  linux-image-4.15.0-23-generic (version 4.15.0-23.25) is present and installed.

dpkg: error processing archive 
linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26_lp1776887_amd64.deb 
(--install):
 conflicting packages - not installing linux-image-unsigned-4.15.0-23-generic
Errors were encountered while processing:
 linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26_lp1776887_amd64.deb

I suspect I'm missing something very basic.

My current kernel image is: 4.15.0-23.25

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

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

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

Bug description:
  This upstream bug has been confirmed to affect Ubuntu users[1].  As
  per the fix commit (below), the most frequent symptom is a crash of
  Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
  from system sleep.  Frequency of the bug is described as once every
  few days[2].

  [1] E.g. this user confirms the bug & very specific workaround: 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
  [2] E.g. this log of crashes: 
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23

  This is a bug in blk-core.c.  It is not specific to any one hardware
  driver.  Technically the suspend bug is triggered by the SCSI core -
  which is used by *all SATA devices*.

  The commit also includes a test which quickly and reliably proves the
  existence of a horrifying bug.

  I guess you might avoid this bug only if you have root on NVMe.  The
  other way to not hit the Xorg crash is if you don't use all your RAM,
  so there's no pressure that leads to cold pages of Xorg being swapped.
  Also, you won't reproduce the Xorg crash if you suspend+resume
  immediately.  (This frustrated my tests at one point, it only
  triggered after left the system suspended over lunch :).

  Fix: "block: do not use interruptible wait anywhere"

  in kernel 4.17:
  
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428

  in kernel 4.16.8:
  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
  stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6

  lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
  /~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
  core.c?id=Ubuntu-4.15.0-24.26#n856

  I.e., this bug is still present in Ubuntu source package
  linux-4.15.0-24.26 (and 4.15.0-23.25).  I attach hardware details
  (lspci-vnvn.log) of a system where this bug is known to happen.

  Regards
  Alan

  WORKAROUND: Use kernel parameter:
  scsi_mod.scan=sync

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

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

[Kernel-packages] [Bug 1779173] Re: Dell D6000 dock lacks multicast Ethernet functionality

** Bug watch added: Linux Kernel Bug Tracker #200331
   https://bugzilla.kernel.org/show_bug.cgi?id=200331

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=200331
   Importance: Unknown
   Status: Unknown

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

Title:
  Dell D6000 dock lacks multicast Ethernet functionality

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

Bug description:
  Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However,
  multicast Ethernet traffic is not processed making IPv6 not
  functional. Other services, like mDNS used for LAN service discovery
  are also hindered.

  The actual reason is that CDC_NCM driver was not processing requests
  to filter (admit) multicast traffic. I provide two patches to the
  linux kernel that admit all Ethernet multicast traffic whenever a
  multicast group is being joined.

  The solution is not optimal, as it makes the system receive more
  traffic than that strictly needed, but otherwise this only happens
  when the computer is connected to a dock and thus is running on AC
  power. I believe it is not worth the hassle to join only the requested
  groups. This is the same that is done in the CDN_ETHER driver.

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk

2018-06-28 Thread Jun Kong

Tried that rc2 kernel, still the same problem.

root@localhost:~# 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
root@localhost:~# nvme list
Node SN   Model
Namespace Usage  Format   FW Rev
   
- --  
/dev/nvme0n1 CJH0020005EB HUSMR7616BDP301  
1   1.92  TB /   1.92  TB512   B +  8 B   KNECD105

root@localhost:~# uname -sr
Linux 4.18.0-041800rc2-generic
root@localhost:~#


** Changed in: linux (Ubuntu Bionic)
   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:
  Incomplete
Status in linux source package in Bionic:
  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 1779187] [NEW] Ubuntu 16.04.4: crash can not open dumps: "crash: invalid structure member offset: task_struct_pids"

You have been subscribed to a public bug:

Ubuntu 16.04 on IBM z: crash can not open dumps gathered on 4.13.0-39
crash: invalid structure member offset: task_struct_pids
FILE: task.c  LINE: 2102  FUNCTION: refresh_hlist_task_table_v3()

 
---uname output---
Linux fvtc2i 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:41:28 UTC 
2018 s390x s390x s390x GNU/Linux
 
---Additional Hardware Info---
none 

 
Machine Type = lpar type 3906, model 400 LM2  
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 crash vmlinux-4.13.0-39-generic dump.201806150854
or
crash vmlinux-4.13.0-39-generic
 
Userspace tool common name: crash 
 
The userspace tool has the following bit modes: 64 

Userspace rpm: crash,crash-dbgsym  7.1.4-1ubuntu4.2 s390x

Userspace tool obtained from project website:  na 
 
We came across this issue while trying to extract traces from a vmcore gathered 
on one of our Ubuntu 16.04 nodes running HWE kernel (4.13)

It seems crash cannot open this dump

# crash vmlinux-4.13.0-39-generic dump.201806150854

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 "s390x-ibm-linux-gnu"...

WARNING: cannot determine MAX_PHYSMEM_BITS
please wait... (gathering task table data)
crash: invalid structure member offset: task_struct_pids
   FILE: task.c  LINE: 2102  FUNCTION: refresh_hlist_task_table_v3()

[/usr/bin/crash] error trace: 116ed1ed8 => 116ec4b14 => 116f25eec =>
116f25e48


this issue is 100% reproducible. An attempt to analyze the live system
is failing with exact the same error.

# crash vmlinux-4.13.0-39-generic

crash 7.1.4
...
WARNING: cannot determine MAX_PHYSMEM_BITS

crash: invalid structure member offset: task_struct_pids
   FILE: task.c  LINE: 2102  FUNCTION: refresh_hlist_task_table_v3()

[/usr/bin/crash] error trace: 1260d1ed8 => 1260c4b14 => 126125eec =>
126125e48


it seems that crash version 7.2.1 shipped with Ubuntu 18.04 can handle dumps 
taken on kernel 4.13, so we have at least a workaround.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-169322 severity-medium 
targetmilestone-inin16044
-- 
Ubuntu 16.04.4: crash can not open dumps: "crash: invalid structure member 
offset: task_struct_pids"
https://bugs.launchpad.net/bugs/1779187
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 1779187] [NEW] Ubuntu 16.04.4: crash can not open dumps: "crash: invalid structure member offset: task_struct_pids"

2018-06-28 Thread bugproxy

Public bug reported:

Ubuntu 16.04 on IBM z: crash can not open dumps gathered on 4.13.0-39
crash: invalid structure member offset: task_struct_pids
FILE: task.c  LINE: 2102  FUNCTION: refresh_hlist_task_table_v3()

 
---uname output---
Linux fvtc2i 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:41:28 UTC 
2018 s390x s390x s390x GNU/Linux
 
---Additional Hardware Info---
none 

 
Machine Type = lpar type 3906, model 400 LM2  
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 crash vmlinux-4.13.0-39-generic dump.201806150854
or
crash vmlinux-4.13.0-39-generic
 
Userspace tool common name: crash 
 
The userspace tool has the following bit modes: 64 

Userspace rpm: crash,crash-dbgsym  7.1.4-1ubuntu4.2 s390x

Userspace tool obtained from project website:  na 
 
We came across this issue while trying to extract traces from a vmcore gathered 
on one of our Ubuntu 16.04 nodes running HWE kernel (4.13)

It seems crash cannot open this dump

# crash vmlinux-4.13.0-39-generic dump.201806150854

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 "s390x-ibm-linux-gnu"...

WARNING: cannot determine MAX_PHYSMEM_BITS
please wait... (gathering task table data)
crash: invalid structure member offset: task_struct_pids
   FILE: task.c  LINE: 2102  FUNCTION: refresh_hlist_task_table_v3()

[/usr/bin/crash] error trace: 116ed1ed8 => 116ec4b14 => 116f25eec =>
116f25e48


this issue is 100% reproducible. An attempt to analyze the live system
is failing with exact the same error.

# crash vmlinux-4.13.0-39-generic

crash 7.1.4
...
WARNING: cannot determine MAX_PHYSMEM_BITS

crash: invalid structure member offset: task_struct_pids
   FILE: task.c  LINE: 2102  FUNCTION: refresh_hlist_task_table_v3()

[/usr/bin/crash] error trace: 1260d1ed8 => 1260c4b14 => 126125eec =>
126125e48


it seems that crash version 7.2.1 shipped with Ubuntu 18.04 can handle dumps 
taken on kernel 4.13, so we have at least a workaround.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-169322 severity-medium 
targetmilestone-inin16044

** Tags added: architecture-s39064 bugnameltc-169322 severity-medium
targetmilestone-inin16044

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

Title:
  Ubuntu 16.04.4: crash can not open dumps: "crash: invalid structure
  member offset: task_struct_pids"

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 on IBM z: crash can not open dumps gathered on 4.13.0-39
  crash: invalid structure member offset: task_struct_pids
  FILE: task.c  LINE: 2102  FUNCTION: refresh_hlist_task_table_v3()

   
  ---uname output---
  Linux fvtc2i 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:41:28 UTC 
2018 s390x s390x s390x GNU/Linux
   
  ---Additional Hardware Info---
  none 

   
  Machine Type = lpar type 3906, model 400 LM2  
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   crash vmlinux-4.13.0-39-generic dump.201806150854
  or
  crash vmlinux-4.13.0-39-generic
   
  Userspace tool common name: crash 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: crash,crash-dbgsym  7.1.4-1ubuntu4.2 s390x

  Userspace tool obtained from project website:  na 
   
  We came across this issue while trying to extract traces from a vmcore 
gathered on one of our Ubuntu 16.04 nodes running HWE kernel (4.13)

  It seems crash cannot open this dump

  # crash vmlinux-4.13.0-39-generic dump.201806150854

  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 C

[Kernel-packages] [Bug 1511511] Re: USB keyboard stops working after pressing extended key

2018-06-28 Thread Alejandro Díaz-Caro

I confirm the module works like a charm on Arch Linux, kernel 4.17.
Thanks!
(Here are the instructions to compile it: 
https://help.ubuntu.com/community/DKMS)

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

Title:
  USB keyboard stops working after pressing extended key

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  USB keyboard Cougar 500k Gaming Keyboard has some additional extended
  keys, all of them making the keyboard stop responding if pressed under
  linux. The device is recovered only by unplugging the USB and plugging
  it again.

  The keyboard has been tested under Ubuntu 14.04.3 LTS, Ubuntu 15.04
  and Ubuntu 15.10 (the latter running as virtualbox guest). All tests
  failed with exactly the same behaviour.

  USB ID is: "060b:500a Solid Year".

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: 
boot/vmlinuz-4.2.0-16-generic]
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pinfli 1055 F pulseaudio
  Date: Thu Oct 29 19:33:23 2015
  HibernationDevice: RESUME=UUID=f68f4b91-ea68-4e4b-9a10-8ed5bca2efbe
  InstallationDate: Installed on 2015-10-24 (5 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IwConfig:
   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 060b:500a Solid Year
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=523dfd8b-b825-47e3-a116-cb85f901386c ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill:

  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1778029] Re: Use "Medium power with Device Initiated PM" as default LPM policy for mobile SATA devices

2018-06-28 Thread Evgen

Before making final decision please consider that some users experience
issues with this option. For example:
https://bugzilla.redhat.com/show_bug.cgi?id=1571330 ,
https://bugzilla.redhat.com/show_bug.cgi?id=1578072

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

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

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

Title:
  Use "Medium power with Device Initiated PM" as default LPM policy for
  mobile SATA devices

Status in linux-oem package in Ubuntu:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  Intel CPU can't reach beyond Package C-State 3 (PC3). Drains lots of power.

  [Test]
  Check the value of 
/sys/devices/pci:00/:00:17.0/ata1/host0/scsi_host/host0/link_power_management_policy.

  It's med_power_with_dipm as default.
  Also check the powertop, it can reach PC8.

  [Fix]
  Introduce a new config to let AHCI pick med_power_with_dipm for mobile 
platforms.

  [Regression Potential]
  Medium. Some SATA devices are broken under med_power_with_dipm or min_power.
  Fortunately this is for -oem kernel only, so every SATA device gets tested 
before shipping to customers.

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

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

[Kernel-packages] [Bug 1766777] Re: test_182_config_hardened_usercopy in kernel security test failed with 4.15 KVM kernel

2018-06-28 Thread Steve Beattie

The test is correcty detecting that the bionic linux-kvm kernel
CONFIG_HARDENED_USERCOPY is unset, which is inconsistent with the
setting for the master bionic kernel.

** Changed in: qa-regression-testing
   Status: New => Invalid

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

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

Title:
  test_182_config_hardened_usercopy  in kernel security test failed with
  4.15 KVM kernel

Status in QA Regression Testing:
  Invalid
Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-kvm source package in Bionic:
  New

Bug description:
  Test test_182_config_hardened_usercopy from the kernel security test
  suite failed with 4.15.0-1008 KVM kernel.

FAIL: test_182_config_hardened_usercopy (__main__.KernelSecurityTest)
Ensure CONFIG_HARDENED_USERCOPY is set
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2176, in 
test_182_config_hardened_usercopy
self.assertTrue(self._test_config(config_name))
AssertionError: False is not true


  
  The CONFIG_HARDENED_USERCOPY is not set.
  $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_HARDENED_USERCOPY
  # CONFIG_HARDENED_USERCOPY is not set

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
  ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
  Uname: Linux 4.15.0-1008-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 04:36:58 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1779199] [NEW] hangs when resume from hibernation (Fault errors on pipe A)

2018-06-28 Thread Serge Gavrilov

Public bug reported:

Kernel: linux-image-4.15.0-23-generic
Ubuntu: 18.04 
Hardware: Lenovo ThinkPad X1 Yoga 2nd,
model 20JD0026RT

Basically the bug is

https://bugs.freedesktop.org/show_bug.cgi?id=100378
https://bugs.freedesktop.org/show_bug.cgi?id=105196

Downgrade to the latest mainline kernel 4.14.52 fixes the problem.

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

Title:
  hangs when resume from hibernation (Fault errors on pipe A)

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel: linux-image-4.15.0-23-generic
  Ubuntu: 18.04 
  Hardware: Lenovo ThinkPad X1 Yoga 2nd,
  model 20JD0026RT

  Basically the bug is

  https://bugs.freedesktop.org/show_bug.cgi?id=100378
  https://bugs.freedesktop.org/show_bug.cgi?id=105196

  Downgrade to the latest mainline kernel 4.14.52 fixes the problem.

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

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

[Kernel-packages] [Bug 1776887] Re: Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash after suspend

2018-06-28 Thread Joseph Salisbury

Did you install the linux-modules, linux-modules-extra packages first?

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

Title:
  Critical upstream bugfix missing in Ubuntu 18.04 - frequent Xorg crash
  after suspend

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

Bug description:
  This upstream bug has been confirmed to affect Ubuntu users[1].  As
  per the fix commit (below), the most frequent symptom is a crash of
  Xorg/Xwayland, i.e. killing the entire GUI, when a laptop is woken
  from system sleep.  Frequency of the bug is described as once every
  few days[2].

  [1] E.g. this user confirms the bug & very specific workaround: 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1760450/comments/11
  [2] E.g. this log of crashes: 
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c23

  This is a bug in blk-core.c.  It is not specific to any one hardware
  driver.  Technically the suspend bug is triggered by the SCSI core -
  which is used by *all SATA devices*.

  The commit also includes a test which quickly and reliably proves the
  existence of a horrifying bug.

  I guess you might avoid this bug only if you have root on NVMe.  The
  other way to not hit the Xorg crash is if you don't use all your RAM,
  so there's no pressure that leads to cold pages of Xorg being swapped.
  Also, you won't reproduce the Xorg crash if you suspend+resume
  immediately.  (This frustrated my tests at one point, it only
  triggered after left the system suspended over lunch :).

  Fix: "block: do not use interruptible wait anywhere"

  in kernel 4.17:
  
https://github.com/torvalds/linux/commit/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428

  in kernel 4.16.8:
  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
  stable.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6

  lack of fix in 4.15.0-24.26 (ubuntu 18.04): https://git.launchpad.net
  /~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
  core.c?id=Ubuntu-4.15.0-24.26#n856

  I.e., this bug is still present in Ubuntu source package
  linux-4.15.0-24.26 (and 4.15.0-23.25).  I attach hardware details
  (lspci-vnvn.log) of a system where this bug is known to happen.

  Regards
  Alan

  WORKAROUND: Use kernel parameter:
  scsi_mod.scan=sync

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

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

[Kernel-packages] [Bug 1779199] 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 1779199

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

Title:
  hangs when resume from hibernation (Fault errors on pipe A)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel: linux-image-4.15.0-23-generic
  Ubuntu: 18.04 
  Hardware: Lenovo ThinkPad X1 Yoga 2nd,
  model 20JD0026RT

  Basically the bug is

  https://bugs.freedesktop.org/show_bug.cgi?id=100378
  https://bugs.freedesktop.org/show_bug.cgi?id=105196

  Downgrade to the latest mainline kernel 4.14.52 fixes the problem.

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

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

[Kernel-packages] [Bug 1765302] Re: ubuntu_qrt_apparmor test will fail on Azure 4.13 Standard-A0

2018-06-28 Thread Steve Beattie

Yes, this does look like an OOM condition. Does this happen now that
linux-azure has moved to to the 4.15 kernel?

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

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

Title:
  ubuntu_qrt_apparmor test will fail on Azure 4.13 Standard-A0

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-azure package in Ubuntu:
  Incomplete

Bug description:
  The test_regression_testsuite in ubuntu_qrt_apparmor test constantly
  fails on Azure 4.13 Standard-A0 node (passed on the other nodes).

  Run parser regression tests ... (Applying patch 
r3446-fix-sysctl-syscall-detection.patch) (Applying patch 
tests-readdir-lp1674245.patch) (Applying patch tests-max_path-lp1692543.patch) 
(Applying patch r3701-tests-pivot_root.patch) (Applying patch 
r3702-tests-query_label.patch) ok
  test_regression_testsuite (__main__.ApparmorTestsuites)
    preparing apparmor_2.10.95-0ubuntu2.9.dsc...  done
   ERRORubuntu_qrt_apparmor.test-apparmor.py
ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1524115809localtime=Apr 
19 05:30:09   Test subprocess failed rc=9
   END ERRORubuntu_qrt_apparmor.test-apparmor.py
ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1524115826localtime=Apr 
19 05:30:26
  Persistent state client._record_indent now set to 1
  Persistent state client.unexpected_reboot deleted
  END GOOD  timestamp=1524115851localtime=Apr 19 
05:30:51

  Not sure if it's because of insufficient memory:
  $ free -m
    totalusedfree  shared  buff/cache   
available
  Mem:647 251  59   2 336 
225
  Swap: 0   0   0

  If you execute the "ubuntu-bug linux" command after this test, it will 
trigger an OOM event on it.
  Please find the dmesg output here: http://paste.ubuntu.com/p/dH7mf5Vnzs/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-1012-azure 4.13.0-1012.15
  ProcVersionSignature: User Name 4.13.0-1012.15-username 4.13.13
  Uname: Linux 4.13.0-1012-azure x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 19 06:27:08 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-azure
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2018-06-28 Thread Serge Gavrilov

apport information

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

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

Title:
  hangs when resume from hibernation (Fault errors on pipe A)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel: linux-image-4.15.0-23-generic
  Ubuntu: 18.04 
  Hardware: Lenovo ThinkPad X1 Yoga 2nd,
  model 20JD0026RT

  Basically the bug is

  https://bugs.freedesktop.org/show_bug.cgi?id=100378
  https://bugs.freedesktop.org/show_bug.cgi?id=105196

  Downgrade to the latest mainline kernel 4.14.52 fixes the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-27 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.14.52-041452-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/1779199/+subscriptions

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

[Kernel-packages] [Bug 1779199] Re: hangs when resume from hibernation (Fault errors on pipe A)

2018-06-28 Thread Serge Gavrilov

apport information

** Tags added: apport-collected bionic

** Description changed:

  Kernel: linux-image-4.15.0-23-generic
  Ubuntu: 18.04 
  Hardware: Lenovo ThinkPad X1 Yoga 2nd,
  model 20JD0026RT
  
  Basically the bug is
  
  https://bugs.freedesktop.org/show_bug.cgi?id=100378
  https://bugs.freedesktop.org/show_bug.cgi?id=105196
  
  Downgrade to the latest mainline kernel 4.14.52 fixes the problem.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-06-27 (1 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ Package: linux (not installed)
+ Tags:  bionic
+ Uname: Linux 4.14.52-041452-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

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1779199/+attachment/5157528/+files/ProcCpuinfoMinimal.txt

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

Title:
  hangs when resume from hibernation (Fault errors on pipe A)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel: linux-image-4.15.0-23-generic
  Ubuntu: 18.04 
  Hardware: Lenovo ThinkPad X1 Yoga 2nd,
  model 20JD0026RT

  Basically the bug is

  https://bugs.freedesktop.org/show_bug.cgi?id=100378
  https://bugs.freedesktop.org/show_bug.cgi?id=105196

  Downgrade to the latest mainline kernel 4.14.52 fixes the problem.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-27 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.14.52-041452-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/1779199/+subscriptions

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

[Kernel-packages] [Bug 1773520] Re: After update to 4.13-43 Intel Graphics are Laggy

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

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

Title:
  After update to 4.13-43 Intel Graphics are Laggy

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

Bug description:
  == SRU Justification ==
  The bug reporter states that after update to Kernel 4.13-43 the intel
  graphics seem to really lag - especially noticeable in apps which are
  using vsync, which, at least on his system, locks to 40fps unlike the
  previous kernel.

  See https://askubuntu.com/questions/1039189/today-i-got-an-update-and-
  graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for
  some other users with the same issue

  This regression was introduced by upstream commit dc911f5bd8aa.  A
  revert of this commit fixes this bug.  Upstream has already reverted
  this commit in drm-tip tree and cc'd it to upstream stable.  However,
  the revert has not landed in mainline or stable yet, so it is being sent
  as a SAUCE patch.

  The revert is also needed in Bionic. However, the Bionic revert is
  slightly differant, so it will be SRU'd separately.

  == Fix ==
  UBUNTU: SAUCE: Revert "drm/i915/edp: Allow alternate fixed mode for eDP if 
available."

  == Regression Potential ==
  Low.  This revert is to fix a current regression.

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


  After update to Kernel 4.13-43 the intel graphics seem to really lag -
  especially noticeable in apps which are using vsync, which, at least
  on my system, locks to 40fps unlike the previous kernel I have
  installed (4.13-41) which locks at a steady 60fps.

  See https://askubuntu.com/questions/1039189/today-i-got-an-update-and-
  graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for
  some other users with the same issue

  In short
  4.13-41 doesn't have the problem
  4.13-43 has the laggy problem
  ---
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  2835 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ac1331a0-15f2-4832-aebc-48e3ad655add
  InstallationDate: Installed on 2016-05-31 (724 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Gaming Notebook
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-43-generic N/A
   linux-backports-modules-4.13.0-43-generic  N/A
   linux-firmware 1.157.18
  Tags:  xenial
  Uname: Linux 4.13.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker libvirtd lpadmin plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/16/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.53
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A9
  dmi.board.vendor: HP
  dmi.board.version: 91.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.53:bd09/16/2015:svnHP:pnHPPavilionGamingNotebook:pvrType1ProductConfigId:rvnHP:rn80A9:rvr91.18:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Gaming Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1756700] Re: Ryzen/Raven Ridge USB ports do not work

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

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

Title:
  Ryzen/Raven Ridge USB ports do not work

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

Bug description:
  ===SRU Justification===
  [Impact]
  USB controller stops working once a USB device gets plugged.

  [Fix]
  Add a delay for xHC can workaround the issue.

  [Test]
  Plug a USB device to affected system. USB controller stop working
  afterward.
  With the patch, the issue is solved.

  [Regression Potential] 
  Low. Trivial patch which adds a delay. No functional change.

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

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

[Kernel-packages] [Bug 1778261] Re: large KVM instances run out of IRQ routes

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

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

Title:
  large KVM instances run out of IRQ routes

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  When starting large KVM instances with large numbers of attached
  devices may run KVM out of IRQ routes.  Up the system limit to allow
  these configurations to boot.

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

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

[Kernel-packages] [Bug 1778265] Re: Bionic update: upstream stable patchset 2018-06-22

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

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

Title:
  Bionic update: upstream stable patchset 2018-06-22

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

Bug description:
  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-22 (ported from v4.14.39 and v4.16.7)
     from git://git.kernel.org/

  drm/amd/display: Disallow enabling CRTC without primary plane with FB
  drm/amd/display: Fix deadlock when flushing irq
  drm/i915/audio: set minimum CD clock to twice the BCLK
  drm/i915/fbdev: Enable late fbdev initial configuration
  drm/edid: Reset more of the display info
  module: Fix display of wrong module .text address
  PCI / PM: Do not clear state_saved in pci_pm_freeze() when smart suspend is 
set
  ASoC: dmic: Fix clock parenting
  block: do not use interruptible wait anywhere
  serial: mvebu-uart: Fix local flags handling on termios update
  powerpc/eeh: Fix race with driver un/bind
  arm/arm64: KVM: Add PSCI version selection API
  tick/sched: Do not mess with an enqueued hrtimer
  x86/microcode: Do not exit early from __reload_late()
  x86/microcode/intel: Save microcode patch unconditionally
  x86/smpboot: Don't use mwait_play_dead() on AMD systems
  x86/ipc: Fix x32 version of shmid64_ds and msqid64_ds
  tools/lib/subcmd/pager.c: do not alias select() params
  objtool, perf: Fix GCC 8 -Wrestrict error
  drm/i915: Enable display WA#1183 from its correct spot
  drm/amdgpu: set COMPUTE_PGM_RSRC1 for SGPR/VGPR clearing shaders
  earlycon: Use a pointer table to fix __earlycon_table stride
  fpga-manager: altera-ps-spi: preserve nCONFIG state
  libceph: validate con->state at the top of try_write()
  libceph: reschedule a tick in finish_hunting()
  libceph: un-backoff on tick when we have a authenticated session
  ASoC: fsl_esai: Fix divisor calculation failure at lower ratio
  crypto: drbg - set freed buffers to NULL
  KVM: arm/arm64: Close VMID generation race
  ARM: socfpga_defconfig: Remove QSPI Sector 4K size force
  ARM: amba: Don't read past the end of sysfs "driver_override" buffer
  ARM: amba: Fix race condition with driver_override
  ARM: amba: Make driver_override output consistent with other buses
  PCI: aardvark: Fix PCIe Max Read Request Size setting
  PCI: aardvark: Use ISR1 instead of ISR0 interrupt in legacy irq mode
  PCI: aardvark: Set PIO_ADDR_LS correctly in advk_pcie_rd_conf()
  PCI: aardvark: Fix logic in advk_pcie_{rd,wr}_conf()
  ANDROID: binder: prevent transactions into own process.
  vfio: ccw: process ssch with interrupts disabled
  bfq-iosched: ensure to clear bic/bfqq pointers when preparing request
  scsi: sd: Defer spinning up drive while SANITIZE is in progress
  kobject: don't use WARN for registration failures
  mtd: rawnand: tango: Fix struct clk memory leak
  mtd: cfi: cmdset_0002: Do not allow read/write to suspend erase block.
  mtd: cfi: cmdset_0001: Workaround Micron Erase suspend bug.
  mtd: cfi: cmdset_0001: Do not allow read/write to suspend erase block.
  mtd: spi-nor: cadence-quadspi: Fix page fault kernel panic
  ALSA: hda/realtek - change the location for one of two front mics
  ALSA: hda/realtek - Update ALC255 depop optimize
  ALSA: hda/realtek - Add some fixes for ALC233
  ALSA: hda: Hardening for potential Spectre v1
  ALSA: seq: oss: Hardening for potential Spectre v1
  ALSA: seq: oss: Fix unbalanced use lock for synth MIDI device
  ALSA: core: Report audio_tstamp in snd_pcm_sync_ptr
  ALSA: pcm: Return negative delays from SNDRV_PCM_IOCTL_DELAY.
  ALSA: control: Hardening for potential Spectre v1
  ALSA: rme9652: Hardening for potential Spectre v1
  ALSA: hdspm: Hardening for potential Spectre v1
  ALSA: asihpi: Hardening for potential Spectre v1
  ALSA: opl3: Hardening for potential Spectre v1
  ALSA: hda - Skip jack and others for non-existing PCM streams
  ALSA: dice: fix error path to destroy initialized stream data
  ALSA: dice: fix OUI for TC group
  tty: Use __GFP_NOFAIL for tty_ldisc_get()
  tty: Avoid possible error pointer dereference at tty_ldisc_restore().
  tty: n_gsm: Fix DLCI handling for ADM mode if debug & 2 is not set
  tty: n_gsm: Fix long delays with control frame timeouts in ADM mode
  tty: Don't call panic() at tty_ldisc_init()
  drm/virtio: fix vq wait_event condition
  virtio_console: reset on out of memory
  virtio_console: mov

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

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

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

Title:
  Bionic update: upstream stable patchset 2018-06-26

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

Bug description:
  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()

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

-- 
Mailing list: https://launchpad.net/~kernel-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 Bionic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Fix Committed

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 1767181] Re: Upgrade to Bionic and USB audio devices no longer work

ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   andrei11513 F...m pulseaudio
 /dev/snd/pcmC0D0p:   andrei11513 F...m pulseaudio
 /dev/snd/controlC0:  andrei11513 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=6b91b055-5e50-43be-b4a7-754b9334f8ab
InstallationDate: Installed on 2017-12-26 (184 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
MachineType: Dell Inc. Inspiron 5570
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=d848d42f-7543-4f54-ba4b-ee642ebb50a1 ro amdgpu.dpm=0 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: Upgraded to bionic on 2018-06-10 (18 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
_MarkForUpload: True
dmi.bios.date: 09/08/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.4
dmi.board.name: 0DRPKR
dmi.board.vendor: Dell Inc.
dmi.board.version: X07
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0DRPKR:rvrX07:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.sys.vendor: Dell Inc.


** Tags added: apport-collected

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop'

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1767181/+attachment/5157553/+files/ProcCpuinfoMinimal.txt

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.

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

apport information

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

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpa

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

apport information

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

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1767181/+attachment/5157550/+files/Lspci.txt

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc

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

apport information

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

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/

[Kernel-packages] [Bug 1767181] Re: Upgrade to Bionic and USB audio devices no longer work

I have similar issue with a Logitech USB headset.  See attached apport
info in the comments above.

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

apport information

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

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun

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

apport information

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

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/

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

apport information

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

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

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage noti

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

apport information

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

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou

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

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1767181/+attachment/5157546/+files/AlsaInfo.txt

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu

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

apport information

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

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.ne

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

apport information

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

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Kernel-packages] [Bug 1778765] Re: Ubuntu 18.04 NVMe disks are not displayed on lsblk, kernel-bug-exists-upstream

2018-06-28 Thread Jun Kong

** Summary changed:

- Ubuntu 18.04 NVMe disks are not displayed on lsblk
+ Ubuntu 18.04 NVMe disks are not displayed on lsblk, 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/1778765

Title:
  Ubuntu 18.04 NVMe disks are not displayed on lsblk, kernel-bug-exists-
  upstream

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  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 1767181] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1767181/+attachment/5157560/+files/WifiSyslog.txt

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ub

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

apport information

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

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu

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

apport information

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

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

Title:
  Upgrade to Bionic and USB audio devices no longer work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use a Jabra Speak 510 USB audio device (speaker/mic) with my desktop
  for conference calls, hangouts, etc.

  Yesterday (and ever since I bought the device) I was able to use this
  device for audio output and input on Xenial.

  Today, after upgrading to Bionic, I am no longer able to use the
  device.

  Plugging it in shows that it's recognized correctly when plugging it into a 
USB3 port (via dmesg):
  [14066.244592] usb 3-2.4: new full-speed USB device number 7 using xhci_hcd
  [14066.365164] usb 3-2.4: New USB device found, idVendor=0b0e, idProduct=0420
  [14066.365170] usb 3-2.4: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14066.365174] usb 3-2.4: Product: Jabra SPEAK 510 USB
  [14066.365178] usb 3-2.4: SerialNumber: 745C4B24EDD7020A00
  [14133.075895] usb 3-2.1.4: USB disconnect, device number 5
  [14145.362837] usb 3-2.4: USB disconnect, device number 7
  [14194.218452] usb 3-2.1.3: new full-speed USB device number 8 using xhci_hcd
  [14194.338627] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14194.338632] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14194.338635] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14194.338637] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00
  [14240.079238] usb 3-2.1.3: USB disconnect, device number 8
  [14269.993176] usb 3-2.1.3: new full-speed USB device number 9 using xhci_hcd
  [14270.131688] usb 3-2.1.3: New USB device found, idVendor=0b0e, 
idProduct=0420
  [14270.131694] usb 3-2.1.3: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [14270.131698] usb 3-2.1.3: Product: Jabra SPEAK 510 USB
  [14270.131702] usb 3-2.1.3: SerialNumber: 745C4B24EDD7020A00

  And it appears on the USB bus:
  bladernr@galactica:~$ lsusb
  Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 004: ID 1050:0010 Yubico.com Yubikey
  Bus 003 Device 009: ID 0b0e:0420 GN Netcom Jabra SPEAK 510
  Bus 003 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 17f6:0860 Unicomp, Inc 
  Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  And when I open the sound settings (I am using Unity 7) the Jabra device 
appears as both an available input and output device.
  However, when I select it, and try a test sound, the output STILL comes out 
of the desktop's line-out and NOT the USB audio device.

  Likewise, on the Input tab, if I select the Jabra, no sound is
  detected when I speak.

  Thinking this might be because I'm using a USB hub, I disconnected the
  hub and plugged the device in directly to an onboard USB3 port but the
  problem persists.  The device appears as an available output and input
  source, but sound does not come out of it (it still comes out the
  line-out despite the fact I have selected the USB device) and no sound
  is detected when testing the input side.

  I also plugged in a USB webcam that has a built in microphone,  LIke
  the Jabra Speak 510, my USB webcam Microphone appears as an available
  input device and like the Jabra, no sound is detected when I select
  the webcam microphone.  USB audio seems to be completely inoperative
  on Bionic.

  Looking at the Sound Settings menu, I notice that the title changes
  with each device I choose, however it does NOT change when I choose
  the USB devices.  See attached screen shots for more info there.

  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: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Apr 26 15:24:56 2018
  InstallationDate: Installed on 2016-02-11 (805 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc

[Kernel-packages] [Bug 1779173] Re: Dell D6000 dock lacks multicast Ethernet functionality

2018-06-28 Thread Bug Watch Updater

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=200331.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2018-06-28T17:03:57+00:00 miguel wrote:

Created attachment 276977
[PATCH 1/2] Hook into usbnet_change_mtu respecting usbnet driver_info

Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However,
multicast Ethernet traffic is not processed making IPv6 not functional.
Other services, like mDNS used for LAN service discovery are also
hindered.

The actual reason is that CDC_NCM driver was not processing requests to
filter (admit) multicast traffic. I provide two patches to the linux
kernel that admit all Ethernet multicast traffic whenever a multicast
group is being joined.

The solution is not optimal, as it makes the system receive more traffic
than that strictly needed, but otherwise this only happens when the
computer is connected to a dock and thus is running on AC power. I
believe it is not worth the hassle to join only the requested groups.
This is the same that is done in the CDN_ETHER driver.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779173/comments/4

On 2018-06-28T17:05:07+00:00 miguel wrote:

Created attachment 276979
[PATCH 2/2] Admit multicast traffic

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779173/comments/5

On 2018-06-28T19:28:58+00:00 greg wrote:

On Thu, Jun 28, 2018 at 05:03:57PM +, bugzilla-dae...@bugzilla.kernel.org 
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=200331
> 
> Bug ID: 200331
>Summary: CDC NCM driver does not process multicast Ethernet
> traffic
>Product: Drivers
>Version: 2.5
> Kernel Version: 4.15

All USB bugs should be sent to the linux-...@vger.kernel.org mailing
list, and not entered into bugzilla.  Please bring this issue up there,
if it is still a problem in the latest kernel release.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779173/comments/6

** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1779173

Title:
  Dell D6000 dock lacks multicast Ethernet functionality

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However,
  multicast Ethernet traffic is not processed making IPv6 not
  functional. Other services, like mDNS used for LAN service discovery
  are also hindered.

  The actual reason is that CDC_NCM driver was not processing requests
  to filter (admit) multicast traffic. I provide two patches to the
  linux kernel that admit all Ethernet multicast traffic whenever a
  multicast group is being joined.

  The solution is not optimal, as it makes the system receive more
  traffic than that strictly needed, but otherwise this only happens
  when the computer is connected to a dock and thus is running on AC
  power. I believe it is not worth the hassle to join only the requested
  groups. This is the same that is done in the CDN_ETHER driver.

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

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

[Kernel-packages] [Bug 1759848] Re: Allow multiple mounts of zfs datasets

2018-06-28 Thread Brian Murray

Hello Colin, or anyone else affected,

Accepted zfs-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.6.5.6-0ubuntu24 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

Title:
  Allow multiple mounts of zfs datasets

Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  === SRU Justification, Xenial ==

  An attempt to mount an already mounted zfs dataset should return a new
  mount referencing the existing super block, but instead it returns an
  error. Operations such as bind mounts and unsharing mount namespaces
  create new mounts for the sb, which can cause operations to fail which
  involve unmounting and remounting the dataset.

  == Fix ==

  Backport of upstream fix https://trello.com/c/l89Ygj28/352-allow-
  multiple-mounts-of-zfs-datasets to allow multiple mounts

  This fix from Seth addresses this issue

  == Regression potential ==

  Like all backports, this has a potential to be incorrectly backported
  and break the ZFS mounting. However, any breakage should be picked up
  via the ZFS smoke tests that thoroughly exercise mounting/dismounting
  options.  At worst, the mounting won't work, but this has been tested,
  so I doubt this is a possibility.

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

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

[Kernel-packages] [Bug 1779241] [NEW] package linux-headers-3.13.0-143 3.13.0-143.192 failed to install/upgrade: não pode copiar dados extráidos para './usr/src/linux-headers-3.13.0-143/include/media/

2018-06-28 Thread Wallace Reis

Public bug reported:

my update gave error in several packages, and I can not and can not
update my ubunt 12.4 to the 16

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-headers-3.13.0-143 3.13.0-143.192
ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39
Uname: Linux 3.13.0-143-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
AptOrdering:
 linux-headers-3.13.0-143: Install
 linux-headers-3.13.0-143: Configure
 linux-headers-3.13.0-143-generic: Configure
 linux-headers-generic: Configure
 linux-generic: Configure
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  anderson   1875 F pulseaudio
Date: Thu Jun 28 11:51:14 2018
DpkgHistoryLog:
 Start-Date: 2018-06-28  11:50:57
 Commandline: apt-get install -f
 Install: linux-headers-3.13.0-143:i386 (3.13.0-143.192, automatic)
DuplicateSignature: package:linux-headers-3.13.0-143:3.13.0-143.192:não pode 
copiar dados extráidos para 
'./usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para 
'/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de 
ficheiro ou stream inesperado
ErrorMessage: não pode copiar dados extráidos para 
'./usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para 
'/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de 
ficheiro ou stream inesperado
HibernationDevice: RESUME=UUID=c88c53c8-7acf-443f-852d-b95b388a9d0e
InstallationDate: Installed on 2017-10-27 (244 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
MachineType: Acer Aspire 4739Z
PackageArchitecture: all
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-143-generic 
root=UUID=e90c1af9-730a-46ca-9a75-08496280e0f2 ro locale=pt_BR quiet splash 
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
SourcePackage: linux
Title: package linux-headers-3.13.0-143 3.13.0-143.192 failed to 
install/upgrade: não pode copiar dados extráidos para 
'./usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para 
'/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de 
ficheiro ou stream inesperado
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: V1.05
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: HMA_CP
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvrV1.05:bd05/30/2011:svnAcer:pnAspire4739Z:pvrV1.05:rvnAcer:rnHMA_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire 4739Z
dmi.product.version: V1.05
dmi.sys.vendor: Acer

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


** Tags: apport-package i386 trusty

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

Title:
  package linux-headers-3.13.0-143 3.13.0-143.192 failed to
  install/upgrade: não pode copiar dados extráidos para './usr/src
  /linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para '/usr/src
  /linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de
  ficheiro ou stream inesperado

Status in linux package in Ubuntu:
  New

Bug description:
  my update gave error in several packages, and I can not and can not
  update my ubunt 12.4 to the 16

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-headers-3.13.0-143 3.13.0-143.192
  ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-143-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  AptOrdering:
   linux-headers-3.13.0-143: Install
   linux-headers-3.13.0-143: Configure
   linux-headers-3.13.0-143-generic: Configure
   linux-headers-generic: Configure
   linux-generic: Configure
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anderson   1875 F pulseaudio
  Date: Thu Jun 28 11:51:14 2018
  DpkgHistoryLog:
   Start-Date: 2018-06-28  11:50:57
   Commandline: apt-get install -f
   Install: linux-headers-3.13.0-143:i386 (3.13.0-143.192, automatic)
  DuplicateSignature: package:linux-headers-3.13.0-143:3.13.0-143.192:não pode 
copiar dados extráidos para 
'./usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para 
'/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de 
ficheiro ou stream inesperado
  ErrorMessage: não pode copiar dados extráidos para 
'./usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para 
'/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de 
ficheiro ou stream inesperado
  HibernationDevice: RESUME=UUID=c88c53c8-7a

[Kernel-packages] [Bug 1779241] Re: package linux-headers-3.13.0-143 3.13.0-143.192 failed to install/upgrade: não pode copiar dados extráidos para './usr/src/linux-headers-3.13.0-143/include/media/s5

2018-06-28 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-headers-3.13.0-143 3.13.0-143.192 failed to
  install/upgrade: não pode copiar dados extráidos para './usr/src
  /linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para '/usr/src
  /linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de
  ficheiro ou stream inesperado

Status in linux package in Ubuntu:
  New

Bug description:
  my update gave error in several packages, and I can not and can not
  update my ubunt 12.4 to the 16

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-headers-3.13.0-143 3.13.0-143.192
  ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-143-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  AptOrdering:
   linux-headers-3.13.0-143: Install
   linux-headers-3.13.0-143: Configure
   linux-headers-3.13.0-143-generic: Configure
   linux-headers-generic: Configure
   linux-generic: Configure
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anderson   1875 F pulseaudio
  Date: Thu Jun 28 11:51:14 2018
  DpkgHistoryLog:
   Start-Date: 2018-06-28  11:50:57
   Commandline: apt-get install -f
   Install: linux-headers-3.13.0-143:i386 (3.13.0-143.192, automatic)
  DuplicateSignature: package:linux-headers-3.13.0-143:3.13.0-143.192:não pode 
copiar dados extráidos para 
'./usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para 
'/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de 
ficheiro ou stream inesperado
  ErrorMessage: não pode copiar dados extráidos para 
'./usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para 
'/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de 
ficheiro ou stream inesperado
  HibernationDevice: RESUME=UUID=c88c53c8-7acf-443f-852d-b95b388a9d0e
  InstallationDate: Installed on 2017-10-27 (244 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Acer Aspire 4739Z
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-143-generic 
root=UUID=e90c1af9-730a-46ca-9a75-08496280e0f2 ro locale=pt_BR quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
  SourcePackage: linux
  Title: package linux-headers-3.13.0-143 3.13.0-143.192 failed to 
install/upgrade: não pode copiar dados extráidos para 
'./usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h' para 
'/usr/src/linux-headers-3.13.0-143/include/media/s5k4ecgx.h.dpkg-new': fim de 
ficheiro ou stream inesperado
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: HMA_CP
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.05:bd05/30/2011:svnAcer:pnAspire4739Z:pvrV1.05:rvnAcer:rnHMA_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire 4739Z
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1778029] Re: Use "Medium power with Device Initiated PM" as default LPM policy for mobile SATA devices

2018-06-28 Thread Kai-Heng Feng

Only OEM systems with Ubuntu preloaded use linux-oem kernel. We have QA
to rigorously test systems before shipping, so it should be fine for
linux-oem users.

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

Title:
  Use "Medium power with Device Initiated PM" as default LPM policy for
  mobile SATA devices

Status in linux-oem package in Ubuntu:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  Intel CPU can't reach beyond Package C-State 3 (PC3). Drains lots of power.

  [Test]
  Check the value of 
/sys/devices/pci:00/:00:17.0/ata1/host0/scsi_host/host0/link_power_management_policy.

  It's med_power_with_dipm as default.
  Also check the powertop, it can reach PC8.

  [Fix]
  Introduce a new config to let AHCI pick med_power_with_dipm for mobile 
platforms.

  [Regression Potential]
  Medium. Some SATA devices are broken under med_power_with_dipm or min_power.
  Fortunately this is for -oem kernel only, so every SATA device gets tested 
before shipping to customers.

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

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

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