Yes, this kernel works as expected, thanks.
I presume that despite this being marked as Artful the fix will get into
Xenail hwe releases. Is this correct?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Changed in: ubuntu-z-systems
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages,
Fix released (zero crash reports after 15.04)
** Changed in: bluez (Ubuntu)
Status: Confirmed => Fix Released
--
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/1493481
Title:
blueto
Fix released (zero crash reports after 15.04)
--
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/1493528
Title:
bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state
from s
Fix released (zero crash reports after 15.04)
** Changed in: bluez (Ubuntu)
Status: Confirmed => Fix Released
--
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/1493528
Title:
blueto
** Changed in: ubuntu-z-systems
Status: Fix Committed => 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/1747639
Title:
[18.04 FEAT] Automatically detect layer2 settin
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1755470
Title:
[P9,Power N
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Importance: Undecided => High
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel
You have been subscribed to a public bug:
== Comment: #0 - JENIFER HOPPER - 2018-03-14 16:20:47 ==
+++ This bug was initially created as a clone of Bug #163375 +++
---Problem Description---
All KVM guest cpu utilization is being reported as sys% time in the host.
It turns out Guest time accounti
--- Comment From shriy...@in.ibm.com 2018-03-15 01:00 EDT---
Updating for reference :
===
Also verified on bionic kernel : 4.15.0-10-generic #11-Ubuntu
and Perf version is : perf version 4.15.3
root@ltc-boston122:~# perf list | grep pm_
power:dev_pm_qos_add_request
I fixed this in qa-r-t differently, I'd prefer to know the exact config used in
each kernel version:
https://git.launchpad.net/qa-regression-testing/commit/?id=9ea99cecf8f023478c64d3e66b88dbba24738649
Closing. Thanks for the report!
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for trackin
With the test triggered yesterday on the same box, the system has passed with
the enosys test:
12:33:56 DEBUG| [stdout] enosys STARTING
12:34:01 DEBUG| [stdout] enosys RETURNED 0
Also the file-ioctl test:
12:34:41 DEBUG| [stdout] file-ioctl STARTING
12:34:46 DEBUG| [stdout] file-ioctl RET
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
*** This bug is a duplicate of bug 1754059 ***
https://bugs.launchpad.net/bugs/1754059
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package linux - 4.15.0-12.13
---
linux (4.15.0-12.13) bionic; urgency=medium
* linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)
* CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings
* ppc64e
This bug was fixed in the package debian-installer - 20101020ubuntu534
---
debian-installer (20101020ubuntu534) bionic; urgency=medium
* Move master kernels to 4.15.0-12. LP: #1754059
-- Dimitri John Ledkov Thu, 15 Mar 2018 00:14:05
+
** Changed in: debian-installer (Ubunt
171d8b9363725e122b164e6b9ef2acf2f751e387 looks good. The next test is
with 4681ee21d62cfed4364e09ec50ee8e88185dd628.
4.4.0-116(xenial) - bad (9 of 31 - 29.0%)
v4.12-rc2 - bad (15 of 53 - 28.3%)
v4.12-rc3 - bad (24 of 90 - 26.6%)
v4.12.0-041200rc1 #201803141333 - relatively good (1 of 217 - 0
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1755302
Title:
Ubuntu 17.10 freezes randomly
Hello, your logs show more errors than I'm accustomed to seeing;
consider running fwts or fwts-frontend, or looking for firmware updates
from your system vendor.
Thanks
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1753227
Title:
Ubuntu 17.10 freezes randomly
** Description changed:
- Steps:
- 1) install bto and boot into OS
- 2) check sound setting,
- 3) Plugin headset
- 4) check external microphone
+ == SRU Justification ==
+ We have a OEM bug #1727951, in this bug, The Dell OptiPlex 7460 AIO can't
+ detect external mic and can't record sound via ext
Hello, your logs have more complaints about firmware errors than I'm
accustomed to seeing. Wild guess, maybe try the firmware test suite
package 'fwts' or 'fwts-frontend' on your system. Maybe your hardware
vendor has updated BIOS you can try?
Thanks
** Information type changed from Private Secur
** 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 up
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 1755954
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Steps:
1) install bto and boot into OS
2) check sound setting,
3) Plugin headset
4) check external microphone
Expected results: external microphone should wrok well
Actual results: No external microphone be detected
** Affects: hwe-next
Importance: Critical
St
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1754059
Title:
linux: 4.15.0-12.13 -proposed tracker
** Branch linked: lp:~ubuntu-core-dev/debian-installer/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/1754059
Title:
linux: 4.15.0-12.13 -proposed tracker
Status in Kernel SRU Wo
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 1755941
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Yes, with 4.16-rc4 and 4.16-rc5 the problem persists. Every kernel
version after 4.15-rc5 is making the computer lose connectivity after
returning from suspension.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
h
Public bug reported:
HDMI audio out is available after suspend/sleep, but I am using a Radeon
video card with Audio/Video through HDMI. I have video, but no audio.
Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
lspci
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar
** Changed in: kernel-sru-workflow/security-signoff
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/1755208
Title:
linux: 4.4.0-117.141 -propose
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/tree/kernel/sysctl.c#n2433
and
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/tree/kernel/sysctl.c#n2446
are the source(s) of the noise
Looking at nearby functions like proc_dointvec_ibrs_ctrl an
A new test kernel with commit 651438bb0af is also available here:
http://kernel.ubuntu.com/~jsalisbury/lp1753371
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1753371
Title:
Ubuntu 18.0
Request submitted for inclusion in Bionic:
https://lists.ubuntu.com/archives/kernel-team/2018-March/090807.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1753371
Title:
Ubuntu 18.04
*** This bug is a duplicate of bug 1180649 ***
https://bugs.launchpad.net/bugs/1180649
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sbsigntool (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of K
*** This bug is a duplicate of bug 1180649 ***
https://bugs.launchpad.net/bugs/1180649
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Thank you Leann!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1755627
Title:
ibrs/ibpb fixes result in excessive kernel logging
Status in linux package in Ubuntu:
Confirmed
Status i
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => Triaged
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Canoni
Here's the issue:
The newer kernels have the retpoline Spectre mitigation. You're going to
need to rebuild your nvidia.ko kernel module with a patched version of
the stock distribution gcc.
Here is the bug:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1750937
--
You received this bug not
--- Comment From jhop...@us.ibm.com 2018-03-14 16:28 EDT---
Thanks, I verified the test kernel fixes the bug.
To do so, I ran the specjbb2005 benchmark in a pinned guest with base
page backing and compared that to a pinned guest with 2MB hugepage
backing. On the stock 4.15.0-10 kernel, the
959.acd706b851), linux-signed-image-generic:amd64
(4.13.0.36.38, 4.13.0.37.40), papirus-icon-theme:amd64
(20180311-2268+pkg18~ubuntu17.10.1, 20180314-2272+pkg18~ubuntu17.10.1),
linux-signed-generic:amd64 (4.13.0.36.38, 4.13.0.37.40),
firefox-locale-en:amd64 (59.0~b14+build1-0ubuntu0.17.10.1,
59.0+bui
It keeps popping. I have no idea whats going on. it is not like an emergency.
However, it might be related to Bluetooth. It acts wieredOn Wednesday,
March 14, 2018, 10:01:00 AM MDT, Joseph Salisbury
wrote:
Do you have a way to reproduce this bug, or was it a one time event?
** Changed
-theme:amd64
(20180311-2268+pkg18~ubuntu17.10.1, 20180314-2272+pkg18~ubuntu17.10.1),
linux-signed-generic:amd64 (4.13.0.36.38, 4.13.0.37.40),
firefox-locale-en:amd64 (59.0~b14+build1-0ubuntu0.17.10.1,
59.0+build5-0ubuntu0.17.10.1), firefox-locale-nl:amd64
(59.0~b14+build1-0ubuntu0.17.10.1, 59.0+build5
Just updated to 4.13.0-37 kernel, problem remains
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1752946
Title:
System freezes on copy to USB drive since kernel 4.13.0-36 (32bit)
Status
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1750810
Title:
qeth: fix calculation of required buffer elements
** Tags added: cdo-qa-blocker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1753662
Title:
[i40e] LACP bonding start up race conditions
Status in linux package in Ubuntu:
Triaged
Sta
** Changed in: linux (Ubuntu Artful)
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1748901
Title:
System hang with Virtualbox & kernel 4.13.0-32-gen
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
This bug was fixed in the package zfs-linux - 0.7.5-1ubuntu6
---
zfs-linux (0.7.5-1ubuntu6) bionic; urgency=medium
* Fix ARC hit rate (LP: #1755158)
- Upstream fix, commit 0873bb6337452e3e028e40f5dad945b30deab185,
fixes issue that can impact ARC hit rate especially with a
** Changed in: ubuntu-z-systems
Status: Triaged => 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/1755712
Title:
Ubuntu18.04 - KVM on S390 - Multiple epoch facility
I built the next test kernel, up to the following commit:
4681ee21d62cfed4364e09ec50ee8e88185dd628
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1753662
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
Also, to call it out again, this appears to affect Trusty's LTS kernel,
too (it's not clear how one marks a bug as such from the Launchpad UI)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
I built a test kernel with commit 36447456e1cca853188505f2a964dbbeacfc7a7a.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1755804
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both the linux-image and
li
For the sake of completeness on this one, I installed the following
mainline packages on an AWS m5.large instance running 16.04.3 w/
4.4.0-112-generic
- linux-headers-4.16.0-041600rc4_4.16.0-041600rc4.201803041930_all.deb
- linux-headers-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
--
You received this bug notification becau
** 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/1755857
Title:
devpts: handle bind-mounts
Status in linux package in
Don't appear to be able to find the appropriate log in Ubuntu - however
grepping journalctl there for blue* gives me:
journalctl |grep blue*
Mar 14 17:51:27 ubuntu NetworkManager[985]: [1521049887.5999] Loaded
device plugin: NMBluezManager
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device
4.15.0-12.13-generic from bionic-proposed is also working for me.
Relevant CPU model info (same as in description):
cpu family : 6
model : 142
model name : Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
stepping: 9
microcode : 0x84
Model 142 corresponds to 0x8E in hex,
It's worth noting, too, that this does not happen on Bionic @ 4.15
(using Ubuntu 4.15.0-1001.1-aws 4.15.3) but it does happen on Trusty
(using Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Returning to confirmed status - easily reproducible with LTS kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1755627
Title:
ibrs/ibpb fixes result in excessive kernel logging
St
4.15.0-12.13-generic, from bionic-proposed, fixes this bug for me due to
it containing this upstream commit:
1751342095f0d2b36fa8114d8e12c5688c455ac4
Relevant CPU model info from /proc/cpuinfo:
cpu family : 6
model : 78
model name : Intel(R) Core(TM) m5-6Y54 CPU @ 1.10GHz
ste
We use LTS kernels, so no - unfortunately we cannot.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
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 1755857
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Hey everyone,
I sent a few patches to fix a regression caused by wrong behavior in the
devpts filesystem when used with the TIOCGPTPEER ioctl() we implemented
a while back. The context and reproducer can be taken from my following
commit message. The required patches are in G
Oh sorry, it would be great if we could cherry-pick these as this
currently breaks users. Sorry for all the pre-release extra work this
causes. :)
Christian
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
I'm able to interact with the system normally using the ctrl-alt-F3
terminal, although none of the methods listed in
https://askubuntu.com/questions/455301/how-to-restart-gnome-shell-after-
it-became-unresponsive-freeze/496999 properly restart gnome-shell. It
seems to be related to graphics.
--
The test is still in progress, but so far
171d8b9363725e122b164e6b9ef2acf2f751e387 looks good (0 of 21). Since I
already downloaded the kernel locally, please go ahead to build the next
one. Thanks,
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
And what if I can't boot into 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/1734147
Title:
corrupted BIOS due to Intel SPI bug in kernel
Status in Linux:
Unknown
Status in li
1 - 100 of 191 matches
Mail list logo
