** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
--
You received this bug notification because you
Would it be possible for you to do a kernel bisection?
First, find the last good -rc kernel and the first bad -rc kernel
between v4.16-rc1 to v4.18, from http://kernel.ubuntu.com/~kernel-
ppa/mainline/
Then,
$ sudo apt build-dep linux
$ git clone
Please raise the issue to alsa-de...@alsa-project.org for ALSA
maintainers' awareness.
--
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/1773697
Title:
[USB-Audio - PX USB, playback]
That's pretty much all you can do unless you're capable of writing
drivers or reading ACPI tables yourself.
--
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/1795292
Title:
ELAN469D touch
All that seems to happen here is that you make me try new BIOSes and
kernels as they come out. Disappointing.
--
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/1795292
Title:
ELAN469D
[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.
[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.
*** This bug is a duplicate of bug 1791032 ***
https://bugs.launchpad.net/bugs/1791032
** This bug has been marked a duplicate of bug 1791032
Failed to compile lttng module on small Azure nodes
--
You received this bug notification because you are a member of Kernel
Packages, which is
That is the problem then. If the kernel can't get EDID data from your
monitor then it has no idea what the supported resolutions are.
First, please try unplugging and re-plugging your monitor a few times.
If that doesn't fix it then please also try a different monitor cable if
you can.
Second,
Also, please try:
sudo cat /sys/class/drm/*/edid
--
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/1799035
Title:
[SKL] My ubuntu doesn't show resolution above 1024x768
Status in linux
out of cat /sys/class/drm/*/edid is blank
--
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/1799035
Title:
[SKL] My ubuntu doesn't show resolution above 1024x768
Status in linux package
It's true. Linux kernel v4.19 support touchpad. Also scroll works.
--
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/1781879
Title:
Latest ASUS trackpad doesn't work in Ubuntu
Status in
It looks like your kernel command line has a custom backlight change,
which is unusual:
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic
root=UUID=fd7306d2-c2eb-414c-bf34-7e6c72a1fe79 ro quiet splash
acpi_backlight=vendor vt.handoff=1
Maybe try:
1. Removing the
** Package changed: xorg (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/1799228
Title:
USB-ports do not work
Status in linux package in Ubuntu:
Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799228
Title:
USB-ports do not work
Status
You have been subscribed to a public bug:
brightness controller gone after installing nvidia drivers
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules:
You have been subscribed to a public bug:
Two out of 3 USB-ports are not regognized anymore (i.e. when I insert a
USB-stick, it will not be shown in Nautilus). I tried various
workarounds from ubuntuusers, but they were not successful. Among them
to use "dpkg-reconfigure x-server". X-org now
** Changed in: oem-priority
Importance: Critical => High
--
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/1773940
Title:
Enable AMD PCIe MP2 for AMDI0011
Status in HWE Next:
New
** 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
Successfully upgraded to 4.19. Stress-ng memory test passed without lockup
issue. New rebuild kernel 4.19 has fixed the issue. Refer to text below:
---
ubuntu@fluent-orca:~$ uname -r
4.19.0-041900rc8-generic
ubuntu@fluent-orca:~$ sudo stress-ng -k --aggressive --verify --timeout 300
'kernel-fixed-upstream'
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1798127
Title:
CPU Soft Lockups when stress-ng stack stressor runs with M.2 NVMe as
root FS
Status in linux
@dr-strangehate
Sorry if this is an obtuse question, but you are saying that this
problem owes to a bug in the Linux 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/1791427
Title:
Texted to NVidia support about the issue. Got reply
Your case is being escalated to our Level 2 Tech Support group. The
Level 2 agents will review the case notes and may attempt to recreate
your issue or find a workaround solution if possible. As this process
may take some time we ask that you be
-- cosmic testing --
ubuntu@starbuck:~$ uname -a
Linux starbuck 4.18.0-10-generic #11~lp1799281+cosmic.1 SMP Mon Oct 22 21:45:47
UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@starbuck:~$ for i in {1..500}; do sudo modprobe -r ipmi_ssif; sleep 2s ;
sudo modprobe ipmi_ssif || exit; done
--
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1791427
Title:
Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
Carbon
This has been an issue ever since I have used this laptop with any distribution
of Linux. Up until 18.10 with touchpad would be non-functional. It would jump
all over the screen and would basicaly be unusable with the laptop. Since
18.10. and kernel 4.17.4 the touchpad works as far as no longer
** Description changed:
I upgrade from 18.04 to 18.10 and now the desktop does not start on a
fresh boot. The console output ends with "Starting GNOME Display
Manager". I cannot switch VTs, my keyboard and mouse are unresponsive
though RESUIB sequence works to reboot. If I remote login
Qualcomm released new firmware recently that's worth checking out:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/qca?id=534daf431c88b24236d23572039cdd79223b246a
--
You received this bug notification because you are a member of Kernel
Packages, which is
5 days ago I've installed Ubuntu 16.0.1 with kernel 4.4.0-21-generic on
the second disk. No updates to kernel or libs were installed. So far no
fan issue appeared. Also, 16.04 correctly goes to sleep when lid is
closed which was not always the case with 18.04.
Also, probably not related, but I
btusb.enable_autosuspend=0 seems to have worked (so far)...
--
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/1796553
Title:
BT mouse getting reset during operation
Status in Linux:
Oops, sorry for typo. Ubuntu 16.04.1
--
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/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in
Public bug reported:
I upgrade from 18.04 to 18.10 and now the desktop does not start on a
fresh boot. The console output ends with "Starting GNOME Display
Manager". I cannot switch VTs, my keyboard and mouse are unresponsive
though RESUIB sequence works to reboot. If I remote login using ssh,
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 1799237
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799237
Title:
mprotect fails on ext4 with dax
Status in
*** This bug is a duplicate of bug 1752772 ***
https://bugs.launchpad.net/bugs/1752772
Same problem in 4.15.0-38-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1759644
Title:
--- Comment From stefan.ra...@de.ibm.com 2018-10-22 16:40 EDT---
According to https://legacy.python.org/dev/peps/pep-0373/, end of life for
Python 2.7 was moved to 2020 - that's still a wee bit!
Still, since kvm_stat should be Python 3 compatible by now, why not just go a
head and try to
I see nothing that needs translation.
--
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/1799277
Title:
package linux-modules-extra-4.15.0-38-generic 4.15.0-38.41 failed to
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799039
Title:
Apple Facetime HD PCI (Broadcom 1570) not accessible
Status in linux package in
** Changed in: linux (Ubuntu)
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/1799277
Title:
package linux-modules-extra-4.15.0-38-generic
Thank you for taking the time to report this issue and helping to make
Ubuntu better. We noticed that some of the sentences in this bug report
are not in English. If they were translated to English they would be
more understandable to triagers. Could you please translate them?
** Changed in:
** 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
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 1799281
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1799276
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
I'm pretty sure it was Sophos Antivirus that screwed things up.
Don't get me started on why I have that piece of crap installed.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-modules-extra-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu
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/1799277
Title:
package
Public bug reported:
[Impact]
If you attempt to remove and insert the ipmi_ssif module a number of times, it
would result in a kernel panic. This is due to mod_timer from arming a timer
that was already removed by del_timer during module unload.
[Fix]
In linux-next:
0711e8c1b457 ipmi: Fix
Public bug reported:
[Impact]
The IPMI spec states:
The purpose of the SPMI Table is to provide a mechanism that can be used
by the OSPM (an ACPI term for “OS Operating System-directed
configuration and Power Management” essentially meaning an ACPI-aware OS
or OS loader) very early in the boot
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: ubuntu-z-systems
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
This bug was fixed in the package linux-kvm - 4.15.0-1025.25
---
linux-kvm (4.15.0-1025.25) bionic; urgency=medium
* linux-kvm: 4.15.0-1025.25 -proposed tracker (LP: #1797065)
[ Ubuntu: 4.15.0-38.41 ]
* linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
* Silent data
Yes , It seems that bug is still not fixed
FYI - We also observed page fault in 4.18 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/1795453
Title:
IO's are issued with incorrect
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => 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
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
So with the script we are able to re-create the panic on one of our
systems. Which is good because I was not yet able to extract anything
from the uploaded dump (using makedumpfile to convert from kdump_flat
format seems to fail finding an end marker).
Generally from the data seen so far all
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => 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
This bug was fixed in the package linux - 4.4.0-138.164
---
linux (4.4.0-138.164) xenial; urgency=medium
* linux: 4.4.0-138.164 -proposed tracker (LP: #1795582)
* Linux 4.4.155 stable release build is broken on ppc64 (LP: #1795662)
- powerpc/fadump: Return error when fadump
Public bug reported:
Hi,
I am on Ubuntu 16.04 and kernel version 4.4.0-137.
I am facing issue with the cursor going haywire while typing.
What could be possible fix for the same?
VERSION :
lsb_release -rd
Description:Ubuntu 16.04.5 LTS
Release:16.04
Thanks
** Affects: linux
The issue began after a fresh system install on a new computer.
Admittedly, the first system I installed was Qubes, with Fedora (24 I
believe). When I decided Qubes wasn't adequate for my needs, I wiped
the system (reformatted using gparted) and installed the latest Ubuntu
(as of a month ago).
This bug was fixed in the package linux - 3.13.0-161.211
---
linux (3.13.0-161.211) trusty; urgency=medium
* linux: 3.13.0-161.211 -proposed tracker (LP: #1795595)
* CVE-2017-0794
- scsi: sg: protect accesses to 'reserved' page array
- scsi: sg: reset 'res_in_use' after
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => 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
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Invalid
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Tags removed: block-proposed-bionic
** Tags removed: block-proposed
--
You received this bug notification because you
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux - 4.15.0-38.41
---
linux (4.15.0-38.41) bionic; urgency=medium
* linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
* Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
-
@jsalsbury We are still seeing the issue, given ridsaim has not replied
lets move forward. I'd like to get some movement on this issue without
marking as a Field Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux-gcp - 4.15.0-1023.24
---
linux-gcp (4.15.0-1023.24) bionic; urgency=medium
* linux-gcp: 4.15.0-1023.24 -proposed tracker (LP: #1797062)
[ Ubuntu: 4.15.0-38.41 ]
* linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
* Silent data
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
There may be a possible fix already available so converting this to a
question
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/linux/+question/675460
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1797062 ***
https://bugs.launchpad.net/bugs/1797062
This bug was fixed in the package linux-gcp - 4.15.0-1023.24
---
linux-gcp (4.15.0-1023.24) bionic; urgency=medium
* linux-gcp: 4.15.0-1023.24 -proposed tracker (LP: #1797062)
[ Ubuntu:
*** This bug is a duplicate of bug 1797080 ***
https://bugs.launchpad.net/bugs/1797080
This bug was fixed in the package linux-gcp - 4.15.0-1023.24~16.04.1
---
linux-gcp (4.15.0-1023.24~16.04.1) xenial; urgency=medium
* linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker (LP:
This bug was fixed in the package linux-gcp - 4.15.0-1023.24~16.04.1
---
linux-gcp (4.15.0-1023.24~16.04.1) xenial; urgency=medium
* linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker (LP: #1797080)
[ Ubuntu: 4.15.0-38.41 ]
* linux: 4.15.0-38.41 -proposed tracker (LP:
This bug was fixed in the package linux - 4.15.0-38.41
---
linux (4.15.0-38.41) bionic; urgency=medium
* linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
* Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
-
This bug was fixed in the package linux - 4.15.0-38.41
---
linux (4.15.0-38.41) bionic; urgency=medium
* linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
* Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
-
This bug was fixed in the package linux - 4.15.0-38.41
---
linux (4.15.0-38.41) bionic; urgency=medium
* linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
* Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
-
This bug was fixed in the package linux - 4.15.0-38.41
---
linux (4.15.0-38.41) bionic; urgency=medium
* linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
* Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
-
This bug was fixed in the package linux - 4.15.0-38.41
---
linux (4.15.0-38.41) bionic; urgency=medium
* linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
* Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
-
This bug was fixed in the package linux - 4.15.0-38.41
---
linux (4.15.0-38.41) bionic; urgency=medium
* linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
* Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
-
With the 4.18.0-8-generic kernel, I see AMD IOMMU IO_PAGE_FAULTs for invalid
addresses
AMD-Vi: Event logged [IO_PAGE_FAULT device=e1:00.0 domain=0x
address=0xfffd14c0 flags=0x0030]
PERC controller is still present btw, but the vdbench stress crashed due
to this page faults.
**
I see the disks going offline during stress in mainline
4.19.0-041900rc7-generic as well.
Although the symptoms look different in 4.15 and 4.18 kernels, I feel
the bug is not fixed; address being accessed is still out-of-range in
this 16GB server.
--
You received this bug notification because
*** This bug is a duplicate of bug 1797061 ***
https://bugs.launchpad.net/bugs/1797061
This bug was fixed in the package linux - 4.15.0-38.41
---
linux (4.15.0-38.41) bionic; urgency=medium
* linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
* Silent data corruption in
** 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/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
This bug was fixed in the package linux - 4.15.0-38.41
---
linux (4.15.0-38.41) bionic; urgency=medium
* linux: 4.15.0-38.41 -proposed tracker (LP: #1797061)
* Silent data corruption in Linux kernel 4.15 (LP: #1796542)
- block: add a lower-level bio_add_page interface
-
1 - 100 of 246 matches
Mail list logo
