** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Also affects: qa-regression-testing
Importance: Undecided
Status: New
** Also affects: apparmor
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
If we are sure that the r8169 works on older kernel, but not on the
latest one, we can use kernel bisection to find which commit causes the
regression:
First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Then,
$ sudo apt build-dep
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Released => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Stefan Bader (smb) => Khaled El Mously (kmously)
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix
Please send that patch to amd-...@lists.freedesktop.org
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1776563
Title:
Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
[Expired for linux (Ubuntu Precise) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Precise)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
4.4.0-1025.26 - aws
Regression test CMPL, RTB.
Issue to note in x86_64 (aws):
libhugetlbfs - 1 failed (alloc-instantiate-race shared), bad config 3, only
spotted on t2.small, passed on the rest
ubuntu_kvm_unit_tests - test skipped, KVM not supported
ubuntu_quota_smoke_test - should be
[ 7609.135055] [ cut here ]
[ 7609.135057] kernel BUG at /home/kernel/COD/linux/drivers/md/raid5.c:1762!
[ 7609.135065] invalid opcode: [#1] SMP PTI
[ 7609.135069] CPU: 2 PID: 302 Comm: md0_raid5 Not tainted
4.18.0-041800rc5-generic #201807152130
[ 7609.135071]
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1782174
Title:
linux-gcp: 4.15.0-1014.14
** Summary changed:
- linux-gcp: -proposed tracker
+ linux-gcp: 4.15.0-1014.14 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team
Great! Thanks for testing.
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1745828
Title:
** Description changed:
[Impact]
Any of the platforms we’ve been seeing SATA problems not going to deepest
state leading to other devices not getting there during long idle or s2idle.
And it also prevents the system from entering deeper PC state other than PC3.
[Test]
Verified the
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Khaled El Mously (kmously) => Stefan Bader (smb)
--
You received this bug notification because you are a member of Kernel
These lockups are probably not related to this bug. I've updated by Intel Sandy
Bridge laptop to 4.17.5 from Fedora 28 repository and now I have random CPU
lockups, too.
4.17.3 worked fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Khaled El Mously (kmously) => Stefan Bader (smb)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress =>
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Released => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Stefan Bader (smb) => Khaled El Mously (kmously)
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1776563
Title:
Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
load, kernel freeze
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1782176
Title:
linux-aws: 4.15.0-1016.16
** Summary changed:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.15.0-1016.16 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.15.0-1016.16 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Khaled El Mously (kmously) => Stefan Bader (smb)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress =>
The following hack resolves the issue for me on arm64:
--- build/util/grub-gencfg.orig 2018-07-17 23:19:53.101127509 +
+++ build/util/grub-gencfg 2018-07-17 22:44:09.46019 +
@@ -144,6 +144,7 @@
push @cmdline, @OPTS;
push @cmdline, "rescue/enable=true" if $xattr{Rescue};
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Released => In Progress
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Stefan Bader (smb) => Khaled El Mously (kmously)
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix
Edit: I checked the uncompromisedness via GPG - as I do not want to risk
waiting a very long time until the https issue is solved. The kernel
still panics at boot and claims this time about a tick-broadcast.c:652.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu Cosmic)
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Khaled El Mously (kmously) => Stefan Bader (smb)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress =>
I'm investigating an issue we're seeing on a couple ARM servers, and it
looks like this maybe the same issue here. What it looks like is that
the mpt3sas driver is being downloaded/loaded just before the
partitioner starts. Since the kernel is configured to scan for SCSI
devices asynchronously,
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Released => In Progress
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Stefan Bader (smb) => Khaled El Mously (kmously)
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Khaled El Mously (kmously) => Stefan Bader (smb)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress =>
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: debian-installer (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1742698
Title:
zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Released => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Stefan Bader (smb) => Khaled El Mously (kmously)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Released =>
I get the following error when i try to install the kernel:
$ sudo dpkg -i
linux-headers-4.18.0-041800rc5-generic_4.18.0-041800rc5.201807152130_amd64.deb
[sudo] password for ignacio:
Selecting previously unselected package linux-headers-4.18.0-041800rc5-generic.
(Reading database ... 187153
> Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
This is a fresh install on a brand new computer, so no clue if a prior
kernel has this problem or not.
> Would it be possible for you to test the latest
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Khaled El Mously (kmously) => Stefan Bader (smb)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress =>
At the current time kernel.ubuntu.com has no https availability (it
times out) and downloading those packages over http is very insecure. I
hope https becomes available soon so I can test this kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is
> First, if one is using select proprietary or out-of-tree modules (e.g.
bcmwl, fglrx, NVIDIA proprietary graphics drivers, VitualBox, etc.)
unless there is an extra package available for the version you are
testing, you will need to uninstall the module first, in order to test
the mainline
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Released => In Progress
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Stefan Bader (smb) => Khaled El Mously (kmously)
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix
@@ -, +, @@
---
drivers/gpu/drm/amd/amdgpu/amdgpu_atpx_handler.c | 1 +
1 file changed, 1 insertion(+)
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_atpx_handler.c
+++ a/drivers/gpu/drm/amd/amdgpu/amdgpu_atpx_handler.c
@@ -575,6 +575,7 @@ static const struct amdgpu_px_quirk amdgpu_px_quirk_list[]
** Patch added: "amdgpu patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776563/+attachment/5164639/+files/patch.diff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Dear Ubuntu Maintainers,
here is the summary:
1. Kernel freeze can be resolved by using the mentioned kernel parameters:
> ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2
It would be the best if the broken DSTD tables were fixed but I think nobody
will do it.
The workaround with the parameters
It is wonderful news! It works - I can now find two devices!
Whether I can work out how to use them is another matter, but as far as I can
see the bug is fixed.
Thanks for your efforts.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: ubuntu-z-systems
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/bugs/1781535
Title:
qdio: don't retry EQBS after CCQ 96
Status in Ubuntu
Hi Joseph,
What's next?
--
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 Carbon regularly has frozen lock- or dark screen after
closing lid
Status in linux
I have been doing stress-testing on LXD at a freshly installed 18.04.
The Linux kernel was the standard 18.04 kernel.
LXD though was compiled from master, ZFS was also compile from master.
I performed the stress-testing by running the command
lxd-benchmark --count 384 --parallel 24
This
Thanks will try that .
On Tue, 17 Jul 2018, 20:21 Joseph Salisbury,
wrote:
> 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
*** This bug is a duplicate of bug 1780894 ***
https://bugs.launchpad.net/bugs/1780894
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** This bug has been marked a duplicate of bug 1780894
package
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
**
** 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.
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
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
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
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
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
SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-July/093876.html
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New =>
** Changed in: kernel-sru-workflow/stakeholder-signoff
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
The requested commit is in Bionic as of Ubuntu-4.15.0-23.25~80:
25dbc82 s390/qdio: don't retry EQBS after CCQ 96
The requested commit is in Xenial as of Ubuntu-4.4.0-128.154~221:
e26f413 s390/qdio: don't retry EQBS after CCQ 96
** Changed in: linux (Ubuntu Xenial)
Status: In Progress =>
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
Our testing on 4.15.0-1017 looks good
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
--
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/1781259
Title:
quickbooks not working properly
Status in linux package 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
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
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
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
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
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
4.17.5 is an upstream kernel. Does this bug happen with an Ubuntu
specific kernel or just upstream?
** 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.
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
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
I built a Bionic test kernel with the patch from:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=d497ebf5fb3a026c0817f8c96cde57
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1781436
Can you test this kernel and see if it resolves
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
**
** No longer affects: linux (Ubuntu Trusty)
--
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/1781535
Title:
qdio: don't retry EQBS after CCQ 96
Status in Ubuntu on IBM z Systems:
(Our testing on 4.15.0-1017, that is)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1782186
Title:
linux-azure: -proposed tracker
Status in Kernel SRU Workflow:
In Progress
I built the next test kernel, up to the following commit:
fc8704280f2ada9f61f08a2d5adc0dab169cc207
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777338
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Our testing looks good.
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1782186
Title:
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Khaled El Mously (kmously) => Stefan Bader (smb)
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress =>
Mainline commit 686c97ee29c886ee07d17987d0059874c5c3b5af is in 18.04 as
of Ubuntu-4.15.0-24.26~47:
6f8aaf5 s390/qeth: fix error handling in adapter command callbacks
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury
(jsalisbury)
**
** Changed in: kernel-sru-workflow/stakeholder-signoff
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Khaled El Mously (kmously) => Stefan Bader (smb)
--
You received this bug notification because you are a member of Kernel
I followed the instructions to unbind the device from xhci and bind it
to vfio and afterwords I was able to boot the VM with the PCI card set
up as pass-through. However, the Windows VM only listed it as an unknown
PCI device and could not find the device drivers (VIA VL805) and I could
not find
** Tags added: kernel-da-key
** 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.
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
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph
Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury
I have more information on this issue. It turns out that I do two things
that are unusual: I set the MTU of the ethernet device to 2156. Then I
send a non-IP ethernet type packet with a length of 2170 bytes (2156 +
14 bytes ethernet header) using raw sockets. The raw socket receiving
it, gets a
You could also try the current mainline kernel if you are interested in
upstream kernels:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Per the commit message for commit dae55b6fef5, the requested patch is
also needed in Trusty and Xenial:
Fixes: 25f269f17316 ("[S390] qdio: EQBS retry after CCQ 96")
Cc: #v3.2+
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury
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
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Released => In Progress
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Stefan Bader (smb) => Khaled El Mously (kmously)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status:
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1780976
and then change the status of the bug to 'Confirmed'.
If, due to the
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
**
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
**
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
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
The files might be empty if all the sequences are marked ok.
--
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/1780979
Title:
Retpoline files are empty on Bionic amd64
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
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!
** Tags added: bionic kernel-da-key
** Package changed: linux-signed
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
Artful and the 4.13 kernel are EOL. Does this bug still happen with the
4.15 or newer kernel?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
1 - 100 of 270 matches
Mail list logo
