@ltraeger, the patch above, that's part of disco, only works in combination
with a z14 (and again a pretty recent firmware level). It doesn't change the
situation on z13 or z13s.
So z14 (or z14 ZR1) is a prerequisite.
--
You received this bug notification because you are a member of Kernel
Marking this as Triaged / Low, as it seems to be only caused by these
unusual options.
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1823116
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which
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/1823116
Title:
Upgrade to 19.04 fails with
more or less, though AIUI the xserver changes aren't necessary if the
kernel support is there
--
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/1714178
Title:
Triple 4K monitor display
i915 is loaded just fine on your first journal log:
Mar 25 23:26:06 zlink2 kernel: [drm] Initialized i915 1.6.0 20181204 for
:00:02.0 on minor 0
but it's happening after lightdm is started, so I'd say it's lightdm
which is just being too hasty
** Changed in: xorg-server (Ubuntu)
Public bug reported:
Upgrade to 19.04 Ubuntu MATE fails with following:
Could not install 'linux-image-5.0.0-8-generic
triggers looping, abandoned
Could not install the upgrades
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
a little digging and plymouth is supposed to work with drm modesetting
drivers which means i915 has to be loaded for it to work .. so not
seeing it means ..some hardware detection has failed .. is that part of
plymouth or something else?
since it works on the upgraded install on sda1 I suspect a
[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
[Expired for wayland (Ubuntu) because there has been no activity for 60
days.]
** Changed in: wayland (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been
no activity for 60 days.]
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Kernel module will load if added to /etc/ modules .. I have my sda1
partition running kernel 5.0.0-8.9 as are the iso's tested recently .. my
sda1 partition loads i915 without using /etc/modules.. I notice that the
recent isos do not show Plymouth progress screen at startup..is that
relevant?
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
Public bug reported:
My system:
ubuntu 18.04
gnome desktop
4GB RAM
Nvidia GT 630
kernel 4.15.0-47-generic (but happened with all the kernels before as well)
TWO MONITORS, attached to the video card with DVI / HDMI (I think this is
important...)
When resuming from hibernate, the machine powers
@Vamshee
Can you provide more details what you did and what did not work?
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => AaronMa (mapengyu)
** Tags added: disco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Tags added: regression-testing-passed
--
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/1820326
Title:
linux-fips: 4.4.0-1007.9 -proposed tracker
Status in Kernel SRU Workflow:
In
@Stephan
Following comment #28, I have re-packaged linux-firmware package to
include the firmwares from the two upstreams:
[1]
https://people.canonical.com/~ypwong/lp1818881/linux-firmware_1.173.3test1_all.deb
[2]
Also, are you able to change any settings in your BIOS to prevent wakeup
from Bluetooth?
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
It sounds like you've found a good workaround but I am curious about the
root cause here.
It seems the Bluetooth mouse might be emitting events even when you
don't touch it..? Are you able to try a different model of Bluetooth
mouse?
** Summary changed:
- Intel NUC (8I3BEH1) wakes up
If I understand it correctly, to completely resolve this issue, we will
need mesa + xserver + kernel fix, but currently only mesa fix is in
place, right?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Summary changed:
- External monitor turns off for short period of times / until moving mouse
+ External monitor turns off for short period of times / until moving mouse
when using kernel options i915.enable_gvt=1 intel_iommu=on
** No longer affects: gnome-shell (Ubuntu)
--
You received
Separately, the "tick" and "thud" may be related to bug 1821663.
--
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/1822426
Title:
19.04 Built in Intel HDA sound is disabled upon resume
Please also try step 2 from comment #2.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => 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/1822426
Title:
19.04 Built in
Can you please try some older kernel versions and tell us if any of
those avoid the bug?
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You
@venturia,
No need to do more tests.
Thanks.
--
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/1821663
Title:
[regression][snd_hda_codec_realtek] repeating crackling noise after
19.04
If you're sure that's the problem then we would need to figure out which
kernel version it started in. Please try some different kernel versions:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
and see if you can find the two closest versions where one doesn't have
the bug and the
2. Actually maybe use this image (higher quality): https://user-
images.githubusercontent.com/15329494/44345316-4c2d8700-a493-11e8-8691-6e9d0978fdcc.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Jeb,
We first need some more information from you to verify we're looking in
the right place. Please:
1. Log into "Ubuntu" (not "Ubuntu on Wayland") so as to ensure you are
using Xorg.
2. Open this image in a new tab or window: https://news-
I tested this today using 5.0.0-8-generic and between reboots I am still
getting different MAC addresses on Z13.
--
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/1646805
Title:
MAC
** Changed in: ubuntu-power-consumption
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/1808108
Title:
nvidia-drm.modeset=1 incurs very high CPU usage in
@Mike
Many Thanks for your answer.
The PCI-X is a 4 ports with 2 channels.
The PCIe is 7 ports with an unknown number of channels.
The PCI-X was intended to be used with a HP Proliant for external Backup
purpose which is running Ubuntu Server 18.04 LTS. No more PCIe slots are
available because
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
@kaihengfeng, I cc'ed you:
https://bugzilla.kernel.org/show_bug.cgi?id=203147 (upstreamed because I
produced it outside of Ubuntu)
** Bug watch added: Linux Kernel Bug Tracker #203147
https://bugzilla.kernel.org/show_bug.cgi?id=203147
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
Kai-Heng Feng
I switched to Ubuntu 16.04.2 based on 4.8 as a base LTS is better. I've tested
kernel v4.9-rc8 as bisect good and v4.10-rc8 as bisect bad but I get:
$ git bisect good v4.9-rc8
$ git bisect bad v4.10-rc8
Some good revs are not ancestor of the bad rev.
git bisect cannot work
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1822792
Just rerun this on the same iso as above (beta) and this time wireless
was found.
Putting this down as a glitch.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** 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
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** 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
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1822790
After reverting https://patchwork.freedesktop.org/series/58893/ (commit
d179b88deb3bf6fed4991a31fd6f0f2cad21fab5 upstream kernel drm/i915/fbdev)
and rebuilding default disco kernel 5.0.0-8-generic everything works as
expected. Possible regression in upstream kernel.
--
You received this bug
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1822792
** 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
I can confirm that this works. Thank you Thiago!
--
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/1817225
Title:
18.04.2 breaks xrdp
Status in linux package in Ubuntu:
Confirmed
Status
@Hui: I've installed the package as per comment #19 (sorry for the typo at #20)
and this has fixed the problem.
I've skipped the instructions at #12. Do you need additional tests?
A-
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1822787
** 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
@Hui: I've installed the package as per comment #18 and this has fixed the
problem.
I've skipped the instructions at #12. Do you need additional tests?
A-
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks Chris for your reply, but my machine is x86 :-(
I will try with other distro. :-(
--
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/1794922
Title:
lubuntu 18.10 x86 (32bit) image
** 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
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1822817
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1822795
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-trusty
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-nouveau (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/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
** 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
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1822832
This seems to be an old bug with uswsusp, which is an old package:
https://bugzilla.kernel.org/show_bug.cgi?id=75101
I think I first started using it because it was easier to set up and I
heard it was better for nvidia proprietary modules.
** Also affects: uswsusp (Ubuntu)
Importance:
Okay I found a way to get it working, first I gave up of uswsusp and
runned:
apt remove --purge hibernate uswsusp.
I basically followed this: https://askubuntu.com/a/1064114
but changed to:
resume=/dev/disk/by-uuid/70d967e6-ad52-4c21-baf0-01a813ccc6ac (just
the uuid wouldn't work so the path
** 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
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => 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/1821863
Title:
Need to add Intel CML related pci-id's
On 2019-04-03 03:06:09, thighland wrote:
> I encountered this issue on xenial after updating to Azure's 4.15 kernel
> for testing. We started encountering an apparmor deny which doesn't
> happen on the latest 4.4 kernel. I had missed setting the k flag for a
> policy, and everything worked on the
Public bug reported:
After replacing my USB mouse with a BT mouse, I noticed my machine would
no longer suspend without immediately waking up. i.e. I suspend and see
the light go into the slow fade in and out for one cycle and then goes
solid and the display wakes up again. If I disable BT (via
I see that this is a result of LP #1764794, I've adjusted my copy
debian-installer source package to compensate (using bionic version as a
template).
This however, should be fixed for xenial if there is going to be another
point release.
** Summary changed:
- xenial 4.4.0-145 image udeb
Public bug reported:
The payload in the xenial package kernel-signed-image-4.4.0-145-generic-
di_4.4.0-145.171_amd64.udeb doesn't have the proper suffix and
overwrites the unsigned version of the same kernel image:
(from data.tar.xz from the package):
./
./boot/
./boot/vmlinuz-4.4.0-145-generic
Kai-Heng Feng (kaihengfeng),i built kernel with commit
ed14acd316bae2d3365f71ea9941490a71d3adf2.
I was lucky and from the first attempt the bug was fixed =) Current
kernel version 4.18.12+.
Need to test the other two commits?
--
You received this bug notification because you are a member of
systemctl hibernate
--
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/1819915
Title:
s2disk freezes at saving image to disk (hibernation)
Status in linux package in Ubuntu:
Confirmed
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
I don't have these problems with Windows on the device, either.
I really hope a fix gets implemented. Thank you.
On Tue, Apr 2, 2019, 10:45 PM Daniel van Vugt
wrote:
> Thanks for the animation.
>
> I think that flicker is occurring in the LCD itself. The reason is that
> the old gradient (which
** 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/1822897
Title:
RDMA/hns updates for disco
Status in linux
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Thank you
On Tue, Apr 2, 2019, 10:58 PM Jaap-Willem Dooge <
jaap-willem.do...@outlook.com> wrote:
> Yep, same issue here on Ubuntu 18.10, 4.18.0-16-lowlatency kernel.
>
> If relevant:
> CPU: AMD A10-5800K
> GPU: AMD GeForce GTX 660
> RAM: 8GB DDR3
> DE/WM: GNOME 3.30.2 + GNOME Shell
> Mouse:
Please try the attached package. I believe you should be able to install
it alone; none of the other packages look to be locked to a specific
version of linux-cloud-tools-common.
** Attachment added:
"linux-cloud-tools-common_5.0.0-8.9+lp1820063v201904031200_all.deb"
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-cosmic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
Besiades my BIOS is not U/EFI I also experience the lag keyboard (connected to
PS/2 port) in grub:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668105
--
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/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Changed in: linux (Ubuntu)
Status: New => 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/1823056
Title:
autopkgtests run too often, too much and don't skip
Public bug reported:
[Impact]
* linux autopkgtest should only execute either rebuild tests, when triggered
by toolchain.
or execute regression suite when triggered by meta
but never both. As otherwise, it results in false negative results for the
kernel
[Test Case]
* Trigger adt test
I modified your script to perform 5000 reboots. I'm up to 3508 reboots
now without hitting the bug. I'll let it run for a while longer. I'll
also compare our environments to see if there is a difference.
--
You received this bug notification because you are a member of Kernel
Packages, which
@Kai-Heng Feng
The last stable for me was v4.9 not any single version v4.10 nor v4.10-rc* is
bootable!
--
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/1822363
Title:
Booting hangs when
Why the xhci_hcd module which is unstable driver itself and works with many
unstable USB 3.0 controllers and devices (with bugs) is compiled in kernel and
cannot be easoly disabled???
It is insane script-kiddie unprofessional kernel development.
--
You received this bug notification because
@Fabien
Some FWs over the net are for 2 port and some for 4-port. I had
situation after Windows Application FW upgrade, that card was programmed
wrongly as 2 channel 4 port instead of 1 channel 2 port card resulted in
yellow Windows mark after every reboot. It was with 2.0.2.6 FW. Please
rollback
Are really you using uswsusp? (hibernate command), pm-utils (pm-
hibernate) or systemctl hibernate?
--
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/1819915
Title:
s2disk freezes at
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-cosmic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Summary changed:
- linux-azure: -proposed tracker
+ linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
Hi, Josh.
The changes are already applied and will be included in this current
cycle. Let us know if you have found any issues with the test kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
Small update for a quick workaround on hanging touchpad:
Instead of unloading/loading kernel modules a quicker way is to go to a
terminal screen and back to X11:
- Press to enter terminal mode
- Press to go back to X11
Note that the F-keys can differ, this works on Fedora 29 with Cinnamon
and
Public bug reported:
Built-in nvme is required for support of hibernation to nvme devices;
This change is needed only for linux-aws-xenial (bionic and up already
have these as built-in).
+CONFIG_BLK_DEV_NVME=y
+CONFIG_NVMEM=y
** Affects: linux-aws (Ubuntu)
Importance: High
Assignee:
Your upgrade is done, but for the record, installing the HWE kernel
doesn't remove the old kernel. So you still have the option to go back
to that in the GRUB menu.
Also, once you're sure the HWE kernel is working, you'll probably want
to remove the linux-image-generic package so you're not
There are too many possible commits in PCI and USB between v4.9 and
v4.10.
For situation like this I'll do a bisection between v4.10-rc8 and v4.10
first to find out what commit makes v4.10 be able to boot.
--
You received this bug notification because you are a member of Kernel
Packages, which
Thanks Aaron.
My X1CG6 does have no problems with the trackpad when I use S2idle sleep
- well, except power consumption. Still: I did not know that, 'From 5.0
kernel power consumption of s2idle is less than 1w, pretty much like S3
0.6w.' On the other hand, that is a difference of some 30%.
Thanks - I upgraded the server which was receiving the ZFS snapshot and
things _seem_ to be working well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772412
Title:
zfs 0.7.9
related branch
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco/+ref/amd-iommu-cherrypick
** Also affects: linux (Ubuntu Disco)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: In Progress
** Changed in: linux (Ubuntu Cosmic)
Assignee:
Public bug reported:
[Impact]
If a device has an exclusion range specified in the IVRS table, this region
needs to be reserved in the iova-domain of that device. This hasn't happened
until now and can cause data corruption on data transfered with these devices.
Treat exclusion ranges as
1 - 100 of 213 matches
Mail list logo
