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"
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)
** Changed
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Cosmic)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Kernel
Packages, which is s
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[
I built a test kernel with commit db2173198b95. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788549
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
nassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Cosmic)
I
Bionic SRU request also submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-August/094934.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/1787898
Title:
[18.10 FEAT] Add ke
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => Triaged
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Chang
** Changed in: linux (Ubuntu Bionic)
Assignee: Joseph Salisbury (jsalisbury) => Seth Forshee (sforshee)
--
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/1787898
Title:
[18.10 F
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Cha
*** This bug is a duplicate of bug 1788549 ***
https://bugs.launchpad.net/bugs/1788549
** This bug has been marked a duplicate of bug 1788549
powerpc/powernv/pci: Work around races in PCI bridge enabling
--
You received this bug notification because you are a member of Kernel
Packages, wh
signed) => Joseph Salisbury (jsalisbury)
--
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/1788549
Title:
powerpc/powernv/pci: Work around races in PCI bridge enabling
Status in The Ubu
I also built a Xenial test kernel with commit
db2173198b9513f7add8009f225afa1f1c79bcc6, since it was requested in bug
1788850. That bug is now marked as a duplicate of this bug.
The Xenial test kernel is available from:
http://kernel.ubuntu.com/~jsalisbury/lp1788549/xenial
--
You received this
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
** Changed
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
** Changed
*** This bug is a duplicate of bug 1783957 ***
https://bugs.launchpad.net/bugs/1783957
** This bug has been marked a duplicate of bug 1783957
Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login
screen in a normal sequence
--
You received this bug notification becau
inux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification becaus
v4.15
You don't have to test every kernel, just up until the kernel that first
has this bug.
Thanks in advance!
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) =>
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 => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => 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.n
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: 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/bugs/1761379
Just to confirm:
v4.13 Final is GOOD: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/
v4.14-rc1 is BAD and has the bug:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
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[
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
**
** 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/1788321
Title:
swapon failed: invalid argument
Status in linux packag
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => 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/1788782
Title:
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
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[
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 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 a
Does the machine boot if you select 4.15.0-33 from the GRUB menu? If
so, can you test the latest 4.15 upstream stable kernel, which can be
downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: lin
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.19 kernel[
Can you provide some additional details about the bug? Are there
specific error messages or unexpected system behavior happening?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notif
The specific version to test is 3.13.0-158.
--
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/1789131
Title:
Probable regression with EXT3 file systems and CVE-2018-1093 patches
Status 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.19 kernel[
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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 commits 1bd6a1c, ced1bf5 and a581831. The test
kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788782
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
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1788049
Title:
Kernel 4.15.0-32 disables touchscreen in tablet mode
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Joseph Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Statu
I built the next test kernel, up to the following commit:
6b457409169b7686d293b408da0b6446ccb57a76
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1784665
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
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Thanks for testing. I'll submit an SRU request.
--
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/1785675
Title:
Security fix: check if IOMMU page is contained in the pinned physical
pag
Does 3.13.0-157.207 exhibit the bug and 3.13.0-156.206 does not? If
that is the case, we can perform a bisect to identify the offending
commit.
** Changed in: linux (Ubuntu Trusty)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You re
I built a test kernel with commit 6927868e7ae929f037eea973c582b870808880b6.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1787256
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(
I built the next test kernel, up to the following commit:
87eba0716011e528f7841026f2cc65683219d0ad
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1784665
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
** 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/1789435
Title:
kernel 3.13.0-157+158: ext4: wrong error message »invalid blo
Can you give v4.15-rc1 a try and see if it has the bug:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/
--
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/1783957
Title:
Nouveau cra
** 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
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.15 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
Thanks for testing. We need to narrow down the specific version of 4.18
that has the fix. Can you test the following kernels:
v4.18-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1/
v4.18-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc4/
--
You received this bug notific
signee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
*** This bug is a duplicate of bug 1789131 ***
https://bugs.launchpad.net/bugs/1789131
** This bug has been marked a duplicate of bug 1789131
Probable regression with EXT3 file systems and CVE-2018-1093 patches
--
You received this bug notification because you are a member of Kernel
Packa
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubun
This is probably the fix:
22be37acce25 ext4: fix bitmap position validation
I built a test kernel with commit 22be37acce25. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1789131
Can you test this kernel and see if it resolves this bug?
Note about installing tes
** 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)
I built the next test kernel, up to the following commit:
bc631943faba6fc3f755748091ada31798fb7d50
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1784665
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 commit
af8a41cccf8f469165c6debc8fe07c5fd2ca501a. The test kernel can be downloaded
from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
* If the test kernel is p
Thanks for testing, Sarah. I'll submit an SRU request to have this
commit included in Trusty.
This regression was introduced by the following mainline commit:
7dac4a1726a9 ("ext4: add validity checks for bitmap block numbers")
This commit was added to mainline in version v4.17-rc1. However, the
The following commit introduced the exception table in v4.15-rc1:
35732d01fe31 ipv6: introduce a hash table to store dst cache
This commit does not revert easily. Before I contact upstream
regarding this regression, can you test the v4.19-rc1 kernel to see if
any other commits may have helped th
The bisect reported the following commit as the first bad commit:
bc631943faba ("arm64: dts: rockchip: limit rk3328-rock64 gmac speed to
100MBit for now")
It's strange that this is an arm64 commit. I'll investigate a bit and
see why the bisect came back with this result.
--
You received this b
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.19 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.19 kernel[
Do you have a way to reproduce this bug, or was it a one time event?
** 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
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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: Incomplete => Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Chang
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 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: In Progress => Fix Committed
** 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.la
Thanks for digging up this additional information. I'll investigate
further. While I do that, the v4.19-rc1 kernel is now out. It might be
worthwhile to give that one a go, and see if the fix was already
committed to mainline:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/
--
You re
To confirm this regression is due to commit 35732d01fe31, I built a
mainline test kernel with that commits as the tip.
This test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788623
Can you test this kernel and see if it resolves this bug?
--
You received this bug noti
Thanks for the response, David! Correct the print for the mask came
after those 2 lines of code. Here is the snippet:
/* unconditionally mask off the highest bit */
bit = fls(mask) - 1;
mask &= ~(1 << bit);
/* Debug added for lp1783906: */
dump_stack();
I'll build another test kernel with you're suggestions and ask @danieru
to test.
--
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/1783906
Title:
Linux 4.15 and onwards fails to initialize
** Changed in: linux (Ubuntu Xenial)
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: linu
Thanks for testing. I was hoping a fix would be in 4.19, but I'll dig
some more.
--
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/1784665
Title:
mkfs.ext4 over /dev/bcache0 hangs
Status
I built a test kernel with commit 44de022c4382541cebdd6de4465d1f4f465ff1dd.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1789653
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(
I built a second test kernel with additional debug output as requested
by David. This kernel also has the two lines removed request by David.
Can you test this kernel and post your syslog or dmesg output?
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1783906
--
Thanks for the update, Andy. If you need any specific upstream kernel
versions, they are all prebuilt here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Just let me know if you need assistance with a kernel bisect or building
any specific kernels.
--
You received this bug notification becaus
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => 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
Thanks for testing. I'll submit an SRU request for this commit.
--
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/1789653
Title:
regression with EXT4 file systems and meta_bg flag
Status
* Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => 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
Before starting the bisect, just one last kernel to confirm:
v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/
If v4.14 Final is GOOD, I'll start a bisect between v4.14 and v4.15-rc1.
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
https://lists.ubuntu.com/archives/kernel-team/2018-August/095103.html
** Description changed:
+
+ == SRU Justification ==
+ IBM is requesting commit 76fa4975f3ed in powerpc as a security fix.
+ This commit Fixes: 121f80ba68f1. Commit 76fa4975f3ed also requires
+ mainline commit 1463edca6734 as
SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-August/095106.html
** Description changed:
+
+ == SRU Justification ==
+ Mainline commit 7dac4a1726a9 introduced a regression in v4.17-rc1, which
+ made it's way into Trusty via upstream stable updates. This regression
+
https://lists.ubuntu.com/archives/kernel-team/2018-August/095108.html
** Description changed:
+ == SRU Justification ==
+ A regression was introduced where ext4_check_descriptors() was getting
+ called before s_gdb_count was initialized. This regression was
+ introduced to Xenial in 4.4.0-134.
Thanks for testing. That implies that commit 35732d01fe31 is not the
specific commit that introduced the regression. I built a second test
kernel up to the commit f5bbe7ee79c2.
This test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788623
Can you test this kernel and
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => Khaled El Mously (kmously)
** Changed in: linux (Ubuntu Bionic)
Assignee: Joseph Salisbury (jsalisbury) => Khaled El Mously (kmously)
--
You received this bug notification because you are a member of
There are many nouveau commits that were introduced in v4.15-rc1, so we
need to perform a bisect to identify the specific one that caused this
regression.
I started a kernel bisect between v4.14 final and v4.15-rc1. The kernel
bisect will require testing of about 7-10 test kernels.
I built the fi
** 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
** 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: Triaged => In Progress
** Changed in: linu
I built a test kernel with your patch. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1773509
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
-proposed.
Mainline can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7/
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** C
I built a patched test kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1773704
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 a
** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1773973
Title:
Ubuntu 18.04 [ Garri
It would probably be best to open a new bug with a reason why they are
needed for the SRU . That way we can keep the two separate. I'll
submit an SRU request for this specific bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced. If this is a
regression, we can perf
I attempted to apply patchs 4/6 and 5/6 to Bionic but ran into some
issues. Patch 4 does not apply and is trying to make changes to code
that never existed in mainline or Bionic. For example I don't see a git
history in mainline that the struct lpfc_sli_asic_rev ever existed and
the patch is tryi
** 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/1774165
Title:
package linux-firmware 1.173.1 failed to install/upgrade: i
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubunt
601 - 700 of 17733 matches
Mail list logo
