** Description changed:
- Steps:
- 1. Installed system and log in.
- 2. Do something on M715q-RR-1 or let it idle
- 3. Verify the system once per 10 minutes
+ [Impact]
+ On the machine of Lenovo M715, there is an AMD GPU (1022:15dd rev ca), when it
+ switchs to amdgpufb, the system will hang
** Tags added: originate-from-1789802 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/1796789
Title:
the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev
ca,
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 1796789
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Steps:
1. Installed system and log in.
2. Do something on M715q-RR-1 or let it idle
3. Verify the system once per 10 minutes
Actual result:
System got hang during working.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
** Summary changed:
- screen displays normally on the lenovo M715 with the AMD GPU (Radeon Vega 8
Mobile, rev ca, 1002:15dd)
+ screen displays abnormally on the lenovo M715 with the AMD GPU (Radeon Vega 8
Mobile, rev ca, 1002:15dd)
** Description changed:
- Steps:
- 1. Installed system.
- 2.
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1796346
Title:
linux: 4.18.0-9.10 -proposed
[Expired for linux (Ubuntu Cosmic) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Cosmic)
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 Bionic) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Bionic)
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.
[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.
[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 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 1796786
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Steps:
1. Installed system.
2. Verify the screen in the P2 of installation.
Actual result:
Screen displays abnormally, please refer to the picture in attachment.
Expected result:
Display should be good in all stage.
** Affects: hwe-next
Importance: Undecided
Also, the kernel does recognise the keys:
Event: time 1539010310.047487, -- SYN_REPORT
Event: time 1539010313.623520, type 1 (EV_KEY), code 229 (KEY_KBDILLUMDOWN),
value 1
Event: time 1539010313.623520, -- SYN_REPORT
Event: time
did a test on a hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
gui screen shows blue background, lubuntu (logo) and dots (normal plymouth)
text screen shows
[ 99.99] ehci-pci :00:1d.0:dma_direct_map_sg: overflow
0x000223ad7000+2048 of device mask
scrolling by
repeated course bisect, now got something more reasonable:
4.8 fail
4.9 fail
4.10 - ok
4.11 - ok
4.12 - ok
4.14 - ok
4.18 - ok
--
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/1796250
I've tested the proposed kernel under the previous test environment -
after two hours the host was still up, where as it would have previously
crashed within 30 minutes or so. As such, this appears to prevent the
panic.
--
You received this bug notification because you are a member of Kernel
Found patch [0] fixing module build. Observe the same behavior.
[0]
https://www.hlmjr.com/index.php/2018/08/21/nvidia-drivers-390-77-vs-linux-kernel-4-18
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is
After upgrading from 18.04 to 18.10 the gnome freezes after GDM login.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot
Yes it is started right after the upgrade from 18.04. 18.04 with the
latest SW was running just fine (on kernel 4.15.0-36-generic). Have not
seen it working on 18.10.
Tried 4.19-rc7.
Observations:
* Update manager "enables" driver, but it is not loaded
* Manual install of nvidia-driver-390
Haven't asked for a new wifi card yet, as I don't think it's the
hardware. But I might get annoyed enough to try.
--
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/1793997
Title:
test on Bionic
--
original:
$ uname -a
Linux mfo-sf194734 4.15.0-37-generic #40-Ubuntu SMP Tue Oct 2 15:36:54 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
Public bug reported:
error processing archive
/var/cache/apt/archives/libnvidia-compute-390_390.77-0ubuntu0.18.04.1_amd64.deb
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also
in package nvidia-340 340.106-0ubuntu3
Errors were encountered while
** Also affects: linux-signed-hwe (Ubuntu)
Importance: Undecided
Status: New
--
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/1796542
Title:
Silent corruption in Linux
** 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/1796748
Title:
regression in 'ip --family bridge neigh' since linux
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 1796748
and then change the status of the bug to 'Confirmed'.
If, due to the
Ah yes, cold boot seems to fix it for now. I'll need to wait and see if
the bug now occurs during normal operation.
--
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/1790454
Title:
** Description changed:
[Impact]
- * Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
+ * Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
- * Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
-such request/family
** Summary changed:
- regression in 'ip --family bridge neigh' since linux v4.12+
+ regression in 'ip --family bridge neigh' since linux v4.12
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
test on unstable:
-
original:
$ uname -a
Linux mfo-sf194734 4.19.0-1-generic #2 SMP Mon Oct 8 14:38:01 -03 2018
x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
test on Cosmic
--
original:
$ uname -a
Linux mfo-sf194734 4.18.0-9-generic #10-Ubuntu SMP Fri Oct 5 16:49:44 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
$ bridge fdb show
33:33:00:00:00:01 dev ens3 self permanent
01:00:5e:00:00:01 dev ens3 self permanent
Public bug reported:
[Impact]
* Netlink RTM_GETNEIGH requests for PF_BRIDGE are broken since linux
v4.12.
* Users, tools (e.g., iproute2), and libraries (e.g., go netlink) that use
such request/family currently receive nothing back in the kernel response.
* The upstream fix resolves the
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1796730
Title:
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.19-rc7
*** This bug is a duplicate of bug 1796730 ***
https://bugs.launchpad.net/bugs/1796730
** This bug has been marked a duplicate of bug 1796730
Ubuntu 18.10 regression: nvidia driver does not work
--
You received this bug notification because you are a member of Kernel
Packages, which is
*** This bug is a duplicate of bug 1796730 ***
https://bugs.launchpad.net/bugs/1796730
** This bug is no longer a duplicate of bug 1796726
Ubuntu 18.10 regression: nvidia driver does not work
** This bug has been marked a duplicate of bug 1796730
Ubuntu 18.10 regression: nvidia driver
It seems this fix also fixes the touch screen not working (no irq storm)
after a suspend on an Acer Aspire Switch 11 (and possibly also other
modules).
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796580
--
You received this bug notification because you are a member of Kernel
bellajohsan (bellajohsan),
I am booting from a USB key into RAM. That boot fails as per
screenshots.
Power source and storage are immaterial.
This is not an Acer issue.
To all, could it be UEFI related? I tried to disable this in BIOS, but
that option is not available.
--
You received this
Good call, thanks!
This turns out to be fixed in the latest mainline kernel. Looking at the
git log for the i2c_hid driver, I found this commit which I suspect is
the fix for my problem.
https://github.com/torvalds/linux/commit/52cf93e63ee672a92f349edc6ddad86ec8808fd8
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/1796743
Title:
Ubuntu 18.10 - Alienware 17
*** This bug is a duplicate of bug 1796726 ***
https://bugs.launchpad.net/bugs/1796726
** This bug has been marked a duplicate of bug 1796726
Ubuntu 18.10 regression: nvidia driver does not work
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
If the machine goes to sleep, either because I close the lid or because
it idles too long, it ends up in a weird state when I try to resume. If
I press the power/Alien button, the fan runs and the keyboard/trackpad
light up but nothing happens.
Ultimately I need to hard
** Also affects: linux-hwe-edge (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-edge (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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.19-rc7
*** This bug is a duplicate of bug 1796726 ***
https://bugs.launchpad.net/bugs/1796726
Data collected by "ubuntu-bug linux", while system was using proprietary
nvidia driver can be found in bug 1796730
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
Extra info for bug 1796433
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-8-generic 4.18.0-8.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
*** This bug is a duplicate of bug 1796726 ***
https://bugs.launchpad.net/bugs/1796726
** This bug has been marked a duplicate of bug 1796726
Ubuntu 18.10 regression: nvidia driver does not work
--
You received this bug notification because you are a member of Kernel
Packages, which is
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/1796726
Title:
Ubuntu 18.10 regression:
** Description changed:
- Extra info for bug 1796433
+ Problems started after upgrade to 18.10 and first reboot.
+ Symptoms:
+ * Login screen appears
+ * After providing credentials desktop does not start
+
+ Part of dmesg:
+ -
+ ...
+ [
Public bug reported:
Extra info for bug 1796433
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-8-generic 4.18.0-8.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
Submitted bug 1796726
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1796433
Title:
Ubuntu 18.10 regression: nvidia driver does not work
Status in
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
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/1796720
Title:
High GPU temperature after
this report is from running lm-sensor when system is idle:
kernel 4.18.0.8
amdgpu-pci-6500
Adapter: PCI adapter
vddgfx: +0.77 V
fan1: 974 RPM
temp1:+30.0°C (crit = +94.0°C, hyst = -273.1°C)
power1:6.11 W (cap = 48.00 W)
kernel 4.18.0.9.10
amdgpu-pci-6500
Public bug reported:
Hello,
Today I have received an update for Linux kernel which upgraded the
kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after
restart I noticed that the GPU temperature is abnormally High...
Before Update:
- GPU fan set to off on idle
- GPU idle
*** This bug is a duplicate of bug 1794428 ***
https://bugs.launchpad.net/bugs/1794428
This bug was fixed in the package linux-oem - 4.15.0-1021.24
---
linux-oem (4.15.0-1021.24) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use
This bug was fixed in the package linux-oem - 4.15.0-1021.24
---
linux-oem (4.15.0-1021.24) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of
*** This bug is a duplicate of bug 1794433 ***
https://bugs.launchpad.net/bugs/1794433
This bug was fixed in the package linux-kvm - 4.18.0-1002.2
---
linux-kvm (4.18.0-1002.2) cosmic; urgency=medium
* linux-kvm: 4.18.0-1001.1 -proposed tracker (LP: #1795413)
*
This bug was fixed in the package linux-kvm - 4.18.0-1002.2
---
linux-kvm (4.18.0-1002.2) cosmic; urgency=medium
* linux-kvm: 4.18.0-1001.1 -proposed tracker (LP: #1795413)
* Miscellaneous Ubuntu changes
- kvm: [Config] CONFIG_HARDENED_USERCOPY=y
- kvm: [Config]
This bug was fixed in the package linux-oem - 4.15.0-1021.24
---
linux-oem (4.15.0-1021.24) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of
*** This bug is a duplicate of bug 1795413 ***
https://bugs.launchpad.net/bugs/1795413
This bug was fixed in the package linux-kvm - 4.18.0-1002.2
---
linux-kvm (4.18.0-1002.2) cosmic; urgency=medium
* linux-kvm: 4.18.0-1001.1 -proposed tracker (LP: #1795413)
*
This bug was fixed in the package linux-kvm - 4.18.0-1002.2
---
linux-kvm (4.18.0-1002.2) cosmic; urgency=medium
* linux-kvm: 4.18.0-1001.1 -proposed tracker (LP: #1795413)
* Miscellaneous Ubuntu changes
- kvm: [Config] CONFIG_HARDENED_USERCOPY=y
- kvm: [Config]
*** This bug is a duplicate of bug 1794428 ***
https://bugs.launchpad.net/bugs/1794428
This bug was fixed in the package linux-oem - 4.15.0-1021.24
---
linux-oem (4.15.0-1021.24) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use
This bug was fixed in the package linux-oem - 4.15.0-1021.24
---
linux-oem (4.15.0-1021.24) bionic; urgency=medium
[ Ubuntu: 4.15.0-36.39 ]
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of
This bug was fixed in the package linux-kvm - 4.18.0-1002.2
---
linux-kvm (4.18.0-1002.2) cosmic; urgency=medium
* linux-kvm: 4.18.0-1001.1 -proposed tracker (LP: #1795413)
* Miscellaneous Ubuntu changes
- kvm: [Config] CONFIG_HARDENED_USERCOPY=y
- kvm: [Config]
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1795595
Title:
linux: 3.13.0-161.211
** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1796641
Title:
linux-oem:
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1795572
Title:
linux-kvm: 4.15.0-1024.24
Kai-Heng Feng: I did some more testing and I don't see the problem in the
cosmic proposed kernel 4.18.0-9.10.
1) the live CD appeared to boot fine, but I didn't totally trust the test
procedure.
2) I installed cosmic 4.18.0-9.10 from
** 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/1793753
Title:
kernel panic - null pointer dereference
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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/1795583
Title:
linux-aws: 4.4.0-1032.35
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.19-rc7
** 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
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.19-rc7
Hello,
It would be possible to create this report with:
$ ubuntu-bug linux
To add all the necessary technical information
Thanks for helping to create a better Ubuntu...
--
Cristian Aravena Romero (caravena)
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Confirmed =>
The error appears to be different that the error posted in the bug
description. The descriptions mentions a tx_timeout. Are you seeing
that error still as well?
Also, the descriptions seems to indication this is a regression. Was
there a specific prior kernel version that did not exhibit this
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** 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
Thanks for all the testing, Chris. It leaves me a little baffled.
That said, to Joseph et al, two questions:
1. This seems to be the same messages from 1794922 but slightly different
symptoms. Should they be considered as the same?
2. With the kernel apparently working in Bionic, that
** Bug watch added: Linux Kernel Bug Tracker #201291
https://bugzilla.kernel.org/show_bug.cgi?id=201291
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=201291
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19-rc7 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not
There's something wrong going on here. I first reported this issue as a
'linux' bug, based on a hasty reading of documentation. I never
finished that report, so I expect that to be incomplete.
Shortly afterwards I re-reported it as a probable NetworkManager issue.
It seems that these two issues
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => 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/1762385
Title:
dell_wmi: Unknown key codes
Status in OEM
Hmmm, do you still see this if you cold boot with the quirk?
--
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/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
Status
** Changed in: ubuntu-power-systems
Status: Triaged => 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/1792195
Title:
Signal 7 error when running GPFS tracing in
Marking as "Incomplete" while waiting for test kernel results to be
posted.
** Changed in: ubuntu-power-systems
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Marking as "Incomplete" while waiting for test kernel results to be
posted.
** Changed in: ubuntu-power-systems
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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-cosmic
** Tags removed: block-proposed
--
You received this bug notification
*** This bug is a duplicate of bug 1757008 ***
https://bugs.launchpad.net/bugs/1757008
Hello,
Was able to get this to load.
This is a new install of ubuntu 18.04.
Had to run the "install -f" cmd a few times, then the updates worked.
Mark Dannunzio
> On October 7, 2018 at
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
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.
Since we are already on kernel 4.18.0.8.9 in cosmic that incl. the mentioned
patches:
$ git log --oneline | grep "Check if IOMMU page is contained in the pinned
physical page"
76fa497 KVM: PPC: Check if IOMMU page is contained in the pinned physical page
fheimes@T570:~/ubuntu-cosmic$ git tag
Since we are at kernel level 4.18.0.8.9 in cosmic that incl. the fix:
$ git log --oneline | grep "cpuidle: powernv: Fix promotion from snooze if next
state disabled"
0a4ec6a cpuidle: powernv: Fix promotion from snooze if next state disabled
$ git tag --contains 0a4ec6a
Ubuntu-4.18.0-7.8
That already in the current cosmic kernel:
$ git log --oneline | grep "Check if IOMMU page is contained in the pinned
physical page"
76fa497 KVM: PPC: Check if IOMMU page is contained in the pinned physical page
$ git tag --contains 76fa497
Ubuntu-4.18.0-7.8
Ubuntu-4.18.0-8.9
Ubuntu-4.18.0-9.10
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-power-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.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-power-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.
This is now broken also on Hyper-V VMs, tested with 4.18.0-8-generic and
daily 18.10 server
--
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/1794477
Title:
[Azure] Accelerated networking
As this ticket only relates to Xenial and 4.4 kernel, marking as "Fix
Released".
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
** Changed in: systemd (Ubuntu Xenial)
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/1762385
Title:
dell_wmi: Unknown key codes
Status in OEM Priority
** Tags added: kernel-bug-reported-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/1794763
Title:
High utilisation of memory freezes Ubuntu completely for a long time,
with an
1 - 100 of 172 matches
Mail list logo
