** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** 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/1734130
Title:
[18.04 FEAT] Add kvm_stat f
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-propo
Is this fix released in artful & bionic too?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730596
Title:
s390/mm: fix write access check in gup_huge_pmd()
Status in Ubuntu on IBM z Sy
** 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/1738219
Title:
the kernel is blackholing IPv6 packets to linkdown next
** Information type changed from Private to Public
** 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/1734130
Title:
[18.04
The fix for this bug made it into Zesty via bug 1716491.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1711104
Title:
[P9][Ubuntu 16.04.03] Additional PMU fixes for P9
Status in The Ub
Can you confirm that Zesty with the latest updates and at least the
Ubuntu-4.10.0-38 resolves this bug?
** No longer affects: perforate (Ubuntu Zesty)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Public bug reported:
My machine (XPS 13 9360) won't go into suspend properly after upgrading
from linux-image-4.13.0-17-generic to linux-image-4.13.0-19-generic.
This affects both suspend through lid close and "systemctl suspend".
Screen goes off, power led remains lit. Then after some time the s
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1716491
Title:
New PMU fixes for marked events.
Status in The Ubu
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 1738219
and then change the status of the bug to 'Confirmed'.
If, due to the nature
You have been subscribed to a public bug:
My machine (XPS 13 9360) won't go into suspend properly after upgrading
from linux-image-4.13.0-17-generic to linux-image-4.13.0-19-generic.
This affects both suspend through lid close and "systemctl suspend".
Screen goes off, power led remains lit. Then
SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088920.html
** Description changed:
+
+ == SRU Justification ==
+ This issue was first reported on the netdev email list by Lennart Sorensen:
+ https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html
+
Yes, these commits will also land in the HWE kernels.
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Zesty)
Status: New => In Progress
** Cha
Public bug reported:
When the 'ignore_routes_with_linkdown' sysctl is set, we should not
consider linkdown nexthops during route lookup.
While the code correctly verifies that the initially selected route
('match') has a carrier, it does not perform the same check in the
subsequent multipath sele
SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088912.html
** Also affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Description changed:
+ == SRU Justification ==
+ Artful uses the
This is a brand new laptop that shipped with windows 10. This is the
first time trying to install. I will proceed with newest kernel.
existing is 4.13.0-19-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-xenial
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-propo
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1737515
Title:
linux-aws: 4.4.0-1044.53 -prop
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1737511
Title:
linux: 4.4.0-104.127 -proposed tra
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1737512
Title:
linux-aws: 4.4.0-1006.6 -propo
*** This bug is a duplicate of bug 1738147 ***
https://bugs.launchpad.net/bugs/1738147
** This bug has been marked a duplicate of bug 1738147
Cherry Trail & USB 3.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738152
T
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 kernel[
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1738178
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1706033
Title:
[P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw bre
** Changed in: linux (Ubuntu Artful)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Zesty)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Status: Incomplete => In P
Can you give the latest 4.13 upstream stable kernel a try:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.16/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1737316
Title:
Having in
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1737512
Title:
linux-aws: 4.4.0-1006.6 -pr
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1737515
Title:
linux-aws: 4.4.0-1044.53 -p
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1737511
Title:
linux: 4.4.0-104.127 -proposed
I wonder what ist done to prevent any other Lenovo über to run into that
issue. As it is not yet sure if this issue can be solved, Canonical
should do something to make sure that no other Lenovo owner installs or
updates to 17.10, no matter if it's their fault at all.
--
You received this bug not
** 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/1738073
Title:
thunderx2: i2c driver PEC and ACPI clock fixes
St
** Changed in: systemd (Ubuntu Artful)
Status: Confirmed => Fix Committed
** Changed in: systemd (Ubuntu Artful)
Status: Fix Committed => In Progress
** Changed in: systemd (Ubuntu Artful)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notificat
** Description changed:
Hi all,
Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.
It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.
Moreover (and most important) US
And just to illustrate my point, on 4.14.0 vanilla:
while true; do
dd if=/nfsmount/debian-live-9.1.0-amd64-xfce+nonfree.iso bs=16M iflag=direct
2>/dev/null | sha1sum; done
With rx offload on (default):
489ed92b17aa9a4582899356d3123621b5d92189 -
742462292c76189f63fc3e7af1acc9dec56c0a8d -
f11b
This is happening even on my 9560 with 4.13.9 vanilla; when running a
background rsync backup job, packages downloaded in a Debian docker
build frequently do not match their checksum and need multiple runs to
succeed.
--
You received this bug notification because you are a member of Kernel
Packag
** 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 se
** 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
**
** 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 se
** Also affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux-oem (Ubuntu)
Statu
** Also affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
St
** Also affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux-oem (Ubuntu)
Statu
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux-oem (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu Xenial)
Status: New =>
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 1738178
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1706033
Title:
[P9, Power NV][ WSP][Ubuntu 16.04.03] : pe
Public bug reported:
In the ubuntu_ecryptfs test suite, it constantly fail with 28 test cases
on all s390x instances (zVM / zKVM / Ubuntu on LPAR) with Xenial kernel.
miscdev-bad-count.sh.xfs 3 sec Failed
extend-file-random.sh.xfs 5 sec Failed
trunc-file.sh.xfs 3 sec Fail
Seeing very similar symptoms on Ubuntu 17.10 running 4.13.0-19-generic or
4.14.0-041400-generic.
Sometimes, but not every time, BT is not available after resuming from suspend.
>From other data sources, the root cause is a lack of .reset_resume
handler in the BT driver.
A possible interim fix (w
** 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/1737942
Title:
linux: 4.10.0-43.47 -prop
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1737515
Title:
linux-aws: 4.4.0-1044.53
** Attachment removed: "0D5EAE0F25F0BA20.jpg"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/839157/+attachment/4920575/+files/0D5EAE0F25F0BA20.jpg
** Attachment removed: "A7435C9644AEB554.jpg"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/839157/+attachment/4994317/+files/A74
** 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
And to answer your question - it is a fresh install on a new machine,
didn't work before.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1737226
Title:
Bluetooth module doesn't work prop
IIRC touchpad on XPS 9343 should use I2C.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1737639
Title:
Touchpad stopped working in Dell XPS13
Status in linux package in Ubuntu:
Confi
--- Comment From praveen.pan...@in.ibm.com 2017-12-14 03:49 EDT---
Hi ,
I verified this on kernel available on
http://kernel.ubuntu.com/~jsalisbury/lp1706247/artful/ and able to
allocate 16GB huge pages number .
ubuntu@ltc-garri3:~$ cat /proc/cmdline
root=UUID=9db8977d-1eec-4245-b1d9-b4f
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/1738152
Title:
generic/308 for xfs in xfstest
Well...
Seconds after my previous message it happened again.
So it seems the upstream kernel does not fix the problem.
I'm adding GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=250"
again.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Inc
@ #3:
I installed the latest upstream kernel and will report back with the
results.
uname -r
4.15.0-041500rc3-generic
I assumed it would also make the most sense to remove the
GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=250"
parameter to see if the upstream kernel fixes the p
Public bug reported:
This test case (generic/308) will hang on i386 system and gets killed
when our timeout setting kicks-in.
Discussion could be found here:
https://lkml.org/lkml/2015/9/26/466
The patch in the mail thread was not applied.
I think we need to update our repo first to see if this
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/1738147
Title:
Cherry Trail & USB 3.0
Status
Public bug reported:
Disk I/O error
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-19-generic 4.13.0-19.22
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.13
101 - 162 of 162 matches
Mail list logo
