Based on you're test results posted in comment #28, I built the next test
kernel, up to the following commit:
8c609698569578913ad40bb160b97c3f6cfa15ec
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1783957
Can you test that kernel and report back if it has the bug
I'll ping upstream for feedback if v4.19-rc4 still exhibits the bug.
--
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/1791321
Title:
No video on laptop display after suspend/resume
Status
signee: (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: linux (Ubuntu)
Status: Triaged =&
We can perform a "Reverse" bisect to identify the commit that fixes this
bug in v4.19. We first need to identify the last bad kernel version and
the first good kernel version.
Can you test the following kernels:
v4.16 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/
v4.17 Final: http:/
Can you next test:
4.15.0-9: https://launchpad.net/ubuntu/+source/linux/4.15.0-9.10/+build/14326410
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsal
I built the next test kernel, up to the following commit:
00c3aa70c712c5f7758370e0cd719ac5e401305e
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792100
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
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Importance: Medium => High
** Changed in
The commit that fixes this bug is in Ubuntu-4.15.0-24 as commit:
9b185721376e powerpc/mce: Fix a bug where mce loops on memory UE.
Changing status to "Fix Released"
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix
Sorry, my upload failed. The .debs are there now.
--
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/1792100
Title:
Boot hangs at "loading initial ramdisk..."
Status in linux package in Ub
Can you next try 4.15.0-15? It can be found at:
https://launchpad.net/ubuntu/+source/linux/4.15.0-15.16/+build/14530348
All of the Bionic kernel versions can be found at:
https://launchpad.net/ubuntu/bionic/+source/linux
>From that page, you click on the version number. Then one the following
p
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Status: Triaged
** Tags add
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 Bionic)
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/1780817
Title:
kernel panic in nested VM with latest 4.15 kernel (
That should be good. I just like to have the latest mainline already
tested in case upstream asks for it. I'll ping upstream and see what
the next steps should be.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
I built the next test kernel, up to the following commit:
84d28cc43f2d9820bd97e8dc428b00483322f660
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792100
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
When you say you 'already' tested that kernel, do you mean you already
tested it before I posted it in comment #31? The kernel name might look
similar to a prior kernel, but there is a unique date stamp in the name,
'201809190746' in the latest test kernel.
--
You received this bug notification
Bionic and Cosmic SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095563.html
** Description changed:
+
+ == SRU Justification ==
+ IBM reports the qethqoat tool fails. qeth_query_oat_command() currently
+ allocates the kernel buffer for the SIOC_QETH_QUERY_OAT ioctl w
Xenial SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095566.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/1793086
Title:
qeth: use vzalloc for QUERY OAT
** Summary changed:
- Kernel hang on drive pull caused by incomplete backport for bug 1597908
+ Kernel hang on drive pull caused by regression introduced by commit
287922eb0b18
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1597908
Title:
linux-kernel: Freeing IRQ from IRQ context
Status
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095569.html
** Description changed:
- A bug was introduced when backporting the fix for
- http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu
- 16.04 LTS 4.4 kernels >= 4.4.0-36, and many other n
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
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
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095572.html
** Description changed:
- After the most recent 18.04 32-bit upgrade of linux-image-generic, it
- now refuses to boot under Xen PV mode:
+ == SRU Justification ==
+ After an upgrade to Bionic, the bug
I built the next test kernel, up to the following commit:
d4be7ce8e6324691737b45f336d770245ba07310
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792100
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
Thanks for the feedback. I submitted those three commits for bug
1747572. To see if they introduced the regression, I built a test
kernel with those three commits reverted.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792580
Can you test this kernel and see if
I built the next test kernel, up to the following commit:
f150891fd9878ef0d9197c4e8451ce67c3bdd014
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1783957
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
We next need to identify which 4.17 release candidate introduced the
fix. Can you next test the following kernels:
v4.17-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc1
v4.17-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc4
v4.17-rc7: http://kernel.ubuntu.com/~kernel-ppa/
The fix landed in Bionic via the 4.15-rc3 updates:
297d6b6e56c2 hv: kvp: Avoid reading past allocated blocks from KVP file
The status has been changed to "Fix Released"
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification becaus
Hi Jarno,
A kernel bug report was opened against Ubuntu [0]. This bug is a
regression introduced in v4.12-rc1. The latest mainline kernel was
tested and still exhibits the bug. The following commit was identified
as the cause of the regression:
120645513f55 ("openvswitch: Add eventmask sup
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095580.html
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
** Description changed:
Hey everyone,
When running in a container with a user namespace, if you call getxattr
I built the next test kernel, up to the following commit:
a2fc4bd61e7ec3bb1f7c8b3d47272be813f88aea
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1783957
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 the next test kernel, up to the following commit:
d86a0bd64457a4373623713e93fe8848a9e75ce7
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1792100
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
New => In Progress
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux
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 => Medium
** Chan
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.16 kernel[
Did this bug just start happening with the 4.15.0-20 kernel? Were there
prior 18.04 kernels that did not exhibit this bug?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also affects: linux (Ubuntu Bionic)
Importance: High
Status: Confirmed
** Also affects: linux-az
I built one more test kernel.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745646
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 .deb packages.
Thanks in advan
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 t
** 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/1766055
Title:
Vcs-Git header on bionic linux source package points to zesty git tree
Status in linux package
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: linu
I built Artful and Xenial test kernels with the back port. The test
kernels can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1762928/xenial
http://kernel.ubuntu.com/~jsalisbury/lp1762928/artful
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, yo
to
identify the last kernel version that did not have bug and the first
kernel version that does.
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed
Thanks for the pointer, Jay! I'll build a Xenial test kernel with these
two commits and post a link to it.
--
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/1753662
Title:
[i40e] LACP bond
** Description changed:
- It's impossible to use power button functionalities in Acer Swift Notebook
Series (tested on Acer Swift 3 sf314-52).
+ == SRU Justification ==
+ It's impossible to use power button functionalities in Acer Swift Notebook
+ Series (tested on Acer Swift 3 sf314-52). The k
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, w
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 s
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.
https://bugs.launchpad
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
+ configures
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: waitin
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 netf
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 t
** Also affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Zesty)
** Changed in: linux (Ubuntu Artful
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first kerne
On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote:
> On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury
> wrote:
>> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
>>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
>>> wrote:
>>>> Hi Rafael,
>&g
Hi Harry,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found the following commit introduced the bug:
commit 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c
Author: Harry Wentland
Date: Tue Sep 12 15:58:20 2017 -0400
drm/amd/dc: Add dc display driver (v2)
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.16 kernel[
** 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/1767356
Title:
Long boot time (approx 5 minuntes!), long shutdown
Status
Does this bug go away if you boot back into the prior kernel version?
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 follow
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => Triaged
** Changed in: linux (U
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 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.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 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.16 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.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 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.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 t
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Bionic)
Importance: Medium
Status: Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
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 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.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 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.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 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.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 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.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 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.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 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.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 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.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 t
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => 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://bugs.launc
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 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.16 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.16 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.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 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.16 kernel[
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of 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.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 t
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
** Also affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
St
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** 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/1767905
Title:
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.16 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.16 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.16 kernel[
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1768211
Title:
norton setup
Status in linux package in Ubuntu:
Invali
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: Ne
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 t
** 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/1768115
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running
with IO stress crashed@se
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** 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
** Changed 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.17 kernel[
The original bug reporter is unable to reproduce this bug, so would it
be possible for others affected to test the latest mainline kernel? It
is available for download from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3
--
You received this bug notification because you are a member of
Can you see if this bug also happens with the latest mainline kernel, or
if it was already fixed upstream? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Can you ensure you are booted into the test kernel posted in comment #2?
It should have the following text in the uname -a output: "lp1758205"
--
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
On 05/02/2018 06:41 AM, Rafael J. Wysocki wrote:
> On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas wrote:
>> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote:
>>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury
>>> wrote:
>>>> On 04/16
Hi Gopal,
I built a test kernel with the patch requested by upstream.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1745646
Can you test this kernel and see if it resolves this bug?
Thanks in advance!
--
You received this bug notification because you are a me
** Changed in: linux (Ubuntu)
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.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
Status in linux
I built a Bionic test kernel with commits 36148c2bbfbe and c9f1f58dc2eb.
Commit 3a9b76fd0db9 is not needed in Bionic, since it is 3.15 based.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1670041/bionic
Can you test this kernel and see if it resolves this bug?
--
On 05/02/2018 06:41 AM, Rafael J. Wysocki wrote:
> On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas wrote:
>> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote:
>>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury
>>> wrote:
>>>> On 04/16
1201 - 1300 of 17733 matches
Mail list logo
