[Kernel-packages] [Bug 1768292] Re: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980

[John W. Galvin]

Followed the instructions in
https://wiki.ubuntu.com/Testing/EnableProposed to enable installing from
the proposed repository.  Used aptitude -t bionic-proposed to upgrade
the linux-headers-generic, linux-generic, linux-image-generic, and
linux-signed-generic packages.  This resulted in the following being
installed (per dpkg -l):

ii  linux-generic  4.15.0.23.24 
   amd64Complete Generic Linux kernel and headers
ii  linux-headers-4.15.0-234.15.0-23.25 
   all  Header files related to Linux kernel version 4.15.0
ii  linux-headers-4.15.0-23-generic4.15.0-23.25 
   amd64Linux kernel headers for version 4.15.0 on 64 bit x86 SMP
ii  linux-headers-generic  4.15.0.23.24 
   amd64Generic Linux kernel headers
ii  linux-image-4.15.0-23-generic  4.15.0-23.25 
   amd64Signed kernel image generic
ii  linux-image-generic4.15.0.23.24 
   amd64Generic Linux kernel image
ii  linux-modules-4.15.0-23-generic4.15.0-23.25 
   amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii  linux-modules-extra-4.15.0-23-generic  4.15.0-23.25 
   amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii  linux-signed-generic   4.15.0.23.24 
   amd64Complete Signed Generic Linux kernel and headers (dummy 
transitional package)

I shut down my laptop and powered on via battery (issue only arises on
battery power).  I selected the 4.15.0.23 kernel via GRUB and booted.
No issues observed.  Tested multiple times without issue.  I believe
this kernel fixes the issue.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Bionic: Intermittently sent to Emergency Mode on boot with unhandled
  kernel NULL pointer dereference at  0980

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

Bug description:
  ===SRU Justification===
  [Impact]
  When TBT ICM firmware is not running properly, it may crash the kernel.

  [Fix]
  Protect against cases when ICM is not set.

  [Test]
  User confirmed the additional patch works.

  [Regression Potential]
  Low. It adds a simple logic to avoid NULL dereference.

  ===Original Bug Report===

  Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop.
  Sometimes, at boot, the system goes into Emergency Mode.  In looking
  at journalctl -xb output, the following messages are logged:

  May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri 
Kosina
  May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on
  May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on
  May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered
  May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 
2005-2007 Rodolfo Giometti 
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI 
initialized, starting thunderbolt
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX 
ring 0 of size 10
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX 
ring 0 of size 10
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel 
created
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel 
starting...
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX 
ring 0
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling 
interrupt at register 0x38200 bit 0 (0x0 -> 0x1)
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX 
ring 0
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling 
interrupt at register 0x38200 bit 12 (0x1 -> 0x1001)
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM 
firmware
  May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer 
dereference at 0980
  May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30
  May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0
  May 01 10:05:04 galvin-T570 kernel: Oops:  [#1] SMP PTI
  May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core 
thunderbolt(+) wmi i2c_hid hid video
  May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not 
tainted 4.15.0-20-generic #21-Ubuntu
 

[Kernel-packages] [Bug 1772950] Update Released

[Steve Langasek]

The verification of the Stable Release Update for dkms has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  dkms key enrolled in mok, but dkms module fails to load

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  All Ubuntu users for whom Secure Boot is enabled.

  [Test cases]
  1) install dkms module (use virtualbox-dkms for example)
  2) Upgrade kernel (for example, install 4.15.0-22-generic on top of 
4.15.0-20-generic).
  3) Verify that the generated module for the new kernel (4.15.0-22-generic in 
this example) is built and signed by verifying that the file in 
/lib/modules/$kernel/updates/dkms/$module.ko ends in ~Module signature 
appended~:

  $ hexdump -Cv /lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko | tail 
-n 100
  [...]
  ~Module signature appended~

  4) Reboot
  5) modprobe -v the module.
  It should not respond "Required key not available", and should return with no 
error.
  6) Verify that dkms does not contain PKCS#7 errors.

  
  [Regression potential]
  Possible regressions involve failure to sign and/or be able to load modules 
after updates: failure to sign leading to a module being built but unsigned 
after a new kernel is installed or after a new DKMS module is installed, 
failure to load modules after reboot (usually caused by module being unsigned); 
failure to sign due to missing keys, signature key not being automatically 
slated for enrollment. All these potential regression scenarios present as 
failure to load a DKMS module after a reboot when it should be loaded 
successfully.

  ---

  At my last reboot, I was prompted to enable SecureBoot, so I did.

  When I booted, however, I noticed that the virtualbox service failed
  to start because it couldn't load its kernel module.  If I attempt the
  same thing, I see that there's an issue with keys:

  $ sudo modprobe vboxdrv
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available

  I do have keys enrolled; `mokutil --list-enrolled` produces
  http://paste.ubuntu.com/p/rntTQr5XJV/

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

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

[Kernel-packages] [Bug 1772950] Re: dkms key enrolled in mok, but dkms module fails to load

[Launchpad Bug Tracker]

This bug was fixed in the package dkms - 2.3-3ubuntu9.1

---
dkms (2.3-3ubuntu9.1) bionic; urgency=medium

  * 0009-Add-support-for-UEFI-Secure-Boot-validation-toggling.patch: move sign
code to dkms script itself, so it also applies on kernel upgrades.
(LP: #1772950)

 -- Mathieu Trudel-Lapierre   Wed, 23 May 2018
13:15:53 -0400

** Changed in: dkms (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  dkms key enrolled in mok, but dkms module fails to load

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  All Ubuntu users for whom Secure Boot is enabled.

  [Test cases]
  1) install dkms module (use virtualbox-dkms for example)
  2) Upgrade kernel (for example, install 4.15.0-22-generic on top of 
4.15.0-20-generic).
  3) Verify that the generated module for the new kernel (4.15.0-22-generic in 
this example) is built and signed by verifying that the file in 
/lib/modules/$kernel/updates/dkms/$module.ko ends in ~Module signature 
appended~:

  $ hexdump -Cv /lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko | tail 
-n 100
  [...]
  ~Module signature appended~

  4) Reboot
  5) modprobe -v the module.
  It should not respond "Required key not available", and should return with no 
error.
  6) Verify that dkms does not contain PKCS#7 errors.

  
  [Regression potential]
  Possible regressions involve failure to sign and/or be able to load modules 
after updates: failure to sign leading to a module being built but unsigned 
after a new kernel is installed or after a new DKMS module is installed, 
failure to load modules after reboot (usually caused by module being unsigned); 
failure to sign due to missing keys, signature key not being automatically 
slated for enrollment. All these potential regression scenarios present as 
failure to load a DKMS module after a reboot when it should be loaded 
successfully.

  ---

  At my last reboot, I was prompted to enable SecureBoot, so I did.

  When I booted, however, I noticed that the virtualbox service failed
  to start because it couldn't load its kernel module.  If I attempt the
  same thing, I see that there's an issue with keys:

  $ sudo modprobe vboxdrv
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available

  I do have keys enrolled; `mokutil --list-enrolled` produces
  http://paste.ubuntu.com/p/rntTQr5XJV/

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

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

[Kernel-packages] [Bug 1774225] [NEW] netns: unable to follow an interface that moves to another netns

[Nicolas Dichtel]

Public bug reported:

The following upstream patches are missing (v4.16):

6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a

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

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

Title:
  netns: unable to follow an interface that moves to another netns

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The following upstream patches are missing (v4.16):

  6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
  c36ac8e23073 ("dev: always advertise the new nsid when the netns iface 
changes")
  38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a

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

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

[Kernel-packages] [Bug 1774124] Re: linux: 4.13.0-45.50 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   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/1774124

Title:
  linux: 4.13.0-45.50 -proposed tracker

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

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

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

  backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)
  kernel-stable-phase-changed:Wednesday, 30. May 2018 09:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Joseph Salisbury]

I built Artful and Bionic test kernels with a revert of commit dc911f5bd8aa.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1773520

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

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

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

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

Bug description:
  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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

[Tom Reynolds]

The microcode updates AMD had announced https://www.amd.com/en/corporate
/security-updates are going to be availble to AMD customers "by
downloading BIOS updates provided by PC and server manufacturers and
motherboard providers" are now actually available as separate microcode
packages which can be loaded by the OS during early boot.

For now, the microcode has not undergone sufficient testing on Ubuntu's
end so it is only made available on the ubuntu-security-proposed PPA (so
far, this will change if it looks fine).

A changelog for the upstream (Debian) package is available at
https://launchpad.net/debian/+source/amd64-microcode/+changelog -
according to a member of the Ubuntu security team it primarily (not sure
if exclusively?) targets family 17h (Zen, so Ryzen, Epyc, Threadripper)
processors.

Note that Ubuntu 14.04 systems running Linux 3.13 require a kernel patch
for this microcode to work properly.

I do not know whether or not this microcode update provides mitigations
for the bug discussed here (it might have helped for AMD to state so),
but it is probably worth a try if your mainboard vendor has not provided
a recent enough BIOS upgrade (and your system remains unstable) or the
latest BIOS update you have just doesn't mitigate Spectre v2 in
hardware, yet.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 

[Kernel-packages] [Bug 1770231] Re: Expose arm64 CPU topology to userspace

[dann frazier]

** Description changed:

  [Impact]
  Applications, particularly those in the HPC domain (e.g. openmpi), can be 
optimized for the processor and cache topology. However, the ARM CPU topology 
isn't correctly exposed to userspace.
  
  [Fix]
  The ACPI 6.2 specification introduced a Processor Properties Topology Table 
(PPTT). This is what ARM server vendors are using to expose their topology. The 
linux kernel needs support for parsing this table, and exposing the parsed 
topology to userspace.
  
  [Test Case]
  A HiSilicon D06 without the fix. Note that it thinks I'm on a 24-socket 
system with 4 cores each. I'm not. I'm on a 2 socket system w/ 48 cores each. 
An HPC app that optimized for this (bogus) topology would therefore suffer a 
performance penalty.
  
  ubuntu@d06-1:~$ lscpu
  Architecture:aarch64
  Byte Order:  Little Endian
  CPU(s):  96
  On-line CPU(s) list: 0-95
  Thread(s) per core:  1
  Core(s) per socket:  4
  Socket(s):   24
  NUMA node(s):4
  Vendor ID:   0x48
  Model:   0
  Stepping:0x0
  BogoMIPS:200.00
  NUMA node0 CPU(s):   0-23
  NUMA node1 CPU(s):   24-47
  NUMA node2 CPU(s):   48-71
  NUMA node3 CPU(s):   72-95
  Flags:   fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid 
asimdrdm dcpop
  
  With the fix (and this is correct):
  ubuntu@d06-1:~$ lscpu
  Architecture:aarch64
  Byte Order:  Little Endian
  CPU(s):  96
  On-line CPU(s) list: 0-95
  Thread(s) per core:  1
  Core(s) per socket:  48
  Socket(s):   2
  NUMA node(s):4
  Vendor ID:   0x48
  Model:   0
  Stepping:0x0
  BogoMIPS:200.00
  L1d cache:   64K
  L1i cache:   64K
  L2 cache:512K
  L3 cache:32768K
  NUMA node0 CPU(s):   0-23
  NUMA node1 CPU(s):   24-47
  NUMA node2 CPU(s):   48-71
  NUMA node3 CPU(s):   72-95
  Flags:   fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid 
asimdrdm dcpop
  
  [Regression Risk]
  Here's a patch-by patch risk analysis of the changeset:
  
  0001-ACPICA-ACPI-6.2-Additional-PPTT-flags.patch
  Just adds new #defines. No functional change.
  
  0002-drivers-base-cacheinfo-move-cache_setup_of_node.patch
  Moves code down in a file. No functional change. (I double-checked that the 
moved code is the same).
  
  0003-drivers-base-cacheinfo-setup-DT-cache-properties-ear.patch
- The code this touches is all #ifdef CONFIG_OF, which only applies to the ARM 
& Power ports of Ubuntu. I've tested on ARM.
+ The code this touches is all #ifdef CONFIG_OF, which only applies to the ARM 
& Power ports of Ubuntu. I've tested on arm64 and regression tested on ppc64el 
(POWER9). POWER booted fine, and there was no change to lscpu output.
  
  0004-cacheinfo-rename-of_node-to-fw_token.patch
  Renames a variable, and changes it's type from "struct device_node *" to 
"void *". No functional change.
  
  0005-arm64-acpi-Create-arch-specific-cpu-to-acpi-id-helpe.patch
  Adds a new function (but doesn't use it yet).
  
  0006-ACPI-PPTT-Add-Processor-Properties-Topology-Table-pa.patch
  Adds new code that isn't called yet.
  
  0007-UBUNTU-Config-CONFIG_ACPI_PPTT-y.patch
  Configures on the new code.
  
  0008-ACPI-Enable-PPTT-support-on-ARM64.patch
  Kconfig/Makefile bits for the new code.
  
  0009-drivers-base-cacheinfo-Add-support-for-ACPI-based-fi.patch
  Finally, we call the new code during initialization, so let's go back and 
look at that code. The first thing it does is to check for the presence of a 
PPTT table before proceeding, so the regression risk to systems *without* a 
PPTT table is negligible. The PPTT table was introduced in the ACPI 6.2 
specification, which was released in May 2017. Regression risk should therefore 
be restricted to systems manufactured (or firmware updated) after that time 
that happened to include a PPTT table. I don't know of anyone other than ARM 
licensees doing this - but it's possible there are others. And, it's possible 
that there's a table out there that tickles a bug in the parsing code. Should 
that be the case, a hotfix would be to use an initrd to override/strip[*] the 
PPTT from the XSDT table until a suitable fix is put in place.
  
  0010-arm64-Add-support-for-ACPI-based-firmware-tables.patch
  0011-arm64-topology-rename-cluster_id.patch
  0012-arm64-topology-enable-ACPI-PPTT-based-CPU-topology.patch
  These patches only touch arm64 code. I explicitly tested on an arm64 server.
  
  0013-ACPI-Add-PPTT-to-injectable-table-list.patch
  Allows users to override the PPTT table. No change to default behavior.
  
+ 0014-arm64-topology-divorce-MC-scheduling-domain-from-cor.patch
+ Only touches arm64 code. I explicitly tested on an arm64 server.
+ 
  [*]
  https://www.kernel.org/doc/Documentation/acpi/initrd_table_override.txt

** Description changed:

  [Impact]
- Applications, particularly those in the HPC domain 

[Kernel-packages] [Bug 1774191] Re: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker

[Stefan Bader]

** Summary changed:

- linux-lts-trusty:  -proposed tracker
+ linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1773165] Card0.Codecs.codec.0.txt

[Ridsai]

apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1773165/+attachment/5146492/+files/Card0.Codecs.codec.0.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/1773165

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 

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

[Ridsai]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1773165/+attachment/5146491/+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/1773165

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root 

[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded

[Ridsai]

apport information

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

** Tags added: apport-collected uec-images

** Description changed:

  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial
  
  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0
  
  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded
  
  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  
  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module
  
  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...
  
  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0
  
  DKMS: add completed.
  
  Kernel preparation unnecessary for this kernel.  Skipping...
  
  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)
  
  DKMS: build completed.
  
  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/
  
  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/
  
  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/
  
  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/
  
  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/
  
  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/
  
  depmod
  
  DKMS: install completed.
  
  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch
  
  #lsmod status
  No modules are listing for openvswitch-datapath-dkms
  
  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.17
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
+ Card0.Amixer.info: Error: [Errno 2] No such file or directory
+ Card0.Amixer.values: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 16.04
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb:
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: Red Hat KVM
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 cirrusdrmfb
+ ProcKernelCmdLine: 

[Kernel-packages] [Bug 1773635] Re: AR3012 Bluetooth not start after an upgrade to 4.4.0-127

[Kai-Heng Feng]

Do you have the problem with latest mainline kernel?

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

Title:
  AR3012 Bluetooth not start after an upgrade to 4.4.0-127

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Atheros mixed WiFi+Bluetooth device which worked nice on a kernels 
prior to 4.4.0-127
  But unfortunately after last upgrade (from 4.4.0-124 to 4.4.0-127) bluetooth 
is unable to start - no bluetooth indicator appears in notifications tray and 
no device could be discovered or connected to via bluetooth.

  Tailing a syslog provides following lines, related to bluetooth:
  May 27 12:15:16 K43T kernel: [  228.102799] usbcore: registered new interface 
driver btusb
  May 27 12:15:16 K43T kernel: [  228.109562] Bluetooth: hci0: don't support 
firmware rome 0x1020200
  May 27 12:15:16 K43T systemd-udevd[4634]: Process '/bin/hciconfig hci0 up' 
failed with exit code 1.
  May 27 12:15:16 K43T kernel: [  228.112017] Bluetooth: hci0: don't support 
firmware rome 0x1020200

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-127-generic 4.4.0-127.153
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  insanedeveloper   1937 F pulseaudio
   /dev/snd/controlC0:  insanedeveloper   1937 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 27 12:33:42 2018
  HibernationDevice: RESUME=UUID=4a7e8ac6-783b-4a23-bfa9-8130cfef7945
  InstallationDate: Installed on 2015-11-28 (910 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: ASUSTeK Computer Inc. K43TK
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed 
root=UUID=7dbd7b42-e67f-4416-8f6d-6c918e744fb7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-127-generic N/A
   linux-backports-modules-4.4.0-127-generic  N/A
   linux-firmware 1.157.18
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-01-08 (503 days ago)
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 206
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K43TK
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr206:bd03/20/2012:svnASUSTeKComputerInc.:pnK43TK:pvr1.0:rvnASUSTeKComputerInc.:rnK43TK:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K43TK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Kernel-packages] [Bug 1774124] Re: linux: 4.13.0-45.50 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-artful

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)
  kernel-stable-phase-changed:Wednesday, 30. May 2018 09:01 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.13.0-45.50 -proposed tracker

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

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

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

  backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)
  kernel-stable-phase-changed:Wednesday, 30. May 2018 09:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1774190] Re: linux: 3.13.0-151.201 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-meta
   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/1774190

Title:
  linux: 3.13.0-151.201 -proposed tracker

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

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

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

  backports: bug 1774191 (linux-lts-trusty)
  derivatives:
  kernel-stable-phase-changed:Wednesday, 30. May 2018 14:31 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1752251] Re: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy

[Steve Langasek]

Yes, since the Ubuntu kernel still has the mcelog interface endless, the
mcelog package could be used in Ubuntu.  However, the interface is
marked deprecated and the package was subsequently removed from Debian
and then Ubuntu.  I don't see a reason to reintroduce this package in
sru, instead of users migrating to non-deprecated interfaces.

I might be willing to accept an sru if someone felt strongly about it.
But for now I don't intend to do any work on this.

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

** Changed in: mcelog (Ubuntu)
 Assignee: Steve Langasek (vorlon) => (unassigned)

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

Title:
  Missing mcelog userspace package in bionic - or maybe linux kernel
  config should disable mcelog_legacy

Status in linux package in Ubuntu:
  Confirmed
Status in mcelog package in Ubuntu:
  Confirmed

Bug description:
  There is no mcelog package in bionic.

  $ sudo apt install mcelog
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package mcelog is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source

  E: Package 'mcelog' has no installation candidate

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

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

[Kernel-packages] [Bug 1752251] Re: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy

[Steve Langasek]

Also if there's use in having this package around it might be worth
considering whether it could be packaged as a snap, which doesn't
require going through the sru process.

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

Title:
  Missing mcelog userspace package in bionic - or maybe linux kernel
  config should disable mcelog_legacy

Status in linux package in Ubuntu:
  Confirmed
Status in mcelog package in Ubuntu:
  Confirmed

Bug description:
  There is no mcelog package in bionic.

  $ sudo apt install mcelog
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package mcelog is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source

  E: Package 'mcelog' has no installation candidate

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

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

[Kernel-packages] [Bug 1766056] [NEW] in Kubuntu Bionic oem install, after installer finishes, it won't shut down to allow reboot

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

it flashes a message about updating microcode, will not start a virtual
term, and must be shut down with the power button.

Otherwise the install seems successful, although I've not completed the
second reboot called for yet.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.9
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Apr 22 00:20:13 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/kubuntu.seed 
boot=casper only-ubiquity quiet splash oem-config/enable=true ---
InstallationDate: Installed on 2018-04-22 (0 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic iso-testing ubiquity-18.04.9
-- 
in Kubuntu Bionic oem install, after installer finishes, it won't shut down to 
allow reboot
https://bugs.launchpad.net/bugs/1766056
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 1766056] Re: in Kubuntu Bionic oem install, after installer finishes, it won't shut down to allow reboot

[Phillip Susi]

If you are unable to install the new microcode that may be a kernel
problem.  Certainly doesn't have anything to do with ubiquity.


** Package changed: ubiquity (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/1766056

Title:
  in Kubuntu Bionic oem install, after installer finishes, it won't shut
  down to allow reboot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  it flashes a message about updating microcode, will not start a
  virtual term, and must be shut down with the power button.

  Otherwise the install seems successful, although I've not completed
  the second reboot called for yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.9
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Apr 22 00:20:13 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/kubuntu.seed boot=casper only-ubiquity quiet splash 
oem-config/enable=true ---
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180421.1)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1774191] Re: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1774190
  phase: Packaging
+ kernel-stable-phase-changed:Wednesday, 30. May 2018 15:32 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1774190
- phase: Packaging
- kernel-stable-phase-changed:Wednesday, 30. May 2018 15:32 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1774124] Re: linux: 4.13.0-45.50 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.13.0-45.50 -proposed tracker

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

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

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

  backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)
  kernel-stable-phase-changed:Wednesday, 30. May 2018 09:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1774225

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

Title:
  netns: unable to follow an interface that moves to another netns

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The following upstream patches are missing (v4.16):

  6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
  c36ac8e23073 ("dev: always advertise the new nsid when the netns iface 
changes")
  38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a

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

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

[Kernel-packages] [Bug 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu

[Stefan Bader]

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

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

Title:
  need to ensure microcode updates are available to all bare-metal
  installs of Ubuntu

Status in linux-meta package in Ubuntu:
  Triaged
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-hwe-edge package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  Fix Released
Status in linux-meta-oem package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta source package in Trusty:
  Fix Released
Status in linux-meta source package in Xenial:
  Fix Released
Status in linux-meta-hwe source package in Xenial:
  Fix Released
Status in linux-meta-hwe-edge source package in Xenial:
  Fix Released
Status in linux-meta-lts-xenial source package in Xenial:
  Fix Committed
Status in linux-meta-oem source package in Xenial:
  Fix Released
Status in linux-meta source package in Zesty:
  Invalid
Status in linux-meta source package in Artful:
  Fix Released
Status in linux-meta source package in Bionic:
  Fix Committed

Bug description:
  From time to time, CPU vendors release updates to microcode that can
  be loaded into the CPU from the OS.  For x86, we have these updates
  available in the archive as amd64-microcode and intel-microcode.

  Sometimes, these microcode updates have addressed security issues with
  the CPU.  They almost certainly will again in the future.

  We should ensure that all users of Ubuntu on baremetal x86 receive
  these security updates, and have them applied to the CPU in early boot
  where at all feasible.

  Because these are hardware-dependent packages which we don't want to
  install except on baremetal (so: not in VMs or containers), the
  logical place to pull them into the system is via the kernel, so that
  only the kernel baremetal flavors pull them in.  This is analogous to
  linux-firmware, which is already a dependency of the linux-
  image-{lowlatency,generic} metapackages, and whose contents are
  applied to the hardware by the kernel similar to microcode.

  So, please update the linux-image-{lowlatency,generic} metapackages to
  add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
  and the corresponding hwe metapackages also.

  Please time this change to coincide with the next updates of the
  microcode packages in the archive.

  I believe we will also need to promote the *-microcode packages to
  main from restricted as part of this (again, by analogy with linux-
  firmware).

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

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

[Kernel-packages] [Bug 1660277] Re: AV Reciever (Marantz NR1506) pairs but won't connect (Resource temporarily unavailable)

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  AV Reciever (Marantz NR1506) pairs but won't connect (Resource
  temporarily unavailable)

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I am able to pair with my AV Reciever, but it won't connect.
  Pulseaudio bluetooth modules are installed and loaded. Tried
  connecting via hcitool and bluetoothctl, always the same error.
  Attached bluetoothd verbose logfile.

  Package / System info:

  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  $ apt-cache policy bluez
  bluez:
Installiert:   5.41-0ubuntu3

  $ apt-cache policy bluetooth
  bluetooth:
Installiert:   5.41-0ubuntu3

  $ apt-cache policy pulseaudio
  pulseaudio:
Installiert:   1:9.0-2ubuntu2.1

  $ apt-cache policy pulseaudio-module-bluetooth 
  pulseaudio-module-bluetooth:
Installiert:   1:9.0-2ubuntu2.1

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

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

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

[Joseph Salisbury]

** Tags removed: kernel-key
** Tags added: kernel-da-key

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

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

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

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

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

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

[Kernel-packages] [Bug 1774126] Re: linux-oem: 4.13.0-1030.33 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1774124
  phase: Uploaded

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04

[Joseph Salisbury]

The following patch was not applied to Bionic as of yet:

bf316c78517d ("scsi: lpfc: Fix WQ/CQ creation for older asic's.")

So are you saying we should first apply commit bf316c78517d, then patch
4/6 from comment #10?

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

Title:
  Lancer A0 Asic HBA's won't boot with 18.04

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

Bug description:
  
  We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.   

  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.

  We'll leave it up to Canonical to decide whether they want to pull
  this in this single patch to an 18.04 subsequent update.

  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
  Resolution: new lpfc driver patch update. 

  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111

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

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

[Kernel-packages] [Bug 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.13.0-1019.23 -proposed tracker

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

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

** 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) => Khaled El 
Mously (kmously)

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1766056] Re: in Kubuntu Bionic oem install, after installer finishes, it won't shut down to allow reboot

[Joseph Salisbury]

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

Title:
  in Kubuntu Bionic oem install, after installer finishes, it won't shut
  down to allow reboot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  it flashes a message about updating microcode, will not start a
  virtual term, and must be shut down with the power button.

  Otherwise the install seems successful, although I've not completed
  the second reboot called for yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.9
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Apr 22 00:20:13 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/kubuntu.seed boot=casper only-ubiquity quiet splash 
oem-config/enable=true ---
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180421.1)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1774191] Re: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1774190
  phase: Uploaded

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

Title:
  linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

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

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

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

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

[Priscila]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1773715/+attachment/5146644/+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/1773715

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Priscila]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1773715/+attachment/5146652/+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/1773715

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Priscila]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1773715/+attachment/5146643/+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/1773715

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Priscila]

apport information

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

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Priscila]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1773715/+attachment/5146650/+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/1773715

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1761646] Re: Can't mount kvm image file on new kernel of 16.04(linux 4.4.0-119)

[LouAlbano]

I am also seeing this behaviour on Ubuntu 16.04, linux-
image-4.4.0-127-generic.

Swapping to kernel 4.13.0-43-generic solved it here too.

Steps:

$ qemu-img create -b example.qcow -f qcow2 /run/shm/temp1.qcow2

$ qemu-nbd -c /dev/nbd1 /run/shm/temp1.qcow2

$ mkdir /tmp/mnt1

$ sudo /bin/mount /dev/nbd1p2 /tmp/mnt1

mount: special device /dev/nbd1p2 does not exist

I can do whatever other diag is needed, please let me know how I can
help.

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

Title:
  Can't mount kvm image file on  new kernel of 16.04(linux 4.4.0-119)

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

Bug description:
  When I use 4.4.0-62-generic　kernel, I can mount kvm image file.
  But when I use 4.4.0-116-generic or 119　kernel, I can't mount the kvm image 
file.
  Is there some way to mount the kvm image file on 4.4.0-116-generic later 
kernel?

  - release

  root@ofaci1:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.4 LTS
  Release:16.04
  Codename:   xenial
  root@ofaci1:~#

  
  - packages

  root@ofaci1:~# dpkg -l | egrep "qemu|mount|linux-image-4.4.0-11"
  ii  cgroupfs-mount  1.2   
 all  Light-weight package to set up cgroupfs mounts
  ii  ipxe-qemu   1.0.0+git-20150424.a25a16d-1ubuntu1.2 
 all  PXE boot firmware - ROM images for qemu
  ii  libmount1:amd64 2.27.1-6ubuntu3.4 
 amd64device mounting library
  ii  linux-image-4.4.0-116-generic   4.4.0-116.140 
 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP
  ii  linux-image-4.4.0-119-generic   4.4.0-119.143 
 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP
  ii  mount   2.27.1-6ubuntu3.4 
 amd64tools for mounting and manipulating filesystems
  ii  qemu-block-extra:amd64  1:2.5+dfsg-5ubuntu10.24   
 amd64extra block backend modules for qemu-system and qemu-utils
  ii  qemu-kvm1:2.5+dfsg-5ubuntu10.24   
 amd64QEMU Full virtualization
  ii  qemu-system-common  1:2.5+dfsg-5ubuntu10.24   
 amd64QEMU full system emulation binaries (common files)
  ii  qemu-system-x86 1:2.5+dfsg-5ubuntu10.24   
 amd64QEMU full system emulation binaries (x86)
  ii  qemu-utils  1:2.5+dfsg-5ubuntu10.24   
 amd64QEMU utilities
  root@ofaci1:~#

  
  - Use 4.4.0-62-generic

  root@ofaci1:~# uname -a
  Linux ofaci1 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  root@ofaci1:~# qemu-nbd --connect /dev/nbd1 /opt/ci-pool/slave1.qcow2
  root@ofaci1:~# fdisk /dev/nbd1

  Welcome to fdisk (util-linux 2.27.1).
  Changes will remain in memory only, until you decide to write them.
  Be careful before using the write command.

  
  Command (m for help): p
  Disk /dev/nbd1: 40 GiB, 42949672960 bytes, 83886080 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x000dfd65

  Device  Boot   Start  End  Sectors  Size Id Type
  /dev/nbd1p1 2048  3905535  3903488  1.9G 82 Linux swap / Solaris
  /dev/nbd1p2 *3905536 83884031 79978496 38.1G 83 Linux

  Command (m for help): q

  root@ofaci1:~# mount /dev/nbd1p2 /mnt/d1
  root@ofaci1:~# ls /mnt/d1
  bin   etc initrd.img.old  lost+found  opt   run   sys  var
  boot  homelib media   proc  sbin  tmp  vmlinuz
  dev   initrd.img  lib64   mnt root  srv   usr  vmlinuz.old
  root@ofaci1:~# umount /mnt/d1

  
  - Use 4.4.0-119-generic

  root@ofaci1:~# uname -a
  Linux ofaci1 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  root@ofaci1:~# qemu-nbd --connect /dev/nbd1 /opt/ci-pool/slave1.qcow2
  root@ofaci1:~# echo $?
  0
  root@ofaci1:~# fdisk /dev/nbd1

  Welcome to fdisk (util-linux 2.27.1).
  Changes will remain in memory only, until you decide to write them.
  Be careful before using the write command.

  
  Command (m for help): p
  Disk /dev/nbd1: 40 GiB, 42949672960 bytes, 83886080 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x000dfd65

  Device  Boot   Start  End  Sectors  Size Id Type
  /dev/nbd1p1 2048 

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

[Priscila]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1773715/+attachment/5146653/+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/1773715

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Priscila]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1773715/+attachment/5146646/+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/1773715

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Priscila]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1773715/+attachment/5146651/+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/1773715

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Priscila]

apport information

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

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Priscila]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1773715/+attachment/5146642/+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/1773715

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1773715] Re: DVI port recognition of dockstation does not work from upgrade to 18.04

[Priscila]

apport information

** Tags added: apport-collected

** Description changed:

  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en el
  dockstation para un segundo monitor, esto paso deszpues de hacer upgrade
  a la version 18.04.
  
  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  
  
  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  pr 1736 F pulseaudio
+  /dev/snd/controlC0:  pr 1736 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-12-14 (166 days ago)
+ InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ MachineType: Dell Inc. Latitude E6420
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
+ 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
+ Tags:  bionic
+ Uname: Linux 4.15.0-22-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
+ UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/14/2013
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A21
+ dmi.board.name: 038C0K
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
+ dmi.product.name: Latitude E6420
+ dmi.product.version: 01
+ dmi.sys.vendor: Dell Inc.

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

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.99

[Kernel-packages] [Bug 1773715] WifiSyslog.txt

[Priscila]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1773715/+attachment/5146655/+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/1773715

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Priscila]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1773715/+attachment/5146647/+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/1773715

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1773715] Re: DVI port recognition of dockstation does not work from upgrade to 18.04

[Priscila]

Hello Ubuntu Kernel Bot (ubuntu-kernel-bot).

I ran the command in my console and it gives me a series of errors,
look:

As a normal user:

pr @ pr: ~ $ apport-collect 1773715
The authorization page:
  
(https://launchpad.net/+authorize-token?oauth_token=0ZGN2tM1Bp1WjHGKkHkP_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision ...
[3366: 3405: 0530 / 144603.637890: ERROR: browser_gpu_channel_host_factory.cc 
(121)] Failed to launch GPU process.
Created new window in existing browser session.
dpkg-query: no packages found matching linux

And give Lauchpad permission for an hour, is that enough?

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

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

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

[Priscila]

apport information

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

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[Priscila]

apport information

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

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

Title:
  DVI port recognition of dockstation does not work from upgrade to
  18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Mi laptop Dell E6440 no reconoce que tiene conectado un cable DVI en
  el dockstation para un segundo monitor, esto paso deszpues de hacer
  upgrade a la version 18.04.

  root@pr:/home/pr# xrandr
  Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
  LVDS-1 connected 1280x720+0+0 (normal left inverted right x axis y axis) 
309mm x 174mm
 1366x768  60.05 +  40.31  
 1360x768  59.8059.96  
 1280x720  60.0059.9959.86*   59.74  
 1024x768  60.0460.00  
 960x720   60.00  
 928x696   60.05  
 896x672   60.01  
 1024x576  59.9559.9659.9059.82  
 960x600   59.9360.00  
 960x540   59.9659.9959.6359.82  
 800x600   60.0060.3256.25  
 840x525   60.0159.88  
 864x486   59.9259.57  
 800x512   60.17  
 700x525   59.98  
 800x450   59.9559.82  
 640x512   60.02  
 720x450   59.89  
 700x450   59.9659.88  
 640x480   60.0059.94  
 720x405   59.5158.99  
 684x384   59.8859.85  
 680x384   59.8059.96  
 640x400   59.8859.98  
 576x432   60.06  
 640x360   59.8659.8359.8459.32  
 512x384   60.00  
 512x288   60.0059.92  
 480x270   59.6359.82  
 400x300   60.3256.34  
 432x243   59.9259.57  
 320x240   60.05  
 360x202   59.5159.13  
 320x180   59.8459.32  
  VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 
376mm x 301mm
 1280x1024 60.02*+  75.02  
 1024x768  75.0360.00  
 800x600   75.0060.32  
 640x480   75.0059.94  
 720x400   70.08  

  root@pr:/home/pr# xrandr --addmode DVI-1 1280x1024_70.00
  xrandr: cannot find output "DVI-1"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sun May 27 18:50:51 2018
  InstallationDate: Installed on 2017-12-14 (164 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (11 days ago)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pr 1736 F pulseaudio
   /dev/snd/controlC0:  pr 1736 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-14 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude E6420
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=8526d01d-3124-46c5-9d7e-60e0b8ff6fce ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (13 days ago)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 038C0K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn038C0K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

[bugproxy]

--- Comment From cdead...@us.ibm.com 2018-05-30 17:35 EDT---
 State: Working by: dlshaw on 30 May 2018 16:24:44 

#=#=#=# David L. Shaw (dls...@us.ibm.com) - 2018-05-30 16:24:41 (CDT) -
POWER Firmware #=#=#=#

I think I installed this test kernel correctly on w34's OS 
(w34L.aus.stglabs.ibm.com). Let me know if I did something wrong and need to 
fix it.
Before installing this test kernel it had Ubuntu 18.04 (Bionic) kernel: 
4.15.0-22-generic

Ran the following to install test kernel:
root@w34L:~/SW430227# ls -lt
total 48220
-rw-r--r-- 1 root root 31438592 May 29 11:14 
linux-modules-extra-4.15.0-23-generic_4.15.0-23.26~lp1773964_ppc64el.deb
-rw-r--r-- 1 root root  6152468 May 29 11:14 
linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26~lp1773964_ppc64el.deb
-rw-r--r-- 1 root root 11767420 May 29 11:14 
linux-modules-4.15.0-23-generic_4.15.0-23.26~lp1773964_ppc64el.deb

root@w34L:~/SW430227# dpkg -i *.deb
Selecting previously unselected package linux-image-unsigned-4.15.0-23-generic.
(Reading database ... 175537 files and directories currently installed.)
Preparing to unpack 
linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26~lp1773964_ppc64el.deb ...
Unpacking linux-image-unsigned-4.15.0-23-generic (4.15.0-23.26~lp1773964) ...
Selecting previously unselected package linux-modules-4.15.0-23-generic.
Preparing to unpack 
linux-modules-4.15.0-23-generic_4.15.0-23.26~lp1773964_ppc64el.deb ...
Unpacking linux-modules-4.15.0-23-generic (4.15.0-23.26~lp1773964) ...
Selecting previously unselected package linux-modules-extra-4.15.0-23-generic.
Preparing to unpack 
linux-modules-extra-4.15.0-23-generic_4.15.0-23.26~lp1773964_ppc64el.deb ...
Unpacking linux-modules-extra-4.15.0-23-generic (4.15.0-23.26~lp1773964) ...
Setting up linux-modules-4.15.0-23-generic (4.15.0-23.26~lp1773964) ...
Setting up linux-image-unsigned-4.15.0-23-generic (4.15.0-23.26~lp1773964) ...
I: /boot/vmlinux.old is now a symlink to vmlinux-4.15.0-22-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-4.15.0-22-generic
I: /boot/vmlinux is now a symlink to vmlinux-4.15.0-23-generic
I: /boot/initrd.img is now a symlink to initrd.img-4.15.0-23-generic
Setting up linux-modules-extra-4.15.0-23-generic (4.15.0-23.26~lp1773964) ...
Processing triggers for linux-image-unsigned-4.15.0-23-generic 
(4.15.0-23.26~lp1773964) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-23-generic
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinux-4.15.0-23-generic
Found initrd image: /boot/initrd.img-4.15.0-23-generic
Found linux image: /boot/vmlinux-4.15.0-22-generic
Found initrd image: /boot/initrd.img-4.15.0-22-generic
Found linux image: /boot/vmlinux-4.15.0-20-generic
Found initrd image: /boot/initrd.img-4.15.0-20-generic
Found linux image: /boot/vmlinux-4.15.0-15-generic
Found initrd image: /boot/initrd.img-4.15.0-15-generic
Found linux image: /boot/vmlinux-4.15.0-13-generic
Found initrd image: /boot/initrd.img-4.15.0-13-generic
done

Rebooted the system and the new kernel is:
Linux w34L 4.15.0-23-generic #26~lp1773964 SMP Tue May 29 16:03:09 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

#=#=#=# end of 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/1773964

Title:
  IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls
  on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

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

Bug description:
  == Comment: #0 - Application Cdeadmin <> - 2018-05-22 09:36:12 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-05-22 09:36:14 ==
   State: Open by: swanman on 22 May 2018 09:17:33 

  Both w34 and wsbmc016 are stopped on this failure, where we get hung
  up on the following FFDC gathering step in the OS:

  #(CDT) 2018/05/22 05:07:19.398218 - 0.211662 - Issuing: OS Execute Command 
ppc64_cpu --frequency ignore_err=1
  #(CDT) 2018/05/22 05:07:19.437808 - 0.024108 - Issuing: ppc64_cpu --frequency 

  , and the last console output shows:
  # tail -200 /var/log/obmc-console.log 
  s this GP) idle=82a/140/0 softirq=2689/2689 fqs=241989 
  [13668.719850]  (detected by 3, t=3075620 jiffies, g=30289, c=30288, q=796881)
  [13732.630691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13732.630727]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=242996 
  [13732.630757]  (detected by 3, t=3091597 jiffies, g=30289, c=30288, q=799822)
  [13795.649568] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13795.649597]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=243942 
  

[Kernel-packages] [Bug 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"

[Andrew Reis]

Also confirmed on 4.15.0-22:

user@host:~$ uname -a
Linux host 4.15.0-22-generic #24~16.04.1-Ubuntu SMP Fri May 18 09:46:31 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
user@host:~$ dmesg | tail
[9.579718] new mount options do not match the existing superblock, will be 
ignored
[9.781330] new mount options do not match the existing superblock, will be 
ignored
[9.957734] TCP: eth0: Driver has suspect GRO implementation, TCP 
performance may be compromised.
[   10.468800] FS-Cache: Loaded
[   10.528082] FS-Cache: Netfs 'cifs' registered for caching
[   10.528179] Key type cifs.spnego registered
[   10.528182] Key type cifs.idmap registered
[   10.910445] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[   10.911089] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[   10.911723] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5

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

Title:
  Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in
  smb2_get_dfs_refer rc=-2"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 17.10 artful
  Kernel: x86_64 Linux 4.13.0-32.35-generic
  cifs-utils 2:6.7-1
  smbclient  2:4.6.7+dfsg-1ubuntu3.1

  Mounting an SMB share with
  
sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777

  in /etc/fstab gives the error: "CIFS VFS: ioctl error in
  smb2_get_dfs_refer rc=-2" in dmesg.

  Shares mounted this way are readable, but writing data to them (or using 
programs such as EasyTAG to write to them) ultimately fails. This bug did not 
occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the 
error, but this is a haphazard fix as SMB v3.0 carries many security features 
with it not avaliable in SMB 1.0.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago)
  UserGroups: libvirt libvirtd sudo wireshark
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-E/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  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.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"

[Andrew Reis]

I can also confirm on Xenial running 4.15.0-13:
user@host:~$ dmesg | tail
[ 1331.150999] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1331.197478] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1331.245486] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1631.292647] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1631.335005] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1631.374513] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1931.420138] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1931.467038] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[ 1931.506586] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5

user@host:~$ uname -a
Linux host 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:04:59 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

user@host:~$ mount -l | grep cifs
//server/share1 on /var/repositories.asp/staging/share1 type cifs 
(rw,relatime,vers=3.02,cache=strict,username=***,domain=***,uid=59948,forceuid,gid=33,forcegid,addr=1.1.1.1,file_mode=0664,dir_mode=0775,nocase,soft,nounix,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,_netdev)
//server/share2 on /var/repositories.asp/staging/share2 type cifs 
(rw,relatime,vers=3.02,cache=strict,username=***,domain=***,uid=59948,forceuid,gid=33,forcegid,addr=1.1.1.1,file_mode=0664,dir_mode=0775,nocase,soft,nounix,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,_netdev)
//server/share3 on /var/repositories.asp/staging/share3 type cifs 
(rw,relatime,vers=3.02,cache=strict,username=***,domain=***,uid=59948,forceuid,gid=33,forcegid,addr=1.1.1.1,file_mode=0664,dir_mode=0775,nocase,soft,nounix,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,_netdev)

names, usernames, domains redacted for privacy.

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

Title:
  Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in
  smb2_get_dfs_refer rc=-2"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 17.10 artful
  Kernel: x86_64 Linux 4.13.0-32.35-generic
  cifs-utils 2:6.7-1
  smbclient  2:4.6.7+dfsg-1ubuntu3.1

  Mounting an SMB share with
  
sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777

  in /etc/fstab gives the error: "CIFS VFS: ioctl error in
  smb2_get_dfs_refer rc=-2" in dmesg.

  Shares mounted this way are readable, but writing data to them (or using 
programs such as EasyTAG to write to them) ultimately fails. This bug did not 
occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the 
error, but this is a haphazard fix as SMB v3.0 carries many security features 
with it not avaliable in SMB 1.0.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: ASUS All Series
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago)
  UserGroups: libvirt libvirtd sudo wireshark
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-E/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  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.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1774282] [NEW] Bluetooth adapter not recognized

[Pedro Zuppelli]

Public bug reported:

I have tried with both ubuntu 16.04 and today with 18.04 and the problem 
persists. I had the blueman installed and nothing works. 
On windows it works fine, so the adapter is not the issue.

piero@piero-dev:/var/log$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04


Ubuntu Software 3.28.1

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-22-generic 4.15.0-22.24
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 30 19:23:41 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-10-17 (224 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: linux-signed
UpgradeStatus: Upgraded to bionic on 2018-05-30 (0 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Bluetooth adapter not recognized

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I have tried with both ubuntu 16.04 and today with 18.04 and the problem 
persists. I had the blueman installed and nothing works. 
  On windows it works fine, so the adapter is not the issue.

  piero@piero-dev:/var/log$ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  Ubuntu Software 3.28.1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 19:23:41 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-17 (224 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-30 (0 days ago)

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

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

[Kernel-packages] [Bug 1774306] [NEW] enable mic-mute hotkey and led on Lenovo M820z and M920z

[Hui Wang]

Public bug reported:

Steps:
1. Installed system and log in.
2. Press the Microphone mute key.

Actual result:
Microphone mute key and Microphone LED doesn't work at all.

Expected result:
Microphone mute key and Microphone LED work should be fine.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: Incomplete


** Tags: originate-from-1773297 sutton

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

** Tags added: originate-from-1773297 sutton

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

Title:
  enable mic-mute hotkey and led on Lenovo M820z and M920z

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

Bug description:
  Steps:
  1. Installed system and log in.
  2. Press the Microphone mute key.

  Actual result:
  Microphone mute key and Microphone LED doesn't work at all.

  Expected result:
  Microphone mute key and Microphone LED work should be fine.

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

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

[Kernel-packages] [Bug 1774190] Re: linux: 3.13.0-151.201 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1774191 (linux-lts-trusty)
  derivatives:
  kernel-stable-phase-changed:Wednesday, 30. May 2018 14:31 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 3.13.0-151.201 -proposed tracker

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

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

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

  backports: bug 1774191 (linux-lts-trusty)
  derivatives:
  kernel-stable-phase-changed:Wednesday, 30. May 2018 14:31 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1774191] Re: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-precise

** Tags added: block-proposed

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

Title:
  linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  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:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1773964] Re: IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

[Joseph Salisbury]

It looks like you booted into the correct test kernel.  Did it resolve
the bug?

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

Title:
  IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls
  on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

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

Bug description:
  == Comment: #0 - Application Cdeadmin <> - 2018-05-22 09:36:12 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-05-22 09:36:14 ==
   State: Open by: swanman on 22 May 2018 09:17:33 

  Both w34 and wsbmc016 are stopped on this failure, where we get hung
  up on the following FFDC gathering step in the OS:

  #(CDT) 2018/05/22 05:07:19.398218 - 0.211662 - Issuing: OS Execute Command 
ppc64_cpu --frequency ignore_err=1
  #(CDT) 2018/05/22 05:07:19.437808 - 0.024108 - Issuing: ppc64_cpu --frequency 

  , and the last console output shows:
  # tail -200 /var/log/obmc-console.log 
  s this GP) idle=82a/140/0 softirq=2689/2689 fqs=241989 
  [13668.719850]  (detected by 3, t=3075620 jiffies, g=30289, c=30288, q=796881)
  [13732.630691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13732.630727]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=242996 
  [13732.630757]  (detected by 3, t=3091597 jiffies, g=30289, c=30288, q=799822)
  [13795.649568] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13795.649597]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=243942 
  [13795.649631]  (detected by 7, t=3107351 jiffies, g=30289, c=30288, q=802916)
  [13860.140483] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13860.140516]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=244940 
  [13860.140557]  (detected by 3, t=3123473 jiffies, g=30289, c=30288, q=806646)
  [13924.731404] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13924.731438]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=245874 
  [13924.731484]  (detected by 3, t=3139620 jiffies, g=30289, c=30288, q=809909)
  [13988.642290] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13988.642321]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=246892 
  [13988.642362]  (detected by 3, t=3155596 jiffies, g=30289, c=30288, q=813048)
  [14052.661176] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14052.661211]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=247857 
  [14052.661266]  (detected by 3, t=3171600 jiffies, g=30289, c=30288, q=816185)
  [14115.680024] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14115.680051]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=248819 
  [14115.680085]  (detected by 4, t=3187355 jiffies, g=30289, c=30288, q=819190)
  [14180.154911] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14180.154945]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=249833 
  [14180.154986]  (detected by 132, t=3203473 jiffies, g=30289, c=30288, 
q=822138)
  [14244.968067]I F: Ne talls onCPUs/tasks
  [14244669838]   75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=2[14244.669944]  (detected by 3, t=3219600 jiffies, 
g=30289, c=30288, q=825384)
  [14308.748680] Id detected stalls on CPUs/tasks:
  [14308.748719]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=251755 
  [14308.748755]  (detected by 3, t=3235620 jiffies, g=30289, c=30288, q=828445)
  [14333.081775] Watchdog CPU:132 Hard LOCKUP
  [14344.750295] Watchdog CPU:132 became unstuck
  [14372.735558] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14372.735587]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=252722 
  [14372.735611]  (detected by 6, t=3251616 jiffies, g=30289, c=30288, q=831375)
  [14435.910193] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14435.910219]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=253675 
  [14435.910253]  (detected by 3, t=3267409 jiffies, g=30289, c=30288, q=834375)
  [14500.167195] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14500.167230]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=254601 
  [14500.167273]  (detected by 134, t=3283473 jiffies, g=30289, c=30288, 
q=837600)
  [14564.664395] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14564.664427]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=255493 
  [14564.664470]  (detected by 3, t=3299596 jiffies, g=30289, c=30288, q=840539)
  [14628.665755] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14628.665790]  75-: (5904 ticks this 

[Kernel-packages] [Bug 1660277] Re: AV Reciever (Marantz NR1506) pairs but won't connect (Resource temporarily unavailable)

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


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

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

Title:
  AV Reciever (Marantz NR1506) pairs but won't connect (Resource
  temporarily unavailable)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am able to pair with my AV Reciever, but it won't connect.
  Pulseaudio bluetooth modules are installed and loaded. Tried
  connecting via hcitool and bluetoothctl, always the same error.
  Attached bluetoothd verbose logfile.

  Package / System info:

  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  $ apt-cache policy bluez
  bluez:
Installiert:   5.41-0ubuntu3

  $ apt-cache policy bluetooth
  bluetooth:
Installiert:   5.41-0ubuntu3

  $ apt-cache policy pulseaudio
  pulseaudio:
Installiert:   1:9.0-2ubuntu2.1

  $ apt-cache policy pulseaudio-module-bluetooth 
  pulseaudio-module-bluetooth:
Installiert:   1:9.0-2ubuntu2.1

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

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

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

[bugproxy]

--- Comment From cdead...@us.ibm.com 2018-05-30 19:55 EDT---
 State: Working by: dlshaw on 30 May 2018 18:45:42 

#=#=#=# David L. Shaw (dls...@us.ibm.com) - 2018-05-30 18:45:40 (CDT) -
POWER Firmware #=#=#=#

The failure was intermittent.  Automated tests are running on the
system.  Time will tell if this resolves the issue.

#=#=#=# end of 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/1773964

Title:
  IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls
  on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

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

Bug description:
  == Comment: #0 - Application Cdeadmin <> - 2018-05-22 09:36:12 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-05-22 09:36:14 ==
   State: Open by: swanman on 22 May 2018 09:17:33 

  Both w34 and wsbmc016 are stopped on this failure, where we get hung
  up on the following FFDC gathering step in the OS:

  #(CDT) 2018/05/22 05:07:19.398218 - 0.211662 - Issuing: OS Execute Command 
ppc64_cpu --frequency ignore_err=1
  #(CDT) 2018/05/22 05:07:19.437808 - 0.024108 - Issuing: ppc64_cpu --frequency 

  , and the last console output shows:
  # tail -200 /var/log/obmc-console.log 
  s this GP) idle=82a/140/0 softirq=2689/2689 fqs=241989 
  [13668.719850]  (detected by 3, t=3075620 jiffies, g=30289, c=30288, q=796881)
  [13732.630691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13732.630727]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=242996 
  [13732.630757]  (detected by 3, t=3091597 jiffies, g=30289, c=30288, q=799822)
  [13795.649568] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13795.649597]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=243942 
  [13795.649631]  (detected by 7, t=3107351 jiffies, g=30289, c=30288, q=802916)
  [13860.140483] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13860.140516]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=244940 
  [13860.140557]  (detected by 3, t=3123473 jiffies, g=30289, c=30288, q=806646)
  [13924.731404] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13924.731438]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=245874 
  [13924.731484]  (detected by 3, t=3139620 jiffies, g=30289, c=30288, q=809909)
  [13988.642290] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13988.642321]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=246892 
  [13988.642362]  (detected by 3, t=3155596 jiffies, g=30289, c=30288, q=813048)
  [14052.661176] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14052.661211]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=247857 
  [14052.661266]  (detected by 3, t=3171600 jiffies, g=30289, c=30288, q=816185)
  [14115.680024] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14115.680051]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=248819 
  [14115.680085]  (detected by 4, t=3187355 jiffies, g=30289, c=30288, q=819190)
  [14180.154911] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14180.154945]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=249833 
  [14180.154986]  (detected by 132, t=3203473 jiffies, g=30289, c=30288, 
q=822138)
  [14244.968067]I F: Ne talls onCPUs/tasks
  [14244669838]   75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=2[14244.669944]  (detected by 3, t=3219600 jiffies, 
g=30289, c=30288, q=825384)
  [14308.748680] Id detected stalls on CPUs/tasks:
  [14308.748719]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=251755 
  [14308.748755]  (detected by 3, t=3235620 jiffies, g=30289, c=30288, q=828445)
  [14333.081775] Watchdog CPU:132 Hard LOCKUP
  [14344.750295] Watchdog CPU:132 became unstuck
  [14372.735558] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14372.735587]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=252722 
  [14372.735611]  (detected by 6, t=3251616 jiffies, g=30289, c=30288, q=831375)
  [14435.910193] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14435.910219]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=253675 
  [14435.910253]  (detected by 3, t=3267409 jiffies, g=30289, c=30288, q=834375)
  [14500.167195] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14500.167230]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=254601 
  [14500.167273]  (detected by 134, t=3283473 jiffies, g=30289, c=30288, 
q=837600)
  [14564.664395] INFO: rcu_sched detected stalls on CPUs/tasks:
  

[Kernel-packages] [Bug 1774306] Re: enable mic-mute hotkey and led on Lenovo M820z and M920z

[Hui Wang]

** Description changed:

- Steps:
- 1. Installed system and log in.
- 2. Press the Microphone mute key.
+ [Impact]
+ M810z, M820z and M920z are Lenovo AIO machines, there is a mic-mute button 
with
+ led on them, without this patch, the hotkey and led only works on M810z, if we
+ want 820z and 920z to work, we need to add their subsystem id in the driver, 
but
+ since they use same codec with same pin conf, we use a better way than adding 
id.
  
- Actual result:
- Microphone mute key and Microphone LED doesn't work at all.
+ [Fix]
+ With this patch, all 3 machines applied ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY.
  
- Expected result:
- Microphone mute key and Microphone LED work should be fine.
+ [Test Case]
+ press mic-mute button, then check sound-setting, we found the input will mute 
or
+ unmute as users press button, and led will on or off to indicate the input 
status.
+ 
+ [Regression Potential]
+ Very low, through the strictly match the pin conf, codec id and vendor id, 
this
+ fix only apply to M810z, M820z and M920z.

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

Title:
  enable mic-mute hotkey and led on Lenovo M820z and M920z

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

Bug description:
  [Impact]
  M810z, M820z and M920z are Lenovo AIO machines, there is a mic-mute button 
with
  led on them, without this patch, the hotkey and led only works on M810z, if we
  want 820z and 920z to work, we need to add their subsystem id in the driver, 
but
  since they use same codec with same pin conf, we use a better way than adding 
id.

  [Fix]
  With this patch, all 3 machines applied ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY.

  [Test Case]
  press mic-mute button, then check sound-setting, we found the input will mute 
or
  unmute as users press button, and led will on or off to indicate the input 
status.

  [Regression Potential]
  Very low, through the strictly match the pin conf, codec id and vendor id, 
this
  fix only apply to M810z, M820z and M920z.

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

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

[Kernel-packages] [Bug 1439503] Re: 14e4:4331 [MacBookPro9, 2] 41%+ packet loss

[Christopher M. Penalver]

Release EOL, and don't have hardware anymore.

** No longer affects: broadcom-sta

** Changed in: bcmwl (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  14e4:4331 [MacBookPro9,2] 41%+ packet loss

Status in bcmwl package in Ubuntu:
  Invalid

Bug description:
  Computer is suffering unusually high packet loss (41%+) with 802.11n through 
a Verizon Jetpack MiFi 5510L (latest router firmware). I tried turning off WiFi 
power management via sudo iwconfig wlan1 power off (I found it enabled), but no 
change. Other WiFi hardware (cell phones, etc.), and other/same operating 
systems don't have this problem. This occurs with the release kernel in Utopic, 
and well as latest:
  uname -a
  Linux macbookpro 3.16.0-33-generic #44-Ubuntu SMP Thu Mar 12 12:19:35 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

  apt-cache policy bcmwl-kernel-source
  bcmwl-kernel-source:
Installed: 6.30.223.248+bdcom-0ubuntu1
Candidate: 6.30.223.248+bdcom-0ubuntu1
Version table:
   *** 6.30.223.248+bdcom-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ utopic/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  lspci -vvnn | grep -A 9 Network
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4331 802.11a/b/g/n 
[14e4:4331] (rev 02)
Subsystem: Apple Inc. AirPort Extreme [106b:00f5]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: wl

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  1 23:53:47 2015
  InstallationDate: Installed on 2015-04-01 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1773635] Re: AR3012 Bluetooth not start after an upgrade to 4.4.0-127

[Andrey Mokrousov]

I'm not sure which mainline kernel is a latest one, so i tried several versions:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.14-xenial/ OK
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.14-xenial/ OK
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.134/   OK
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/  Bluetooth not 
working
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7/  OK

I hope this will help.

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

Title:
  AR3012 Bluetooth not start after an upgrade to 4.4.0-127

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Atheros mixed WiFi+Bluetooth device which worked nice on a kernels 
prior to 4.4.0-127
  But unfortunately after last upgrade (from 4.4.0-124 to 4.4.0-127) bluetooth 
is unable to start - no bluetooth indicator appears in notifications tray and 
no device could be discovered or connected to via bluetooth.

  Tailing a syslog provides following lines, related to bluetooth:
  May 27 12:15:16 K43T kernel: [  228.102799] usbcore: registered new interface 
driver btusb
  May 27 12:15:16 K43T kernel: [  228.109562] Bluetooth: hci0: don't support 
firmware rome 0x1020200
  May 27 12:15:16 K43T systemd-udevd[4634]: Process '/bin/hciconfig hci0 up' 
failed with exit code 1.
  May 27 12:15:16 K43T kernel: [  228.112017] Bluetooth: hci0: don't support 
firmware rome 0x1020200

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-127-generic 4.4.0-127.153
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  insanedeveloper   1937 F pulseaudio
   /dev/snd/controlC0:  insanedeveloper   1937 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 27 12:33:42 2018
  HibernationDevice: RESUME=UUID=4a7e8ac6-783b-4a23-bfa9-8130cfef7945
  InstallationDate: Installed on 2015-11-28 (910 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: ASUSTeK Computer Inc. K43TK
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed 
root=UUID=7dbd7b42-e67f-4416-8f6d-6c918e744fb7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-127-generic N/A
   linux-backports-modules-4.4.0-127-generic  N/A
   linux-firmware 1.157.18
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-01-08 (503 days ago)
  dmi.bios.date: 03/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 206
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K43TK
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr206:bd03/20/2012:svnASUSTeKComputerInc.:pnK43TK:pvr1.0:rvnASUSTeKComputerInc.:rnK43TK:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K43TK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Kernel-packages] [Bug 1770970] Re: Huawei 25G/100G Network Adapters Unsupported

[dann frazier]

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

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

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

Title:
  Huawei 25G/100G Network Adapters Unsupported

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

Bug description:
  [Impact]
  Huawei 25G/100G network adapters are not usable with Ubuntu.

  [Test Case]
  On a system with one of these adapters, the hinic driver should load and 
enumerate devices.

  [Fix]
  We just need to teach the driver about these new PCI IDs.

  [Regression Risk]
  These are previously unsupported devices.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1774306

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

Title:
  enable mic-mute hotkey and led on Lenovo M820z and M920z

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

Bug description:
  Steps:
  1. Installed system and log in.
  2. Press the Microphone mute key.

  Actual result:
  Microphone mute key and Microphone LED doesn't work at all.

  Expected result:
  Microphone mute key and Microphone LED work should be fine.

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

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

[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

[Joseph Salisbury]

I started a kernel bisect between v4.12 final and v4.13-rc1. The kernel
bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
e5f76a2e0e84ca2a215ecbf6feae88780d055c56

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961

Can you test that kernel and report back if it has the bug or not?  I
will build the next test kernel based on your test results.


Thanks in advance

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

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

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1772984] Re: package crda 3.13-1 failed to install/upgrade: Versuch, »/lib/crda/pubkeys/sforshee.key.pub.pem« zu überschreiben, welches auch in Paket wireless-regdb 2015.07.20-1

[Sawyer Bergeron]

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

** This bug has been marked a duplicate of bug 1772985
   package crda 3.13-1 failed to install/upgrade: trying to overwrite 
'/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package 
wireless-regdb 2015.07.20-1ubuntu1

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

Title:
  package crda 3.13-1 failed to install/upgrade: Versuch,
  »/lib/crda/pubkeys/sforshee.key.pub.pem« zu überschreiben, welches
  auch in Paket wireless-regdb 2015.07.20-1ubuntu1 ist

Status in crda package in Ubuntu:
  New

Bug description:
  All said in the summary.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: crda 3.13-1
  Uname: Linux 4.16.10-041610-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  Date: Wed May 23 20:26:25 2018
  ErrorMessage: Versuch, »/lib/crda/pubkeys/sforshee.key.pub.pem« zu 
überschreiben, welches auch in Paket wireless-regdb 2015.07.20-1ubuntu1 ist
  InstallationDate: Installed on 2015-07-08 (1050 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150707)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: crda
  Title: package crda 3.13-1 failed to install/upgrade: Versuch, 
»/lib/crda/pubkeys/sforshee.key.pub.pem« zu überschreiben, welches auch in 
Paket wireless-regdb 2015.07.20-1ubuntu1 ist
  UpgradeStatus: Upgraded to xenial on 2016-06-13 (708 days ago)

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

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

[Kernel-packages] [Bug 1772950] Re: dkms key enrolled in mok, but dkms module fails to load

[Mathieu Trudel-Lapierre]

Verification-done on bionic:

ii  dkms   2.3-3ubuntu9.1   
all  Dynamic Kernel Module Support Framework
ii  virtualbox-dkms5.2.10-dfsg-6
all  x86 virtualization solution - kernel mod

I have verified that with the old dkms, kernel upgrades lead to an
unsigned vboxdrv module; and with the new dkms, kernel upgrades do have
signed modules that load correctly with SecureBoot enabled.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  dkms key enrolled in mok, but dkms module fails to load

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  All Ubuntu users for whom Secure Boot is enabled.

  [Test cases]
  1) install dkms module (use virtualbox-dkms for example)
  2) Upgrade kernel (for example, install 4.15.0-22-generic on top of 
4.15.0-20-generic).
  3) Verify that the generated module for the new kernel (4.15.0-22-generic in 
this example) is built and signed by verifying that the file in 
/lib/modules/$kernel/updates/dkms/$module.ko ends in ~Module signature 
appended~:

  $ hexdump -Cv /lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko | tail 
-n 100
  [...]
  ~Module signature appended~

  4) Reboot
  5) modprobe -v the module.
  It should not respond "Required key not available", and should return with no 
error.
  6) Verify that dkms does not contain PKCS#7 errors.

  
  [Regression potential]
  Possible regressions involve failure to sign and/or be able to load modules 
after updates: failure to sign leading to a module being built but unsigned 
after a new kernel is installed or after a new DKMS module is installed, 
failure to load modules after reboot (usually caused by module being unsigned); 
failure to sign due to missing keys, signature key not being automatically 
slated for enrollment. All these potential regression scenarios present as 
failure to load a DKMS module after a reboot when it should be loaded 
successfully.

  ---

  At my last reboot, I was prompted to enable SecureBoot, so I did.

  When I booted, however, I noticed that the virtualbox service failed
  to start because it couldn't load its kernel module.  If I attempt the
  same thing, I see that there's an issue with keys:

  $ sudo modprobe vboxdrv
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available

  I do have keys enrolled; `mokutil --list-enrolled` produces
  http://paste.ubuntu.com/p/rntTQr5XJV/

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

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

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

[Ridsai]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1773165/+attachment/5146493/+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/1773165

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux 

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

[Ridsai]

apport information

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

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 

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

[Ridsai]

apport information

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

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 

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

[Ridsai]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1773165/+attachment/5146498/+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/1773165

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux 

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

[Ridsai]

apport information

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

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

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 

[Kernel-packages] [Bug 1773165] PciMultimedia.txt

[Ridsai]

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1773165/+attachment/5146495/+files/PciMultimedia.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/1773165

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux 

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

[Ridsai]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1773165/+attachment/5146496/+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/1773165

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux 

[Kernel-packages] [Bug 1773165] WifiSyslog.txt

[Ridsai]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1773165/+attachment/5146501/+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/1773165

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux 

[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04

[Dick Kennedy]

Reply to Comment 12.

There were 2 patches to fix this the 1st patch:
author  James Smart   2018-04-09 14:24:28 -0700
committer   Martin K. Petersen  2018-04-18 
19:34:04 -0400
commit  bf316c78517d9437656293f65a70d6ecdc2ec58e (patch)
tree8ae623e9b580ec1782dbc2d8711cff8a9c9d5e88 /drivers/scsi/lpfc
parent  01466024d2de1c05652d69411461e8e7908f0d1e (diff)
downloadscsi-bf316c78517d9437656293f65a70d6ecdc2ec58e.tar.gz
scsi: lpfc: Fix WQ/CQ creation for older asic's.

Was checking for A0 family and asic ver 0, but this was removed because all of 
the A0 family was effected so thisdiff options
context:
space:  
mode:   
author  James Smart   2018-05-24 21:09:00 -0700
committer   Martin K. Petersen  2018-05-28 
22:40:33 -0400
commit  c221768bd49a7423be57c00a56985c0e9c4122cd (patch)
tree95b132c07e187ecd69665ececbdd7ec12a08772c /drivers/scsi/lpfc
parent  7438273fa23bea6d1e647e66c451570b86e2758b (diff)
downloadscsi-c221768bd49a7423be57c00a56985c0e9c4122cd.tar.gz
scsi: lpfc: Fix 16gb hbas failing cq create. patch removed the asic ver 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/1768103

Title:
  Lancer A0 Asic HBA's won't boot with 18.04

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

Bug description:
  
  We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.   

  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.

  We'll leave it up to Canonical to decide whether they want to pull
  this in this single patch to an 18.04 subsequent update.

  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
  Resolution: new lpfc driver patch update. 

  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111

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

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

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

[Ridsai]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1773165/+attachment/5146499/+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/1773165

Title:
  openvswitch-datapath-dkms kernel module is not getting loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 16.04.4 LTS
  Release: 16.04
  Codename: xenial

  Kernel version: 4.4.0-127-generic
  OVS version: 2.7.0

  
  # Issue description
  openvswitch-datapath-dkms kernelmodule is not getting loaded

  
  # Error from dmesg
  [10863.380564] openvswitch: module verification failed: signature and/or 
required key missing - tainting kernel
  [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)
  [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned 
by kernel)

  
  #Error from syslog
  May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate 
symbol dst_cache_destroy (owned by kernel)
  May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not 
insert 'openvswitch': Exec format error
  May 24 08:37:06 dev65 openvswitch-switch[18336]:  * Inserting openvswitch 
module

  
  #installation logs:
  Selecting previously unselected package openvswitch-datapath-dkms.
  (Reading database ... 84707 files and directories currently installed.)
  Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ...
  Unpacking openvswitch-datapath-dkms (2.7.0-1) ...
  Setting up openvswitch-datapath-dkms (2.7.0-1) ...

  Creating symlink /var/lib/dkms/openvswitch/2.7.0/source ->
   /usr/src/openvswitch-2.7.0

  DKMS: add completed.

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area(bad exit status: 2)
  ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C 
datapath/linux..
  cleaning build area(bad exit status: 2)

  DKMS: build completed.

  openvswitch:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-geneve.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-gre.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-lisp.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-stt.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  vport-vxlan.ko:
  Running module version sanity check.
   - Original module
   - Installation
 - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/

  depmod

  DKMS: install completed.

  
  #Dpkg status
  dpkg -l | grep openvswitch
  ii  openvswitch-common   2.7.0-1  
  amd64Open vSwitch common components
  ii  openvswitch-datapath-dkms2.7.0-1  
  all  Open vSwitch datapath module source - DKMS version
  ii  openvswitch-switch   2.7.0-1  
  amd64Open vSwitch switch implementations
  ii  python-openvswitch   2.6.1-0ubuntu5.2~cloud0  
  all  Python bindings for Open vSwitch

  #lsmod status
  No modules are listing for openvswitch-datapath-dkms

  #modprobe error
  modprobe openvswitch
  modprobe: ERROR: could not insert 'openvswitch': Exec format error
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-127-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux 

[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

[Carl Reinke]

I guess it's less ambiguous to say that e5f76a2 has the bug.

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

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

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

[Carl Reinke]

e5f76a2e0e84ca2a215ecbf6feae88780d055c56 (4.12.0-041200.201805301435)
does not work.

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

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

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

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

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

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

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

[remram44]

[ 2273.365506] BUG: unable to handle kernel NULL pointer dereference at 
0030
[ 2273.365512] IP: ecryptfs_privileged_open+0x51/0x180
[ 2273.365513] PGD 0 P4D 0 
[ 2273.365515] Oops:  [#1] SMP PTI
[ 2273.365516] Modules linked in: ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter 
xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc overlay pci_stub 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep dm_crypt binfmt_misc 
nls_iso8859_1 arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel snd_hda_codec_hdmi kvm irqbypass uvcvideo crct10dif_pclmul 
videobuf2_vmalloc snd_hda_codec_realtek crc32_pclmul videobuf2_memops 
ghash_clmulni_intel snd_hda_codec_generic videobuf2_v4l2 videobuf2_core pcbc 
videodev media btusb btrtl snd_seq_midi btbcm btintel iwlmvm aesni_intel 
bluetooth snd_hda_intel snd_seq_midi_event mac80211 aes_x86_64 ecdh_generic
[ 2273.365541]  crypto_simd glue_helper snd_hda_codec snd_rawmidi cryptd 
snd_hda_core intel_cstate intel_rapl_perf snd_hwdep iwlwifi snd_pcm cfg80211 
snd_seq rtsx_pci_ms idma64 joydev memstick virt_dma input_leds wmi_bmof 
thinkpad_acpi intel_wmi_thunderbolt serio_raw mei_me intel_lpss_pci 
snd_seq_device mei intel_pch_thermal intel_lpss nvram shpchp snd_timer snd 
soundcore mac_hid acpi_pad tpm_crb sch_fq_codel parport_pc ppdev sunrpc lp 
parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear nouveau i915 mxm_wmi ttm i2c_algo_bit 
drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt rtsx_pci_sdmmc psmouse 
ptp fb_sys_fops pps_core nvme drm rtsx_pci nvme_core wmi i2c_hid video hid
[ 2273.365571]  pinctrl_sunrisepoint
[ 2273.365573] CPU: 6 PID: 29901 Comm: action-suid Tainted: G   OE
4.15.0-22-generic #24-Ubuntu
[ 2273.365574] Hardware name: LENOVO 20HH000AUS/20HH000AUS, BIOS N1UET46W (1.20 
) 02/26/2018
[ 2273.365576] RIP: 0010:ecryptfs_privileged_open+0x51/0x180
[ 2273.365577] RSP: 0018:b33145e2bb48 EFLAGS: 00010246
[ 2273.365578] RAX: b33145e2bb70 RBX: 948a0f48fe88 RCX: 948bf02eb780
[ 2273.365579] RDX: 926e4b40 RSI: 91cc2d53 RDI: b33145e2bb68
[ 2273.365580] RBP: b33145e2bbb8 R08: 948c405a7060 R09: 948aa2ca1ab0
[ 2273.365581] R10: 007374736f68 R11: 0005 R12: 
[ 2273.365582] R13: 948bf02eb780 R14:  R15: 948b67ff7200
[ 2273.365583] FS:  7f13be06d580() GS:948c4058() 
knlGS:
[ 2273.365584] CS:  0010 DS:  ES:  CR0: 80050033
[ 2273.365585] CR2: 0030 CR3: 00026c512001 CR4: 003606e0
[ 2273.365586] Call Trace:
[ 2273.365589]  ecryptfs_get_lower_file+0x7d/0xc0
[ 2273.365591]  ecryptfs_open+0x71/0x200
[ 2273.365593]  do_dentry_open+0x1c2/0x310
[ 2273.365594]  ? ecryptfs_flush+0x50/0x50
[ 2273.365596]  vfs_open+0x4f/0x80
[ 2273.365598]  path_openat+0x66e/0x1770
[ 2273.365599]  ? filename_lookup+0xf2/0x190
[ 2273.365602]  do_filp_open+0x9b/0x110
[ 2273.365604]  ? __check_object_size+0xaf/0x1b0
[ 2273.365606]  ? __alloc_fd+0x46/0x170
[ 2273.365607]  do_sys_open+0x1bb/0x2c0
[ 2273.365609]  ? do_sys_open+0x1bb/0x2c0
[ 2273.365611]  SyS_openat+0x14/0x20
[ 2273.365613]  do_syscall_64+0x73/0x130
[ 2273.365615]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 2273.365616] RIP: 0033:0x7f13bdba5c8e
[ 2273.365617] RSP: 002b:7ffc7ffa7d00 EFLAGS: 0246 ORIG_RAX: 
0101
[ 2273.365618] RAX: ffda RBX: 5006 RCX: 7f13bdba5c8e
[ 2273.365619] RDX:  RSI: 55dec5346190 RDI: ff9c
[ 2273.365620] RBP: 55dec5346190 R08:  R09: 0009
[ 2273.365621] R10:  R11: 0246 R12: 55dec533cb70
[ 2273.365622] R13:  R14: 55dec5346190 R15: 
[ 2273.365623] Code: c2 40 4b 6e 92 49 89 cd 65 48 8b 04 25 28 00 00 00 48 89 
45 d8 31 c0 48 8d 45 90 c7 45 a8 00 00 00 00 48 8d 78 20 e8 3f 23 d4 ff <49> 8b 
44 24 30 48 89 5d 90 4c 89 65 a0 4c 89 75 98 48 8b 40 28 
[ 2273.365642] RIP: ecryptfs_privileged_open+0x51/0x180 RSP: b33145e2bb48
[ 2273.365643] CR2: 0030
[ 2273.365645] ---[ end trace e3ba314809fc3c25 ]---

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

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

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

Bug description:
  Trying to 'cat' a file in an overlayfs. The file is in the lowerdir
  which is ecryptfs. I use the attached script to create directories and
  randomly distributed files. $HOME is ecryptfs. /tmp/ is tmpfs.

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

[remram44]

This affects me when I try to run a Singularity (sandbox) container from
my (encrypted) home folder. Linux 4.15.0-22-generic x86_64 on Ubuntu
18.04.

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

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

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

Bug description:
  Trying to 'cat' a file in an overlayfs. The file is in the lowerdir
  which is ecryptfs. I use the attached script to create directories and
  randomly distributed files. $HOME is ecryptfs. /tmp/ is tmpfs.

  $ pwd
  $HOME/Hacking/overlayfs/

  $ ./build.sh

  $ sudo mount -t overlay overlay -o
  lowerdir=lower/1,upperdir=/tmp/upper/1,workdir=/tmp/workdir/1
  overlay/1

  $ grep /tmp /proc/mounts
  tmpfs /tmp tmpfs rw,nosuid,nodev,relatime 0 0
  overlay /home/tj/Hacking/overlayfs/overlay/1 overlay 
rw,relatime,lowerdir=lower/1,upperdir=/tmp/upper/1,workdir=/tmp/workdir/1 0 0

  $ ls lower/1/
  1b  1c  1d  1e  1f  1g  1k  1l  1o  1p  1q  1t  1u  1v  1w  1x  1y  1z

  $ ls /tmp/upper/1/
  1e  1i  1l  1n  1u

  $ ls overlay/1/
  1b  1c  1d  1e  1f  1g  1i  1k  1l  1n  1o  1p  1q  1t  1u  1v  1w  1x  1y  1z

  $ cat overlay/1/1b
  Killed

  $ uname -r
  4.13.0-16-lowlatency

  $ lsb_release -a
  LSB Version:
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  Codename:   xenial

  $ apt list linux-lowlatency-hwe-16.04-edge
  Listing... Done
  linux-lowlatency-hwe-16.04-edge/xenial-proposed,now 4.13.0.16.23 amd64 
[installed]

  $ tail /var/log/kern.log

  Oct 31 03:11:09 hephaestion kernel: [ 1057.380604] BUG: unable to handle 
kernel NULL pointer dereference at 0030
  Oct 31 03:11:09 hephaestion kernel: [ 1057.380668] IP: 
ecryptfs_privileged_open+0x51/0x180
  Oct 31 03:11:09 hephaestion kernel: [ 1057.380686] PGD 20ee07067
  Oct 31 03:11:09 hephaestion kernel: [ 1057.380688] P4D 20ee07067
  Oct 31 03:11:09 hephaestion kernel: [ 1057.380700] PUD 20c455067
  Oct 31 03:11:09 hephaestion kernel: [ 1057.380711] PMD 0
  Oct 31 03:11:09 hephaestion kernel: [ 1057.380721]
  Oct 31 03:11:09 hephaestion kernel: [ 1057.380741] Oops:  [#1] PREEMPT SMP
  Oct 31 03:11:09 hephaestion kernel: [ 1057.380755] Modules linked in: overlay 
hidp scsi_transport_iscsi veth ip6t_MASQUERADE nf_nat_masquerade_ipv6 
ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 ccm xt_conntrack 
nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filter ip_tables x_tables 8021q garp mrp stp 
llc rfcomm bnep binfmt_misc dm_thin_pool dm_persistent_data dm_bio_prison 
dm_bufio cdc_mbim cdc_wdm cdc_ncm usbnet cdc_acm mii gpio_ich dell_laptop 
coretemp btusb btrtl btbcm btintel joydev dell_wmi bluetooth dell_smbios dcdbas 
wmi_bmof sparse_keymap serio_raw ecdh_generic arc4 snd_hda_codec_idt 
snd_hda_codec_generic snd_hda_intel
  Oct 31 03:11:09 hephaestion kernel: [ 1057.381004]  snd_hda_codec 
snd_hda_core input_leds snd_hwdep snd_pcm snd_seq_midi uvcvideo 
snd_seq_midi_event videobuf2_vmalloc videobuf2_memops snd_rawmidi 
videobuf2_v4l2 iwl4965 videobuf2_core iwlegacy videodev media mac80211 snd_seq 
r852 sm_common nand nand_ecc nand_bch bch mtd r592 memstick lpc_ich cfg80211 
snd_seq_device snd_timer snd soundcore shpchp mac_hid kvm_intel kvm irqbypass 
parport_pc ppdev nfsd lp auth_rpcgss nfs_acl lockd grace parport sunrpc autofs4 
crypto_simd glue_helper cryptd aes_x86_64 algif_skcipher af_alg dm_crypt raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log 
hid_generic usbhid hid psmouse sky2 ahci nouveau libahci pata_acpi 
firewire_ohci sdhci_pci sdhci firewire_core
  Oct 31 03:11:09 hephaestion kernel: [ 1057.381012]  crc_itu_t mxm_wmi 
i2c_algo_bit video ttm drm_kms_helper syscopyarea sysfillrect sysimgblt 
fb_sys_fops drm wmi
  Oct 31 03:11:09 hephaestion kernel: [ 1057.381012] CPU: 0 PID: 10087 Comm: 
cat Tainted: P   OE   4.13.0-16-lowlatency #19~16.04.3-Ubuntu
  Oct 31 03:11:09 hephaestion kernel: [ 1057.381012] Hardware name: Dell Inc. 
XPS M1530   /  , BIOS A12 11/19/2008
  Oct 31 03:11:09 hephaestion kernel: [ 1057.381012] task: 8a116705 
task.stack: a10c010a8000
  Oct 31 03:11:09 hephaestion kernel: [ 1057.381012] RIP: 
0010:ecryptfs_privileged_open+0x51/0x180
  Oct 31 03:11:09 hephaestion kernel: [ 1057.381012] RSP: 0018:a10c010abb60 
EFLAGS: 00010246
  Oct 31 03:11:09 hephaestion kernel: [ 

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

[bugproxy]

--- Comment From pavra...@in.ibm.com 2018-05-30 01:55 EDT---
(In reply to comment #8)
> Did this issue start with the 4.15.0-22 kernel?  Was there a prior 4.15
> based kernel that did not exhibit this bug?
>
> Could you also see if this bug happens with the Bionic -proposed or mainline
> kernel:
>
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed.
>
> Mainline can be downloaded from:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7/

Tested with given kernels below is the summary.

4.15.0-20-generic -> System boots
4.15.0-22-generic -> System fails to boots with oops
4.15.0-23-generic -> System fails to boots with oops
4.15.0-23-generic #26~lp1773162 -> System boots

Thanks,
Pavithra

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

Title:
  Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting
  with 4.15.0-22-generic kernel.

Status in The Ubuntu-power-systems project:
  New
Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in debian-installer source package in Bionic:
  New
Status in linux source package in Bionic:
  Incomplete

Bug description:
  ---Problem Description---

  Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting
  with 4.15.0-22-generic kernel.

  ---Environment--
  Kernel Build:   4.15.0-22-generic
  System Name :  ltc-garri1
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  Unable to boot.

  ---Steps to reproduce--

  1. Install Ubuntu 18.04 on Garison BML from http://ports.ubuntu.com
  /ubuntu-ports/dists/bionic/main/installer-
  ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ and try to
  boot.

  ---Logs

  Attaching console lob.

  [4.578205] Bad kernel stack pointer 7b0dd870 at c000b9ec
  [4.578244] Oops: Bad kernel stack pointer, sig: 6 [#11]
  [4.578271] LE SMP NR_CPUS=2048 NUMA PowerNV
  [4.578301] Modules linked in:
  [4.578324] CPU: 27 PID: 1225 Comm: modprobe Tainted: G  D  
4.15.0-22-generic #24-Ubuntu
  [4.578371] NIP:  c000b9ec LR:  CTR: 

  [4.578413] REGS: c0003febbd40 TRAP: 0300   Tainted: G  D  
 (4.15.0-22-generic)
  [4.578460] MSR:  90001031   CR:   XER: 

  [4.578504] CFAR: c000b934 DAR: 0002b200 DSISR: 4000 
SOFTE: -4611686018403131680 
  [4.578504] GPR00:  7b0dd870  
 
  [4.578504] GPR04:    
 
  [4.578504] GPR08:    
 
  [4.578504] GPR12: 75dcd8781700 0002b200  
 
  [4.578504] GPR16:    
 
  [4.578504] GPR20:    
 
  [4.578504] GPR24:    
 
  [4.578504] GPR28:    
 
  [4.615667] NIP [c000b9ec] fast_exception_return+0x9c/0x184
  [4.616210] LR []   (null)
  [4.616237] Call Trace:
  [4.616768] Instruction dump:
  [4.616789] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 
e8810090 
  [4.617697] e8210078 7db243a6 7db142a6 7c0004ac  63ff 
7db242a6 63ff 
  [4.618195] ---[ end trace a0d70ba94f583cca ]---
  [4.675899] usb 1-3.3: new high-speed USB device number 5 using xhci_hcd
  [4.782923] 
  [4.783061] Key type encrypted registered
  [4.783087] AppArmor: AppArmor sha1 policy hashing enabled
  [4.783117] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
  [4.783181] evm: HMAC attrs: 0x1
  [4.806062] rtc-opal opal-rtc: setting system clock to 2018-05-29 07:49:29 
UTC (1527580169)
  [4.806350] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [4.806353] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [4.807260] Freeing unused kernel memory: 4800K
  [4.807321] This architecture does not have kernel memory protection.

  
  == Comment: #2 - SEETEENA THOUFEEK  - 2018-05-29 
06:47:06 ==
  Symptoms looks exactly like 
  .
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691978
  .
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908

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

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

[Kernel-packages] [Bug 1774105] Re: [Dell Inspiron 7577] System took a very long time to shutdown

[Po-Hsu Lin]

** Summary changed:

- [Dell Inspiron 7577] System hang during shutdown
+ [Dell Inspiron 7577] System took a very long time to shutdown

** Description changed:

  CID: 201706-25581 Dell Inspiron 7577
  
  Steps:
-   1. Install Bionic + update with LiveUSB
-   2. Boot to the desktop
-   3. Poweroff / restart the system from the menu in the upper right corner
+   1. Install Bionic + update with LiveUSB
+   2. Boot to the desktop
+   3. Poweroff / restart the system from the menu in the upper right corner
  
  Result:
-   The system will hang before reaching the splash screen. The ctrl + alt + 
prtscr + b magic key combination is still alive. This is the last thing that 
could be seen from syslog:
+   It will take about 5 minutes for this system to poweroff. It will hang for 
about 3 minutes right after you click on the power off button. The ctrl + alt + 
prtscr + b magic key combination is still alive. This is the last thing that 
could be seen from syslog:
  
  May 30 12:29:27 ubuntu-Inspiron-7577 systemd[858]: Stopping D-Bus User 
Message Bus...
  May 30 12:29:27 ubuntu-Inspiron-7577 gvfsd[1038]: A connection to the bus 
can't be made
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: 
gnome-session-binary[942]: WARNING: Lost name on bus: org.gnome.SessionManager
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: WARNING: Lost 
name on bus: org.gnome.SessionManager
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: 
gnome-session-binary[942]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: CRITICAL: We 
failed, but the fail whale is dead. Sorry
  May 30 12:29:27 ubuntu-Inspiron-7577 gsd-xsettings[1223]: Error releasing 
name org.gtk.Settings: The connection is closed
- 
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^
+ 
+ After that, you will see console output and nouveau is complaining about
+ fail-to-idle.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: User Name 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 12:34:00 2018
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  [Dell Inspiron 7577] System took a very long time to shutdown

Status in linux-signed package in Ubuntu:
  New

Bug description:
  CID: 201706-25581 Dell Inspiron 7577

  Steps:
    1. Install Bionic + update with LiveUSB
    2. Boot to the desktop
    3. Poweroff / restart the system from the menu in the upper right corner

  Result:
    It will take about 5 minutes for this system to poweroff. It will hang for 
about 3 minutes right after you click on the power off button. The ctrl + alt + 
prtscr + b magic key combination is still alive. This is the last thing that 
could be seen from syslog:

  May 30 12:29:27 ubuntu-Inspiron-7577 systemd[858]: Stopping D-Bus User 
Message Bus...
  May 30 12:29:27 ubuntu-Inspiron-7577 gvfsd[1038]: A connection to the bus 
can't be made
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: 
gnome-session-binary[942]: WARNING: Lost name on bus: org.gnome.SessionManager
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: WARNING: Lost 
name on bus: org.gnome.SessionManager
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: 
gnome-session-binary[942]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: CRITICAL: We 
failed, but the fail whale is dead. Sorry
  May 30 12:29:27 ubuntu-Inspiron-7577 gsd-xsettings[1223]: Error releasing 
name org.gtk.Settings: The connection is closed

  After that, you will see console output and nouveau is complaining
  about fail-to-idle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: User Name 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  

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

[bugproxy]

--- Comment From vipar...@in.ibm.com 2018-05-30 02:56 EDT---
(In reply to comment #23)
>
> This bug has now been closed in LP. If the issue is recurring with more
> recent kernels, could you raise a new defect referring back to this one
> (LP#1743541)?
> Thanks.

Closing this bug in Bugzilla as verification failed.

Hi Shriya,

Please raise a new bug for this again as suggested by Canonical.

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

Title:
  Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is
  offline

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

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-16 
04:58:48 ==
  Problem Description :
  =

  cpupower monitor fails to show stop states when cpu 0 is made offline.

  Testing :
  =
  root@ltc-wspoon12:~# echo 0 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# 

  root@ltc-wspoon12:~# echo 1 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop | stop | stop 
 0|  12|  12|  0.00|  0.00|  0.00|  0.00|  0.01

  Details :
  
  uname -a : Linux ltc-wspoon12 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 
21:15:55 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  OS : Ubuntu 18.04
  Machine : Witherspoon ( DD2.1) and Boston (DD.01)

  Patch :
  
  Patch that fixes the issue : 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  == Comment: #1 - VIPIN K. PARASHAR  - 2018-01-16 
05:09:40 ==
  (In reply to comment #0)

  > Patch :
  > 
  > Patch that fixes the issue :
  > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
  > ?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  $ git log dbdc468f35ee827 -1
  commit dbdc468f35ee827cab2753caa1c660bdb832243a
  Author: Abhishek Goel 
  Date:   Wed Nov 15 14:10:02 2017 +0530

  cpupower : Fix cpupower working when cpu0 is offline
  
  cpuidle_monitor used to assume that cpu0 is always online which is not
  a valid assumption on POWER machines. This patch fixes this by getting
  the cpu on which the current thread is running, instead of always using
  cpu0 for monitoring which may not be online.
  
  Signed-off-by: Abhishek Goel 
  Signed-off-by: Shuah Khan 
  $

  Commit dbdc468f3 is available with 4.15-rc2 onwards.

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

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

[Kernel-packages] [Bug 1772933] Re: linux-oem: -proposed tracker

[Timo Aaltonen]

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Khaled El Mously (kmously) => Timo Aaltonen (tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Khaled El Mously (kmously) => Timo Aaltonen (tjaalton)

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Khaled El Mously (kmously) => Timo Aaltonen (tjaalton)

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

Title:
  linux-oem: 4.15.0-1007.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1772927
  phase: Packaging

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

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

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

[Stefan Bader]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
+ derivatives: bug 1774125 (linux-raspi2)

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

Title:
  linux:  -proposed tracker

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

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

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

  backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)

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

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

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

[ethan.hsieh]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  [i915_bpo] Fix flickering issue after panel change

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1772951] Re: linux: 4.13.0-44.49 -proposed tracker

[Stefan Bader]

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

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

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

Title:
  linux: 4.13.0-44.49 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  In Progress
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 1772953 (linux-gcp), bug 1772956 (linux-oem), bug 1772957 
(linux-hwe)
  derivatives: bug 1772952 (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/1772951/+subscriptions

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

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

[Stefan Bader]

Public bug reported:

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

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

backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
derivatives: bug 1774125 (linux-raspi2)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


** Tags: artful kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.05.21-2 kernel-sru-master-kernel

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

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

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

** Tags added: artful

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1774105] Re: [Dell Inspiron 7577] System took a very long time to shutdown

[Po-Hsu Lin]

Tested with 4.17rc7, issue still exist.

But the situation is a bit different, the system was hanging there for
more than 30 minutes, and the magic key is not working.

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

Title:
  [Dell Inspiron 7577] System took a very long time to shutdown with
  nouveau driver

Status in linux-signed package in Ubuntu:
  New

Bug description:
  CID: 201706-25581 Dell Inspiron 7577

  Steps:
    1. Install Bionic + update with LiveUSB
    2. Boot to the desktop
    3. Poweroff / restart the system from the menu in the upper right corner

  Result:
    It will take about 5 minutes for this system to poweroff. It will hang for 
about 3 minutes right after you click on the power off button. The ctrl + alt + 
prtscr + b magic key combination is still alive. This is the last thing that 
could be seen from syslog:

  May 30 12:29:27 ubuntu-Inspiron-7577 systemd[858]: Stopping D-Bus User 
Message Bus...
  May 30 12:29:27 ubuntu-Inspiron-7577 gvfsd[1038]: A connection to the bus 
can't be made
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: 
gnome-session-binary[942]: WARNING: Lost name on bus: org.gnome.SessionManager
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: WARNING: Lost 
name on bus: org.gnome.SessionManager
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: 
gnome-session-binary[942]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: CRITICAL: We 
failed, but the fail whale is dead. Sorry
  May 30 12:29:27 ubuntu-Inspiron-7577 gsd-xsettings[1223]: Error releasing 
name org.gtk.Settings: The connection is closed

  After that, you will see console output and nouveau is complaining
  about fail-to-idle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: User Name 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 12:34:00 2018
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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-signed/+bug/1774105/+subscriptions

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

[Kernel-packages] [Bug 1774126] [NEW] linux-oem: -proposed tracker

[Stefan Bader]

Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1774124 kernel-sru-cycle-2018.05.21-2 xenial

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

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

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1774105] Re: [Dell Inspiron 7577] System took a very long time to shutdown with nouveau driver

[Po-Hsu Lin]

** Summary changed:

- [Dell Inspiron 7577] System took a very long time to shutdown
+ [Dell Inspiron 7577] System took a very long time to shutdown with nouveau 
driver

** Description changed:

  CID: 201706-25581 Dell Inspiron 7577
  
  Steps:
    1. Install Bionic + update with LiveUSB
    2. Boot to the desktop
    3. Poweroff / restart the system from the menu in the upper right corner
  
  Result:
    It will take about 5 minutes for this system to poweroff. It will hang for 
about 3 minutes right after you click on the power off button. The ctrl + alt + 
prtscr + b magic key combination is still alive. This is the last thing that 
could be seen from syslog:
  
  May 30 12:29:27 ubuntu-Inspiron-7577 systemd[858]: Stopping D-Bus User 
Message Bus...
  May 30 12:29:27 ubuntu-Inspiron-7577 gvfsd[1038]: A connection to the bus 
can't be made
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: 
gnome-session-binary[942]: WARNING: Lost name on bus: org.gnome.SessionManager
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: WARNING: Lost 
name on bus: org.gnome.SessionManager
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: 
gnome-session-binary[942]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: CRITICAL: We 
failed, but the fail whale is dead. Sorry
  May 30 12:29:27 ubuntu-Inspiron-7577 gsd-xsettings[1223]: Error releasing 
name org.gtk.Settings: The connection is closed
  
  After that, you will see console output and nouveau is complaining about
  fail-to-idle.
  
+ If you have the nvidia-390 driver installed, this issue will gone.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: User Name 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 12:34:00 2018
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [Dell Inspiron 7577] System took a very long time to shutdown with
  nouveau driver

Status in linux-signed package in Ubuntu:
  New

Bug description:
  CID: 201706-25581 Dell Inspiron 7577

  Steps:
    1. Install Bionic + update with LiveUSB
    2. Boot to the desktop
    3. Poweroff / restart the system from the menu in the upper right corner

  Result:
    It will take about 5 minutes for this system to poweroff. It will hang for 
about 3 minutes right after you click on the power off button. The ctrl + alt + 
prtscr + b magic key combination is still alive. This is the last thing that 
could be seen from syslog:

  May 30 12:29:27 ubuntu-Inspiron-7577 systemd[858]: Stopping D-Bus User 
Message Bus...
  May 30 12:29:27 ubuntu-Inspiron-7577 gvfsd[1038]: A connection to the bus 
can't be made
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: 
gnome-session-binary[942]: WARNING: Lost name on bus: org.gnome.SessionManager
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: WARNING: Lost 
name on bus: org.gnome.SessionManager
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session[942]: 
gnome-session-binary[942]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
  May 30 12:29:27 ubuntu-Inspiron-7577 gnome-session-binary[942]: CRITICAL: We 
failed, but the fail whale is dead. Sorry
  May 30 12:29:27 ubuntu-Inspiron-7577 gsd-xsettings[1223]: Error releasing 
name org.gtk.Settings: The connection is closed

  After that, you will see console output and nouveau is complaining
  about fail-to-idle.

  If you have the nvidia-390 driver installed, this issue will gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: User Name 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 12:34:00 2018
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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-signed/+bug/1774105/+subscriptions

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

[Kernel-packages] [Bug 1774127] [NEW] linux-gcp: -proposed tracker

[Stefan Bader]

Public bug reported:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-backport-of-1774124 kernel-sru-cycle-2018.05.21-2 xenial

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

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

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

** Tags added: xenial

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1774099] Re: iwlwifi Error sending STATISTICS_CMD: time out after 2000ms

[Po-Hsu Lin]

BTW this issue is a bit difficult to reproduce.
I can't see this just after a reboot. Nor with the upstream kernel 4.17rc7 
installed.

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

Title:
  iwlwifi Error sending STATISTICS_CMD: time out after 2000ms

Status in linux-signed package in Ubuntu:
  New

Bug description:
  CID: 201706-25581 Dell Inspiron 7577

  Steps:
    1. Install Bionic + update with LiveUSB
    2. Boot to the desktop

  Result:
    Wifi connection looks OK on both 2.4g and 5g network, but error message for 
iwlwifi could be found in dmesg:
  [   73.936841] iwlwifi :3c:00.0: Error sending STATISTICS_CMD: time out 
after 2000ms.
  [   73.936843] iwlwifi :3c:00.0: Current CMD queue read_ptr 198 write_ptr 
199
  [   73.937703] iwlwifi :3c:00.0: Loaded firmware version: 34.0.1
  [   73.937705] iwlwifi :3c:00.0: 0x | ADVANCED_SYSASSERT
  [   73.937707] iwlwifi :3c:00.0: 0x | trm_hw_status0
  [   73.937708] iwlwifi :3c:00.0: 0x | trm_hw_status1
  [   73.937709] iwlwifi :3c:00.0: 0x | branchlink2
  [   73.937710] iwlwifi :3c:00.0: 0x | interruptlink1
  [   73.937712] iwlwifi :3c:00.0: 0x | interruptlink2
  [   73.937713] iwlwifi :3c:00.0: 0x | data1
  [   73.937714] iwlwifi :3c:00.0: 0x | data2
  [   73.937715] iwlwifi :3c:00.0: 0x | data3
  [   73.937716] iwlwifi :3c:00.0: 0x | beacon time
  [   73.937718] iwlwifi :3c:00.0: 0x | tsf low
  [   73.937719] iwlwifi :3c:00.0: 0x000C | tsf hi
  [   73.937720] iwlwifi :3c:00.0: 0x | time gp1
  [   73.937722] iwlwifi :3c:00.0: 0x0390CA61 | time gp2
  [   73.937723] iwlwifi :3c:00.0: 0x0001 | uCode revision type
  [   73.937724] iwlwifi :3c:00.0: 0x0022 | uCode version major
  [   73.937725] iwlwifi :3c:00.0: 0x | uCode version minor
  [   73.937727] iwlwifi :3c:00.0: 0x0230 | hw version
  [   73.937728] iwlwifi :3c:00.0: 0x00489000 | board version
  [   73.937729] iwlwifi :3c:00.0: 0x8078F500 | hcmd
  [   73.937731] iwlwifi :3c:00.0: 0x02722000 | isr0
  [   73.937732] iwlwifi :3c:00.0: 0x0080 | isr1
  [   73.937733] iwlwifi :3c:00.0: 0x08001802 | isr2
  [   73.937734] iwlwifi :3c:00.0: 0x00400082 | isr3
  [   73.937736] iwlwifi :3c:00.0: 0x | isr4
  [   73.937737] iwlwifi :3c:00.0: 0x00C6019C | last cmd Id
  [   73.937738] iwlwifi :3c:00.0: 0x | wait_event
  [   73.937739] iwlwifi :3c:00.0: 0xB30D | l2p_control
  [   73.937741] iwlwifi :3c:00.0: 0x1C20 | l2p_duration
  [   73.937742] iwlwifi :3c:00.0: 0x | l2p_mhvalid
  [   73.937743] iwlwifi :3c:00.0: 0x00F0 | l2p_addr_match
  [   73.937744] iwlwifi :3c:00.0: 0x000D | lmpm_pmg_sel
  [   73.937746] iwlwifi :3c:00.0: 0x30101345 | timestamp
  [   73.937747] iwlwifi :3c:00.0: 0x0034D8F0 | flow_handler
  [   73.937822] iwlwifi :3c:00.0: 0x | ADVANCED_SYSASSERT
  [   73.937823] iwlwifi :3c:00.0: 0x | umac branchlink1
  [   73.937824] iwlwifi :3c:00.0: 0x | umac branchlink2
  [   73.937825] iwlwifi :3c:00.0: 0x | umac interruptlink1
  [   73.937827] iwlwifi :3c:00.0: 0x | umac interruptlink2
  [   73.937828] iwlwifi :3c:00.0: 0x | umac data1
  [   73.937829] iwlwifi :3c:00.0: 0x | umac data2
  [   73.937830] iwlwifi :3c:00.0: 0x | umac data3
  [   73.937832] iwlwifi :3c:00.0: 0x | umac major
  [   73.937833] iwlwifi :3c:00.0: 0x | umac minor
  [   73.937834] iwlwifi :3c:00.0: 0x | frame pointer
  [   73.937835] iwlwifi :3c:00.0: 0x | stack pointer
  [   73.937837] iwlwifi :3c:00.0: 0x | last host cmd
  [   73.937838] iwlwifi :3c:00.0: 0x | isr status reg

  [ 1056.908386] iwlwifi :3c:00.0: Microcode SW error detected.  Restarting 
0x200.
  [ 1056.908546] iwlwifi :3c:00.0: Start IWL Error Log Dump:
  [ 1056.908552] iwlwifi :3c:00.0: Status: 0x0100, count: 6
  [ 1056.908558] iwlwifi :3c:00.0: Loaded firmware version: 34.0.1
  [ 1056.908565] iwlwifi :3c:00.0: 0x0071 | ADVANCED_SYSASSERT
  [ 1056.908570] iwlwifi :3c:00.0: 0x02F0 | trm_hw_status0
  [ 1056.908575] iwlwifi :3c:00.0: 0x | trm_hw_status1
  [ 1056.908581] iwlwifi :3c:00.0: 0x00023FDC | branchlink2
  [ 1056.908586] iwlwifi :3c:00.0: 0x0003915A | interruptlink1
  [ 1056.908591] iwlwifi :3c:00.0: 0x0003915A | interruptlink2
  [ 1056.908596] iwlwifi :3c:00.0: 0x | data1
  [ 1056.908602] iwlwifi :3c:00.0: 0x1000 | data2
  [ 1056.908607] iwlwifi :3c:00.0: 0x0783 | data3
  [ 1056.908612] iwlwifi :3c:00.0: 0x01419617 | beacon time
  [ 1056.908618] iwlwifi :3c:00.0: 

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

[Ubuntu Kernel Bot]

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

apport-collect 1774150

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

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

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

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

** Tags added: trusty

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

Title:
  3.13.0-149-generic: suspend/resume issue on 14.04

Status in linux package in Ubuntu:
  Incomplete

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 1774124] Re: linux: 4.13.0-45.50 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)
+ kernel-stable-phase-changed:Wednesday, 30. May 2018 09:01 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)
  kernel-stable-phase-changed:Wednesday, 30. May 2018 09:01 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.13.0-45.50 -proposed tracker

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

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

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

  backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)
  kernel-stable-phase-changed:Wednesday, 30. May 2018 09:01 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1774126] Re: linux-oem: -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1774124
+ kernel-stable-phase-changed:Wednesday, 30. May 2018 09:03 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1774124
- kernel-stable-phase-changed:Wednesday, 30. May 2018 09:03 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-oem:  -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1774127] Re: linux-gcp: -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1774124
+ kernel-stable-phase-changed:Wednesday, 30. May 2018 09:03 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1774124
- kernel-stable-phase-changed:Wednesday, 30. May 2018 09:03 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

Title:
  linux-gcp:  -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1767452] Re: kernel oops when I undocked

[Anders Kvist]

Christopher, I believe the solution is in the redhat bug mentioned
earlier.

https://bugzilla.redhat.com/show_bug.cgi?id=1565131

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

Title:
  kernel oops when I undocked

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Here's a snippet from the kernel log which I think will make the
  actual issue clear:

  Apr 27 09:49:20 caliburn kernel: [ 4558.910412] pcieport :0a:03.0: 
Refused to change power state, currently in D3
  Apr 27 09:49:20 caliburn kernel: [ 4558.917717] xhci_hcd :0d:00.0: 
remove, state 1
  Apr 27 09:49:20 caliburn kernel: [ 4558.917724] usb usb6: USB disconnect, 
device number 1
  Apr 27 09:49:20 caliburn kernel: [ 4558.917725] usb 6-1: USB disconnect, 
device number 2
  Apr 27 09:49:20 caliburn kernel: [ 4558.917774] xhci_hcd :0d:00.0: xHCI 
host controller not responding, assume dead
  Apr 27 09:49:20 caliburn kernel: [ 4558.968688] xhci_hcd :0d:00.0: USB 
bus 6 deregistered
  Apr 27 09:49:20 caliburn kernel: [ 4558.968694] xhci_hcd :0d:00.0: 
remove, state 1
  Apr 27 09:49:20 caliburn kernel: [ 4558.968700] usb usb5: USB disconnect, 
device number 1
  Apr 27 09:49:20 caliburn kernel: [ 4558.968701] usb 5-3: USB disconnect, 
device number 3
  Apr 27 09:49:20 caliburn kernel: [ 4559.076020] usb 5-4: USB disconnect, 
device number 4
  Apr 27 09:49:20 caliburn kernel: [ 4559.076023] usb 5-4.2: USB disconnect, 
device number 5
  Apr 27 09:49:20 caliburn kernel: [ 4559.123365] usb 5-4.4: USB disconnect, 
device number 7
  Apr 27 09:49:20 caliburn kernel: [ 4559.125340] xhci_hcd :0d:00.0: Host 
halt failed, -19
  Apr 27 09:49:20 caliburn kernel: [ 4559.125343] xhci_hcd :0d:00.0: Host 
not accessible, reset failed.
  Apr 27 09:49:20 caliburn kernel: [ 4559.125467] xhci_hcd :0d:00.0: USB 
bus 5 deregistered
  Apr 27 09:49:21 caliburn kernel: [ 4559.146170] pcieport :0a:02.0: 
Refused to change power state, currently in D3
  Apr 27 09:49:21 caliburn kernel: [ 4559.147809] pcieport :0a:01.0: 
Refused to change power state, currently in D3
  Apr 27 09:49:21 caliburn kernel: [ 4559.149445] xhci_hcd :0b:00.0: 
remove, state 4
  Apr 27 09:49:21 caliburn kernel: [ 4559.149451] usb usb4: USB disconnect, 
device number 1
  Apr 27 09:49:21 caliburn kernel: [ 4559.149700] xhci_hcd :0b:00.0: USB 
bus 4 deregistered
  Apr 27 09:49:21 caliburn kernel: [ 4559.149706] xhci_hcd :0b:00.0: xHCI 
host controller not responding, assume dead
  Apr 27 09:49:21 caliburn kernel: [ 4559.149718] xhci_hcd :0b:00.0: 
remove, state 1
  Apr 27 09:49:21 caliburn kernel: [ 4559.149722] usb usb3: USB disconnect, 
device number 1
  Apr 27 09:49:21 caliburn kernel: [ 4559.149724] usb 3-1: USB disconnect, 
device number 2
  Apr 27 09:49:21 caliburn kernel: [ 4559.206497] usb 3-2: USB disconnect, 
device number 3
  Apr 27 09:49:21 caliburn kernel: [ 4559.462604] usb 3-4: USB disconnect, 
device number 4
  Apr 27 09:49:21 caliburn kernel: [ 4559.464185] BUG: unable to handle kernel 
NULL pointer dereference at 0034
  Apr 27 09:49:21 caliburn kernel: [ 4559.464193] IP: 
tty_unregister_driver+0xd/0x70
  Apr 27 09:49:21 caliburn kernel: [ 4559.464195] PGD 0 P4D 0 
  Apr 27 09:49:21 caliburn kernel: [ 4559.464197] Oops:  [#1] SMP PTI
  Apr 27 09:49:21 caliburn kernel: [ 4559.464199] Modules linked in: veth 
ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user 
xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc overlay hid_led hid_generic snd_usb_audio snd_usbmidi_lib usbhid 
cdc_ether usbnet r8152 mii bnep nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc 
snd_seq_midi snd_hda_ext_core snd_seq_midi_event arc4 snd_soc_sst_dsp 
intel_rapl snd_soc_sst_ipc snd_rawmidi x86_pkg_temp_thermal snd_soc_acpi 
intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_codec_conexant 
snd_hda_codec_generic kvm_intel snd_soc_core snd_compress ac97_bus kvm 
snd_pcm_dmaengine snd_seq irqbypass intel_cstate intel_rapl_perf snd_hda_intel 
joydev uvcvideo input_leds
  Apr 27 09:49:21 caliburn kernel: [ 4559.464233]  serio_raw snd_hda_codec 
thinkpad_acpi videobuf2_vmalloc videobuf2_memops nvram videobuf2_v4l2 iwlmvm 
snd_hda_core snd_hwdep videobuf2_core wmi_bmof intel_wmi_thunderbolt snd_pcm 
mac80211 snd_seq_device snd_timer videodev btusb media btrtl btbcm btintel 
iwlwifi mei_me bluetooth cfg80211 rtsx_pci_ms memstick snd ecdh_generic mei 
ucsi_acpi typec_ucsi intel_pch_thermal typec shpchp soundcore tpm_crb mac_hid 
acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 
algif_skcipher af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc i915 aesni_intel i2c_algo_bit aes_x86_64 
drm_kms_helper crypto_simd e1000e 

[Kernel-packages] [Bug 1772953] Re: linux-gcp: 4.13.0-1018.22 -proposed tracker

[Stefan Bader]

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1772956] Re: linux-oem: 4.13.0-1029.32 -proposed tracker

[Stefan Bader]

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

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

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

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

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

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

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

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