Test result without CONFIG_KALLSYMS and CONFIG_KALLSYMS_ALL enabled:
ubuntu@gummo:~$ sudo cat /proc/modules
signpost 12288 - - Live 0x (OE)
fuse 77824 - - Live 0x
kvm_intel 180224 - - Live 0x
btrfs 819200 - - Live 0x
xor 20480 - -
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => 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 associated
for whatever reason 'ubuntu-bug /var/crash/YOURFILE.crash' doesn't provide an
URL or open a browser window :(
I'll attache the .cash file here
** Attachment added: "_usr_lib_bluetooth_bluetoothd.0.crash"
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports:
derivatives:
** Affects:
Now that 18.04 out now, can we have new build of the packet?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1759628
Title:
bluez regression: Bluetooth audio fails to reconnect after
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => 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/1766614
Title:
linux-aws:
In that case please also send us your package listing (dpkg -l).
** 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.
https://bugs.launchpad.net/bugs/1767124
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.4.0-1018.18 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
Public bug reported:
Since upgrading to kernel 4.15, my laptop (HP Elitebook 850 G3) lasts
less than one hour on a fully charged battery. On Ubuntu 17.10 with
kernel 4.13, the autonomy was typically in excess of 5 hours.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1767075/+attachment/5128283/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1767075/+attachment/5128281/+files/CRDA.txt
--
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/1767075
I can confirm, with the kernel you send the atlantic driver is working again!
Will you send your commit upstream? 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/1767088
Title:
apport information
** Tags added: apport-collected
** Description changed:
On a 18.04 test system, there is BUG in the nfs-kernel-server. If
multiple shares are exported, each share can be mounted from another
computer or via network on the same server. BUT, looking inside the
mounted
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1734243
Title:
Intel 9260/9462/9560 firmware support
Status in HWE
and with the workaround from bug 994921, it refuses to report the bug
because it's not an official kde package (well for sure it is not...)
and I have to remove some third party packages...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** 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
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/1767324
Title:
Extreme regression in battery
This commit [1] might solve it. Can you git it a try?
[1]
https://github.com/torvalds/linux/commit/53fa1f6e8a5958da698a31edf366ffe90596b490
--
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/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status
Kernel 4.15.0-15-generic #16~lp1761751v2: Boots normally
--
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/1761751
Title:
Black screen on 18.04 + AMD RX460
Status in linux package in
Damn, just missed out. :/ Thanks Daniel. :)
Looks like there's only very minor changes in 1.10.5, so judging by the
criteria for SRU it shouldn't be too hard. I'll get onto a bug report
for that at some point, it at least can (hopefully) make it into the
18.04.2 release Live CD. Will be a bit of
Hi
I'm having similar symptons to the original issue after upgrading from
17.10 -> 18.04
Specifically:
I'm able to boot past GRUB and login.
Shortly after login the UI becomes unresponsive
Then the mouse freezes
Then completely dead.
My laptop is similar to the original post: Dell XPS 15
As
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1767075/+attachment/5128286/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1767075/+attachment/5128289/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1767075/+attachment/5128285/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1767075/+attachment/5128291/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1767075/+attachment/5128284/+files/Lspci.txt
--
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/1767075
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1767075/+attachment/5128288/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1767075/+attachment/5128290/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1767075/+attachment/5128287/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1767075/+attachment/5128282/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Please try this one:
https://people.canonical.com/~khfeng/lp1728244-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/1728244
Title:
Touchpad stops working after reboot on Apollo
** Also affects: linux-meta-oem (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-meta-oem (Ubuntu)
Status: New => Invalid
** Changed in: linux-meta-oem (Ubuntu Xenial)
Status: New => Fix Committed
--
You received this bug notification because you are a
Hmm, having resigned to building my own kernels for the foreseeable
future, I DL'd the source tree for bionic and took a peek at xhci-pci.c
It looks like someone has tried to incorporate the patch of interest. I
find:
if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
That would be because you failed to apply a workaround for bug 994921.
It might require some tweaking :/
But lucky for you we did get enough info from the crash file:
Stacktrace:
#0 agent_get (owner=owner@entry=0x0) at src/agent.c:267
agent =
#1 0x55922049561b in
The test kernel can be found here:
http://people.canonical.com/~phlin/kernel/lp-1764980/
--
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/1764980
Title:
Having the same issue with 16.04 LTS using 4.13.0-* kernels
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1647511
Title:
During kernel upgrade, /usr/sbin/dkms falsely reports that
WARNING: CPU: 1 PID: 39 at
/build/linux-5s7Xkn/linux-4.15.0/drivers/gpu/drm/drm_vblank.c:1073
drm_wait_one_vblank+0x181/0x190 [drm]
Modules linked in: ums_realtek uas usb_storage i915 i2c_algo_bit drm_kms_helper
ahci psmouse libahci 8139too syscopyarea 8139cp sysfillrect sysimgblt pata_acpi
** 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
kernel 4.15.0-20, backported to 16.04:
install is okay, BUT no boot (kernel panic); afterwards, the kernel is
uninstallable!
The same behaviour is found with kernel 4.19.0-19 for bionic.
Had to remove the .postinit, .postrm, etc. files in /var/lib/dpkg/info/
in order to be able to use the apt
Public bug reported:
I am reporting this using the most recent auto updated version of the
kernel linux-image-4.4.0-122-generic. But boot also fails on the two
previous auto updated images linux-image-4.4.0-121-generic and linux-
image-4.4.0-119-generic.
Last bootable kernel was
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1766728
Title:
update linux-base on xenial
Status in linux-base package in
*** This bug is a duplicate of bug 1742698 ***
https://bugs.launchpad.net/bugs/1742698
** This bug has been marked a duplicate of bug 1742698
zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build
--
You received this bug notification because you are a member of Kernel
Packages,
Do you get a notice in dmesg when you don't specify the version at mount
time?
On Fri, Apr 27, 2018, 03:05 Walter Cheuk wrote:
> Same problem happened to Ubuntu 16.04.5. I have to specify "vers=1.0" to
> mount a NAS drive successfully. The help said the default version is
>
Public bug reported:
SCENARIO: I have just upgraded to 18.04 from 17.10
PROBLEM PACKAGE (?): linux-modules-4.15.0-20-generic
REPORT FROM 'dmesg' shows this typical error:
[ 899.040146] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]]
*ERROR* [CRTC:41:pipe B] flip_done timed out
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/1767356
Title:
Long boot time (approx 5
--- Comment From indira.pr...@in.ibm.com 2018-04-27 08:14 EDT---
(In reply to comment #211)
> - We have decided to replace the qlogic by Emulex.
> - Apply the new kernel patch in 208.
> - add the slub_debug=FZPU
> System is up with latest kernel and ready now.
> root@boslcp3:~# uname -a
>
Public bug reported:
Version 16.04 Ubunutu - bug appears to be back for newer zfs/ubuntu
update (not rolling to 18.04 - just installing updates to 16.04)
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: zfs-dkms 0.6.5.6-0ubuntu20
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic
can you flash a newer bios ?
can you find the latest kernel not affected by that issue ?
--
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/1767356
Title:
Long boot time (approx 5
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/1767360
Title:
16.04 LTS boot failure with
--- Comment From dougm...@us.ibm.com 2018-04-27 07:33 EDT---
(In reply to comment #211)
> - We have decided to replace the qlogic by Emulex.
> - Apply the new kernel patch in 208.
> - add the slub_debug=FZPU
> System is up with latest kernel and ready now.
> root@boslcp3:~# uname -a
>
The same issue happens starting with the kernel 4.14.36 (also exists
with the 4.14.37) on Ubuntu 16.04 x64, note that 4.14.35 installed fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
here we go...
** Attachment added: "output of dpkg -l"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1767124/+attachment/5128438/+files/dpkg-l.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-April/092020.html
** Description changed:
+ == SRU Justification ==
+ Linux kernel 4.15 has introduced a bug in e1000e msix interrupt drivers,
+ which violates the e1000e specification. Specifically, the driver
+
** 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:
FWIW, I verified that Tycho's microcode revision is what's expected for
his CPU:
142: sig 0x000306d4, pf mask 0xc0, 2018-01-18, rev 0x002a, size 18432
I don't think his lockups are due to running a previously published
microcode revision that Intel pulled or any bad interactions with the
4.15
Public bug reported:
Here's a snippet from the kernel log which I think will make the actual
issue clear:
Apr 27 09:49:20 caliburn kernel: [ 4558.910412] pcieport :0a:03.0: Refused
to change power state, currently in D3
Apr 27 09:49:20 caliburn kernel: [ 4558.917717] xhci_hcd :0d:00.0:
I built a test kernel with the two commits pointed out by Jay. The test
kernel also required commit f307668bfc as a prereq.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1753662
--
You received this bug notification because you are a member of Kernel
Packages,
OK, i'm now running the V4.16.0 kernel:
> craigster0@p51:/local/home/craigster0/Downloads/linux-kernel-4.16$ uname -r
> 4.16.0-041600-generic
and clicking on the "speaker icon" on the menu bar at the bottom of the
screen still shows "No output or input devices found". more
importantly, trying
** 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
** 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) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you
ppc64el versions of the Xenial test kernel are now available here:
http://kernel.ubuntu.com/~jsalisbury/lp1762928/xenial
Xenial required the following two prereq commits:
d96f234f47af ("powerpc: Avoid load hit store in setup_sigcontext()")
d11994314b2b ("powerpc: signals: Stop using current in
Hi Po-Hsu,
Thanks for double-checking, that's appreciated! The security team does
not have an opinion on whether CONFIG_KALLSYMS and CONFIG_KALLSYMS_ALL
should be enabled, from a security/hardening standpoint. It may be
useful from the kernel team's perspective, to make debugging kernel oops
bug
SRU Requests:
https://lists.ubuntu.com/archives/kernel-team/2018-April/092013.html
https://lists.ubuntu.com/archives/kernel-team/2018-April/092016.html
--
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/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** 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/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
Verified fixed in all affected -proposed kernels:
trusty 3.13.0-146.195
xenial 4.4.0-123.147
artful 4.13.0-40.45
** Tags removed: verification-needed-artful verification-needed-trusty
verification-needed-xenial
** Tags added: verification-done-artful verification-done-trusty
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 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 fix
Public bug reported:
[Impact]
The hinic driver isn't included in the installer, so it isn't possible to use
Huawei NICs for network installs.
[Test Case]
Boot d-i on a system with a Huawei PCIe card. Proceed to the network
configuration screen, and see if that NIC is displayed.
[Regression
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 1767443
and then change the status of the bug to 'Confirmed'.
If, due to the
** 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1766605
Title:
linux-aws: 4.4.0-1018.18
** 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:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
add kernel parameter "blacklist=nouveau modprobe.blacklist=nouveau" will
help to boot up for kernel 4.13 and 4.16, but does not solve nvidia
problem
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
v2 SRU request for Artful:
https://lists.ubuntu.com/archives/kernel-team/2018-April/092024.html
--
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/1746474
Title:
unregister_netdevice:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** 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/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in:
SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-April/092032.html
--
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/1766573
Title:
linux < 4.11: unable to use
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1766596
Title:
linux-gcp: 4.13.0-1014.18 -proposed
1 - 100 of 185 matches
Mail list logo