Do you have a way to reproduce this bug, or was it a one time event?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
We think this will be fixed in 4.15.0-19 or newer, so if you can test
and post back that would be great.
--
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/1766577
Title:
4.15.0-15 mdadm: CR
Would it be possible for you to test the proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also af
Would it be possible for you to test the proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags ad
** Changed in: linux (Ubuntu Xenial)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Tags added: xenial
-
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Can you confirm this bug is now resolved in the latest 18.04 kernel?
** Also affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: l
I built a Xenial test kernel with commit 2851940ffee313e. The test kernel can
be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1766573
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .d
I built one more Atrful test kernel with an update to the patch
requested in the SRU feedback.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1746474/artful
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because yo
and
linux-image-extra .deb packages.
Thanks in advance!
** Also affects: acpi (Ubuntu Bionic)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
--
You received
I built a Bionic test kernel with the following one config option not
set:
CONFIG_DRM_AMD_DC_PRE_VEGA
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1761751
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This issue appears to be an upstream bug, since the bug still exists in
mainline without a revert. Would it be possible for you to open an upstream bug
report[0] and maybe ping the patch author?
That will allow the upstream Developers to examine the issue, and may provide
a quicker resolution
Yes, that is the correct kernel version.
--
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/1766377
Title:
Ethernet E1000 Controller Hangs
Status in linux package in Ubuntu:
Incomplete
St
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 t
I built a test kernel with commit 1dc3039bc87ae7d19a990c3ee71cfd8a9068f428.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1776887
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel d
Now that I review this again, I don't think commit
c1fa0768a8713b135848f78fd43ffc208d8ded70 is needed in Xenial proper, since it
is 4.4 based. Commit c1fa0768a871 fixes the following commit:
cd63f3c ("powerpc/tm: Fix saving of TM SPRs in core dump")
However, commit cd63f3c was not added to main
I built the next test kernel, up to the following commit:
1b044f1cfc65a7d90b209dfabd57e16d98b58c5b
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
I built a test kernel with commit 8230819494. It also required commit
94333fac44 as a prereq. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1776927
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kerne
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
--
You receive
sue.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1/
Thanks!
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph
Salisbury (jsalisbury)
Would it be possible for you to test the latest 4.15 upstream stable
kernel?
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/
--
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/1742
I built the next test kernel, up to the following commit:
cbf4b3867875206aa548a8c6d7c886f3299d619e
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
Status: New
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Bionic)
Importance:
Does this issue go away if you boot back into the kernel prior to
4.4.0-127?
--
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/1777345
Title:
Sound card not working in Ubuntu new kernel ver
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 t
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.17 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 t
In Progress
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph
Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
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/1777166
T
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.17 kernel[
** Package changed: linux (Ubuntu) => nvidia-graphics-drivers-390
(Ubuntu)
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Change
Importance: Undecided => High
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
St
in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) =
linux (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you
I built a test kernel with commits 6bed3237624e and ac61c1156623. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777194
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) yo
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.17 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 t
Also, does this bug go away if you select the prior kernel version from
the GRUB menu?
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Status: New
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Ch
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.17 kernel[
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 t
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Cha
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 t
** Changed in: linux-hwe (Ubuntu)
Importance: Undecided => Low
** Changed in: linux-hwe (Ubuntu)
Status: New => Incomplete
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
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.17 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 t
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.17 kernel[
** Changed in: linux (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed
Did this issue just start happening with 18.04?
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury
(jsalisbury)
--
You received th
Can you next test the upstream 4.15.18 stable kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/
If 4.15.18 still has the bug, we can perform a reverse kernel bisect to
identify the fix in mainline.
--
You received this bug notification because you are a member of Kernel
Packages, w
Can you see if this issue exists in the 4.15.0-24 kernel:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/15010188
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• I
At this point, we should probably have two separate bugs to address each
problem. Can we keep this bug for the second issue and create a new bug
for the first issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
--
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/1777600
Title:
chzdev can't find
)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged =>
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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 t
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
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.17 kernel[
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (
)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury
(jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Joseph Salisbury (jsali
I built a test kernel with commit
682e6b4da5cbe8e9a53f979a58c2a9d7dc997175. Commit 34dd25de9fe3f was also
required as a prereq.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777857
Can you test this kernel and see if it resolves this bug?
Note about installing t
I built the next test kernel, up to the following commit:
4422d80ed7d4bdb2d6e9fb890c66c3d9250ba694
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
I built a test kernel with a revert of Bionic commit
494f8f20811baf580370f7d65bb7ea615ec37882. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1777242
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kern
*** This bug is a duplicate of bug 1777820 ***
https://bugs.launchpad.net/bugs/1777820
** This bug has been marked a duplicate of bug 1777820
Updating Nvidia drivers causes Cinnamon crashes and seems to be in fallback
mode
--
You received this bug notification because you are a member of
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.17 kernel[
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.17 kernel[
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: l
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
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/1
Hi Guilhem,
Can you conform that this bug does not exist with the kernel currently
in -proposed?
--
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/1775217
Title:
bluetooth controller fail
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 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 t
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 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 t
I built a test kernel with commit 0d98ba8d70b0070ac117452ea0b663e26bbf46bf.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1771467
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(
Bionic commit 494f8f20811baf5 is a revert of Bionic commit dc0f16f9b50.
This was done for bug 1728238. We will investigate further to find a
solution.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
It now appears reverting Bionic commit dc0f16f9b508 has introduced bug
1777242. We need to put now either revert the revert or find an
alternative fix.
** Changed in: linux (Ubuntu)
Status: Fix Released => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Fix Released => In
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.18 kernel[
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.18 kernel[
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093481.html
** Description changed:
- --Problem Description--
+
+ == SRU Justification ==
+ IBM has seen hard lockups when running stress tests against Bionic.
+ These test sometimes lead to rcu_stalls. IBM found th
SRU Request Submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093483.html
** Description changed:
+ == SRU Justification ==
+ IBM is seeing kernel traces during testing. This is due to a missing
+ backport of some kernel fixes in the RTC driver, which is commit
+ 682e6b4da5cb.
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093487.html
** Description changed:
- Description: uprobes: fix SIGSEGVs with setjmp/longjmp
+ == SRU Justification ==
+ This commit fixes SIGSEGVs with setjmp/longjmp.
Symptom:
Setting a user space return pro
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093488.html
** Description changed:
+ == SRU Justification ==
+ IBM is requesting these patches in Bionic. ocxl (opencapi) is a relatively
+ new driver which was added to Ubuntu 18.04; It's specific to POWER9 systems.
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093493.html
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Description changed:
+
+ == SRU Justification
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093489.html
** Description changed:
- Running up two containers using ipvlan with IPv6 autoconf active
- triggers an assertion failure in the kernel (cloud image running on
- Brightbox)
+ == SRU Justification ==
+ Runn
Bionic SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093495.html
I should have a Xenial test kernel available for testing shortly. It
requires some backporting of the patches.
--
You received this bug notification because you are a member of Kernel
Packages, whi
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1778511
Title:
PCI network card (r8169) UNCLAIMED at boot
Status in linux
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 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 t
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 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 t
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: artful bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
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.18 kernel[
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Impo
I built a test kernel with the patch in the description. The test kernel can
be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1778486
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linu
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093554.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/1766055
Title:
Vcs-Git header on bionic linux so
Team (canonical-kernel-team) => Joseph
Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph
Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 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 t
401 - 500 of 17733 matches
Mail list logo
