Since they might be related, lets focus on the second issue first, which
is cause by the missing files.
I'll set up a test system to try and reproduce.
It seems like this is a regression, but it would be good to confirm.
Can you test these two kernels?
Last 4.14 Bionic kernel:
https://launchpad
I built a test kernel which can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1766857/
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 install the
linux-image and linux-image-extr
It looks like mainline commit b2d3bcfa26a7a is also needed.
I built another test kernel which has the following three commits:
b2d3bcfa26a7 ("net: core: Expose number of link up/down transitions")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
c36ac8e23073 ("dev: alw
Xenial SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093235.html
** Description changed:
+ == SRU Justification ==
+ The bug reporter noticed that Xenial guests running on Nutanix AHV stopped
+ booting after they were upgraded to 4.4.0-127. Only guests with scsi m
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093238.html
** Description changed:
- More information here:
- https://bugzilla.redhat.com/show_bug.cgi?id=1514836
+ == SRU Justification ==
+ This is a regression introduced in v4.15 and Bionic. The bluetooth
+ contr
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093251.html
** Description changed:
+ == SRU Justification ==
+ The quite new Lenovo V330 is not yet completely supported by the
+ ideapad_laptop module. Without an explicit rule, this module assumes that
+ a hardware
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Triaged
** Changed in: linu
** Changed in: linux (Ubuntu Artful)
Status: New => In Progress
--
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/1776211
Title:
kdump fails to take dump with smt set to 2, hm
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1776
This may not be a bug. The GRUB UEFI implementation does not rely on
the initrdefi and linuxefi names for a UEFI boot, this is integrated
into the linux and initrd commands specifically so that we can use a
grub.cfg which is boot-protocol-agnostic.
Could you detail why you need this in order to
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu Cosmic)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
I meant to say: "It looks like the patch got on "ACK", but not a second"
--
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/1642510
Title:
sched: clsact qdisc is missing in xenial
Status in
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Is there any update on testing of the test kernel?
--
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/1763685
Title:
Fix for flushing TM on coredump only if CPU has TM feature
Status in The
Is there any update on testing of the test kernel?
--
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/1770095
Title:
Need fix to aacraid driver to prevent panic
Status in The Ubuntu-power-s
** Changed in: linux (Ubuntu Cosmic)
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/1771844
Title:
powerpc/livepatch: Implement reliable stack
I built an Artful test kernel with the three patches posted in the description.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1776211
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
I built a test kernel with commit 803cdb8ce584198cd45825822910cac7de6378cb.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1764645
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(
Sorry for the delay.
I built the next test kernel, up to the following commit:
cbcd4f08aa637b74f575268770da86a00fabde6d
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
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) => ubiquity (Ubuntu)
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => 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/1776029
Title:
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.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[
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-hwe (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1776254
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 => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1776277
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776376
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/1776389
Title:
** Changed in: linux (Ubuntu)
Status: New => Triaged
** 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
** Changed in: makedumpfile (Ubuntu)
Status: New => Incomplete
** Changed in: makedumpfile (Ubuntu Artful)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launch
The 4.10 kernel is no longer supported in an Ubuntu release.
Can you see if this bug still happens with Artful or Bionic?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received thi
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
** 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/1776266
Title:
Touchpad and keyboard of MacBook unresponsive
Status in li
*** This bug is a duplicate of bug 1768852 ***
https://bugs.launchpad.net/bugs/1768852
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** This bug has been marked a duplicate of bug 1768852
Kernel bug wh
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[
Please ignore the first question. You already indicated this is a
regression.
** 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://bugs.launchpad.net/bugs/1775945
Title:
Lenovi X1 Carbo
I built a test kernel with a revert of commit 2f500a9d7ff6. The test kernel
can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1776005
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
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
Are you able to install earlier releases such as Artful? If so, we can
use an Artful installation to test various kernels and narrow down what
commit introduced this, if it is a regression.
** Tags added: kernel-da-key
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received 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[
Thanks for testing. Yes, I'll add those modules to the udebs. I just
wanted to have you test those modules before adding them into the udebs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093303.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/1773964
Title:
IPL: ppc64_cpu --frequency hang w
** Description changed:
+ == SRU Justification ==
+ IBM is requesting these two commits in powerpc to fix an error they are
+ seeing:
+ IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on
+ CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n
+
+ The first commit reduces so
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093307.html
** Description changed:
+
+ == SRU Justification ==
+ A commit introduced in mainline v4.14-rc1 to aacraid
+ (b60710ec7d7ab1ca277b458338563ac21b393906) introduced a regression whereby a
+ panic may happen
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093308.html
** Description changed:
+ == SRU Justification ==
+ IBM has requested these three commits in Artful. In Artful, kdump fails to
+ capture dump when smt=2 or off.
+
+ Including these three commits allows kd
nce: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Description changed:
+ == SRU Justification ==
+ IBM reports that arch_get_random_seed_long() invocations may slow down the
+ interrupt handling on heavy interrupt
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093315.html
** Description changed:
+ == SRU Justification ==
Description: kernel: Fix memory leak on CCA and EP11 CPRB processing.
Symptom: Kernel memory not freed when CCA or EP11 CPRB processing fails.
P
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093316.html
** Description changed:
+
+ == SRU Justification ==
+ IBM is requesting the five patches in this pull request to be applied to
Bionic.
+ IBM states they patches fix various issues found after the 18.04 ke
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-June/093317.html
** Description changed:
+ == SRU Justification ==
+ A regression was discovered in Bionic. The regression was introduced by
+ mainline commit f44cb4b19ed4, which then made it's way into Bionic in
+ 4.15.0-
* Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notifi
Status: Confirmed => In Progress
** 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 are a mem
** 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/1776927
Title:
RTNL assertion failure on ipvlan
Status in linux package i
) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Jose
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Impo
Yes, the patches were reverted, then replaced with the ones you listed
from next/master tree. As you noticed, they did not revert cleanly, so
I had to back port and remove code that was added by newer commits.
If you could create a new patch with just the diffs that would be great!
I could revert
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: Confirmed
** Also affects: linux (Ubuntu Bionic)
Importance: Undeci
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
I built one more test kernel that can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1768898
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 install the
linux-image and linux-image
The patch mentioned in the upstream bug report and comment #25 never
landed in mainline. I tried to apply it to Bionic, but it does not
apply cleanly. I'll work on back porting it. I'll post a test kernel
shortly. We can then update upstream with testing results.
--
You received this bug noti
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Triaged
** Changed in: linux (Ubuntu)
Status: Fix Committed => 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
Can you see if this bug still exists in current mainline:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc5/
--
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/1747463
Title:
kernel cr
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
--
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/1770739
Title:
amd64 packages for linux-image-4.15-20 and 21 missing
Status 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.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
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 (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Status: Triaged
--
You received this bug notification because you are a member of Kernel
Package
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
** Tags added: kernel-key
--
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/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
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
hanged in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Tria
t; Medium
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Artful)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Also affects: linux (Ubuntu Cosmic)
I built a test kernel with the requested patch. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1770849
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 install
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[
I built Artful and Bionic test kernels with commit
d90a10e2444ba5a351fa695917258ff4c5709fa5. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1771075
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel
Hello Arindam,
There is a bug report[0] that you created a patch[1] for a while back.
However, the patch never landed in mainline. There is a bug reporter in
Ubuntu[2] that is affected by this bug and is willing to test the
patch. I attempted to build a test kernel with the patch, but it does
n
To install the kernel, just use dpkg like you said. Instead of changing
GRUB_DEFAULT, you could also manually select the test kernel from the
GRUB menu on boot. The grub menu can be accessed by holding the SHIFT
key on boot up, after the BIOS information is displayed.
--
You received this bug n
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph
Salisbury (jsalisbury)
** Changed
Hello,
I'll build a test kernel with you're backports. They all apply to the
current Bionic kernel in the master-next branch: version 4.15.0-22.23.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1770003
Can you test this kernel and see if it resolves this bug?
es are already in the mainline. If I
> remember correctly, one of the patches disabled PCI ATS for the graphics card
> which was causing the issue.
>
> Do you still see the issue with latest mainline kernel?
>
> BR,
> Arindam
>
> -----Original Message-
> From: Jose
On 05/15/2018 09:08 AM, Tom Lendacky wrote:
> On 5/15/2018 7:34 AM, Nath, Arindam wrote:
>>
>>> -Original Message-
>>> From: Joseph Salisbury [mailto:joseph.salisb...@canonical.com]
>>> Sent: Tuesday, May 15, 2018 5:40 PM
>>> To: Nath, Arin
@Peridot, I know you responded that the current mainline kernel still
exhibits the bug on IRC. However, could you also add that test result
to this bug report for upstream tracking?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
SRU request submitted for Bionic:
https://lists.ubuntu.com/archives/kernel-team/2018-May/092441.html
** Description changed:
- Dear Canonical,
- We found that the current Ubuntu kernel contains a problem related to
- qla2xxx driver which causes:
+ == SRU Justification ==
+ IBM is requesting th
Would you like me to build another test kernel with a version, so it
won't collide?
--
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/1770095
Title:
Need fix to aacraid driver to prevent pa
Can you run uname -a to confirm the correct kernel is booted? You
should see this string in the output: "lp1768103".
--
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/1768103
Title:
Lancer
Just to confirm, 4.15-rc1 does not have the issue, but 4.15 final does?
If that is the case, we can try to narrow it down further. Could you
test v4.15-rc9:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/
--
You received this bug notification because you are a member of Kernel
Packages
Yes, you can add EXTRAVERSION info to the kernel name. This is done in
the file: ~/debian.master/changelog. The top line would be changed like
the following:
linux (4.15.0-20.21) bionic; urgency=medium
TO
linux (4.15.0-20.21~lp1770095) bionic; urgency=medium
--
You received this bug notifi
@Peridot,
Request from Upstream:
For the original 4.13 kernel, I don't
see any attachments that have the AMD-Vi messages in question. Were they
completion timeouts (like in the later mainline kernel test, which I'll
get to in a bit) or I/O page fault messages? Without that information it
is har
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1771480
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 (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/1771431
T
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
As
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** 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
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Chang
801 - 900 of 17733 matches
Mail list logo
