** 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: 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/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/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.
** 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
derivatives: bug 1832584
Oops. It appears upstream already fixed this bug. And we removed their
fix in Ubuntu (revert_nvidia_wayland_blacklist.patch in gdm3). If you
revert that revert then the bug is fixed.
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: gdm3
Public bug reported:
Hi,
The SACK Panic kernel update was uploaded into xenial-updates instead of
xenial-security:
https://packages.ubuntu.com/xenial-updates/linux-image-generic
normally I would expect this to be in the xenial-security component,
especially because this is a security update.
** 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 --
** Summary changed:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.15.0-1037.37 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** 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 1832573
** 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 1832560
** 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
derivatives: bug 1832500
** Summary changed:
- linux-gcp: -proposed tracker
+ linux-gcp: 4.15.0-1035.37~16.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
** 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
looks like no responses to v2, anything I can do to help move this
along? could it at least make it into an updated kernel build with
security patches, if not the ubuntu patch set?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-disco
** 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-1021.21~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
** 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 1832502
It's challenging for me to test mainline kernels because it means losing
access to ZFS, but I can probably do this later this week.
--
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/1832101
We got a potential fix thanks to TJ that seems to be working wonderfully from
what I can ascertain:
https://phab.lubuntu.me/D15
Download the raw diff, cd /etc/calamares, sudo patch --strip 2 <
/path/to/diff, and install like normal. Done!
--
You received this bug notification because you are a
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.4.0-1047.51 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** 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-signing-to-proposed
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
** 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
derivatives: bug 1832558
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1831103
Title:
bionic: netlink: potential shift
** 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.
** 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-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1832585
Title:
linux-raspi2:
Public bug reported:
Test failed with:
Error: Unknown device type.
Further inspection shows this has failed on the first line:
ip link add testdummy0 type dummy
It is because the KVM kernel does not have the dummy module:
$ sudo modprobe dummy
modprobe: FATAL: Module dummy not found in
** 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
** 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
derivatives: bug 1832584
Public bug reported:
[Impact]
Pointstick on HP ZBook 17 G5 doesn't work.
[Fix]
Let hid-multitouch know it has a pointstick, and exposes it as a mouse.
[Test]
With the fix applied the pointstick starts to work.
[Regression Potential]
Low. It's limited to one driver and limited to one specific
** 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
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 1833382
and then change the status of the bug to 'Confirmed'.
If, due to the
** 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-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1832589
Title:
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 1833387
and then change the status of the bug to 'Confirmed'.
If, due to the
Just to add my $.02 . . . I also had this problem with perhaps 6/12
daily and then I zsyncd what I think is the 6/15 daily . . . finding the
same "kernel panic" report as Dan found. A couple days later I
downloaded a fresh 19.04 iso and ran the install . . . and that went
well.
Glad to hear that
** Tags removed: apport-collected bionic verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1819485
Title:
x86: add
*** This bug is a duplicate of bug 1833439 ***
https://bugs.launchpad.net/bugs/1833439
** 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:
The patchset is significant already without knowing yet what is missing to
address the side-effect.
I would need kernel team review/approval before thinking to SRU this into
Ubuntu 4.15.
I can't SRU this as-is, now knowing this will introduce a regression.
I'll keep you guys posted.
- Eric
Just tried to cherry-pick 1) 6738028 and 2) ed9adb2 from 5.3-rc3 to bionic's
master-next tree:
git://kernel.ubuntu.com/ubuntu/ubuntu-bionic --branch master-next
1) applied cleanly, but 2) did not - I got 3 conflicts while cherry-picking
ed9adb2
Is there something still missing?
(I used bionic to
** Description changed:
- This is a bug.
+ [Impact]
- Test Environment:
+ * QEMU does not support IceLake and CascadeLake CPUs specific features.
+ * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR.
+ * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1811869
Title:
Alienware m15 takes very long to boot Ubuntu
Status
** 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:
** 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
*** This bug is a duplicate of bug 1833438 ***
https://bugs.launchpad.net/bugs/1833438
** 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:
** 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
-- swm properties --
Public bug reported:
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
derivatives: bug 1833436 (azure-kernel), bug
Public bug reported:
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 1833438 (bionic/linux-azure)
--
** 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1832582
Title:
linux-aws:
** 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 1832507
** 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)
** Changed in: kernel-sru-workflow/promote-to-proposed
** 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
derivatives: bug 1832581
I finally found 1st commit (not connected with USB problem) which prevents
booting, but it is corrected much later in 4.10-rc8.I don't know how to locate
correction commit for the one below
$ git bisect bad
174cc7187e6f088942c8e74daa7baff7b44b33c9 is the first bad commit
commit
** 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
+
** 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
derivatives: bug 1832581
** 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
derivatives: bug 1833436
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** 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:
Public bug reported:
sof driver need firmware and tplg to work.
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Assignee: Hui Wang (hui.wang)
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** 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
** Description changed:
This bug will contain status and test results related to a kernel source
Daniel van Vugt (vanvugt),
Do you know what change could have introduced this vmwgfx/wayland
interaction problem inside mutter in the first place ?
I have strong believe, that something userspace has been changed and no
longer interact well with the vmware driver since then.
Just to look at our
** Tags added: seg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1816743
Title:
Add systemd's kdump service command-line regardless if user provides
or not
** Tags added: seg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800566
Title:
Make the reset_devices parameter default for kdump kernels
Status in makedumpfile package in
** Tags added: seg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile
** Tags added: seg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800873
Title:
Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-
line
Status in
** Tags added: seg
--
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/1813651
Title:
hpsa: DMAR invalid read
Status in linux package in Ubuntu:
Confirmed
Status in linux source package
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-disco
** 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-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.
https://bugzilla.redhat.com/show_bug.cgi?id=1693960#c60
Scroll:
Page Up or Page Down before you scroll
Slider:
Slide from edge towards center (for example window itself :) )
All hints at same basic underlying logic
mistake, something simple.
>:]
--
You received this bug notification
** 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 1832560
** 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:
** 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.
** 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 --
or if we identify the offending userspace change, then we can look at
the kernel again with and try to find what bit are missing, and if we
limit the kernel change then maybe the side-effect might not be present
again. (assumption here)
I think the next step is really to find what userspace
of if we identify the offending userspace change, then we can look at
the kernel again and try to find what bit are missing, and if we limit
the kernel change then maybe the side-effect won't be present too.
I think the next step is really to find what userspace change started
all this so we can
** Description changed:
- == SRU ==
+ == SRU [Xenial][Bionic][Cosmic][Disco][Eoan] ==
== Justification ==
When accessing page frames that are greater than max_pfn using the idle-
page sysfs interface an oops is triggered that kills the process that
writes to the sysfs interface.
** 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.
** 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/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
backports: bug 1832547
I have tested this patch in virtualbox and it works for me.
--
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/1829805
Title:
Lubuntu Eoan Daily Image fails to boot after install on KVM
Public bug reported:
== SRU ==
== Justification ==
When accessing page frames that are greater than max_pfn using the idle-
page sysfs interface an oops is triggered that kills the process that
writes to the sysfs interface.
== Fix ==
Upstream fix currently in linux-next:
** 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 1832504
** 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/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
** Description changed:
- sof driver need firmware and tplg to work.
+ [Impact]
+ We have a couple dell and lenovo laptops which have dmic directly connected
+ to PCH, this needs intel sof driver to work, and intel sof driver is merged
+ oem-osp1-b kernel and it needs to load firmware and
** 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
derivatives: bug 1832581
** 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: 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: 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.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Project changed: kernel => ubuntu
** No longer affects: ubuntu
--
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 1832082
and then change the status of the bug to 'Confirmed'.
If, due to the
To continue on my comment #59 ... One user has been impacted on a
physical machine (non-vmware) with the same symptom but can't provide
public details unfortunately, but I witnessed the problem from my own
eye via remote session, and again upgrading to 4.18 kernel did the
trick.
So it really
** Summary changed:
- linux-fips: -proposed tracker
+ linux-fips: 4.4.0-1013.17 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
Verfied fix by reporter
** Tags removed: amd64 apport-bug apport-collected verification-needed-xenial
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.
I tested with Kernel:
Linux tor3 4.4.0-149-generic #175+lp1824687v4 SMP Mon May 27 17:21:02 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
IPv6 is enabled and the system is under usual load.
No crashes in 24h.
For me this is a clear indication that the problem is fixed. Before there where
crashes all
Kai-Heng: thanks for the suggestion, bluetooth now switches on & I can
pair with devices.
Output of "dmesg | grep -i bluetooth" looks healthier too:
martin@martin-N15-17RD:~$ dmesg | grep -i bluetooth
[ 18.577708] Bluetooth: Core ver 2.22
[ 18.577724] Bluetooth: HCI device and connection
1 - 100 of 173 matches
Mail list logo
